Your Team May Still Like You. But Do They Still Believe You?
A manager can remain respected, approachable, and personally well-liked after repeated layoffs—and still discover that their words no longer influence what the team believes or does.
This article is adapted from Chapter 6, “Your Own Credibility Debt,” in Twice Cut: Rebuilding Trust When the Layoffs Don’t Stop. The chapter examines the personal credibility account every leader carries and why rebuilding it requires smaller promises, visible follow-through, and more patience than most managers expect.
Franklin decided to repair the team’s trust in one meeting.
He had noticed the decline for months.
Before the layoffs, his staff meetings often ran beyond the scheduled time.
People challenged assumptions.
They raised concerns before those concerns became problems.
They argued over priorities, proposed alternatives, and asked questions that forced Franklin to think more carefully about decisions he might otherwise have made too quickly.
After the second round of layoffs, the meetings changed.
They became efficient.
Too efficient.
Franklin presented the agenda.
Employees provided their updates.
The group reviewed the immediate deadlines.
Then everyone left.
No one disagreed.
No one asked what the current decisions meant for the next quarter.
No one volunteered a concern that had not already become impossible to ignore.
The meetings ended on time because the team had stopped investing anything that might make them run long.
Franklin could feel his standing slipping.
He did not have a metric for it.
There was no dashboard showing that employees had reduced the amount of credit they extended to his words.
But he could feel the difference.
The team still treated him respectfully.
People still answered his messages.
They still completed their work.
Some employees still stopped by his office to talk about ordinary matters.
But when Franklin discussed the future, something in the room closed.
The team listened without allowing what he said to change very much.
Franklin decided the problem needed a decisive response.
He scheduled an all-hands meeting.
He prepared carefully.
He reviewed the organization’s plans, spoke with his director, and built a presentation designed to replace uncertainty with confidence.
He acknowledged that the previous months had been difficult.
He thanked the team for remaining focused.
He described the company’s strategic direction and explained why he believed the organization was now positioned more securely.
Then, near the end of the meeting, Franklin delivered the sentence he believed the team most needed to hear.
“This was absolutely the last round.”
Not probably.
Not based on current information.
Not as far as leadership presently expected.
Absolutely.
Franklin believed the statement when he made it.
That did not protect him from what happened next.
Nine weeks later, a change in another part of the business affected several responsibilities connected to Franklin’s team. It was not a full third layoff, but it reversed enough of the plan that employees could clearly see the difference between what Franklin had promised and what the organization ultimately did.
No one confronted him.
No one replayed the recording of the meeting.
No one asked whether he remembered using the word “absolutely.”
They did not need to.
Franklin remembered.
So did they.
The statement had been designed to restore confidence.
Instead, it became one more dated entry in the team’s record of leadership promises that had failed to predict reality.
Franklin had attempted to make one large deposit into an account that was already overdrawn.
The deposit did not clear.
And because the promise had been public, memorable, and emotionally significant, the failure carried a penalty.
Every Leader Carries a Personal Trust Account
Employees may distrust the organization as a whole.
They may question senior executives.
They may doubt the official explanations behind restructuring decisions.
But they also maintain a separate judgment about their direct manager.
That judgment answers a narrower question:
How reliably do this person’s words match what happens next?
This is the manager’s personal credibility account.
It does not track whether the manager is kind.
It does not track whether employees believe the manager had good intentions.
It does not even track whether the manager personally agreed with the organizational decisions they communicated.
It tracks whether the manager’s statements proved usable.
Did the update arrive when promised?
Was the timeline accurate?
Did the manager describe an expectation as an expectation—or present it as a certainty?
Did employees learn important information directly from the manager, or through rumors and informal channels?
Did the manager promise workload relief and then actually remove work?
Did they say a question would be escalated and later return with an answer?
Did the future they described resemble the future that arrived?
Employees may never create a written ledger.
But they keep one behaviorally.
Every interaction either adds to or subtracts from the amount of weight they place on the manager’s next statement.
Above the credibility line, employees generally offer the benefit of the doubt.
A manager can make an honest prediction that turns out to be wrong without losing the entire relationship.
People recognize that conditions change.
They understand that managers do not control everything.
Below the line, the default reverses.
The employee no longer assumes the statement is reliable.
They wait.
They verify.
They check with another department.
They look for the budget entry, signed agreement, updated system record, or executive announcement before changing their plans.
They may still listen politely.
But the manager’s words no longer move behavior by themselves.
That is credibility debt.
The Debt Is Personal Even When the Decision Was Not
Franklin did not create the change that weakened his promise.
He had not secretly known a reversal was coming.
He had not intentionally misled the team.
He had spoken using the information available to him at the time.
All of that mattered morally.
Very little of it changed the team’s operating position.
The credibility account does not function like a courtroom.
Employees are not carefully assigning proportional fault among executives, finance teams, consultants, human resources, and middle managers.
They are deciding whether the person standing in front of them can be trusted as a guide.
Franklin’s intention was not the question.
The predictive value of his words was.
This can feel profoundly unfair to managers.
They may have argued against the decision privately.
They may have received the information only hours before the announcement.
They may have communicated exactly what senior leaders told them.
They may have believed every reassurance they delivered.
Yet the credibility cost still attaches to the person who spoke.
That is not because employees think their manager secretly controls the whole organization.
It is because the manager’s words entered the relationship under the manager’s name.
You may borrow information from above.
You cannot borrow someone else’s credibility to deliver it.
Once the statement leaves your mouth, it becomes an entry in your account.
Good Intentions Do Not Cancel a Withdrawal
Leaders often defend failed reassurance by explaining that they sincerely believed it.
“I would never intentionally mislead the team.”
“I shared the best information I had.”
“At the time, leadership genuinely expected the restructuring to be finished.”
Those statements may be true.
They may also be important in a conversation about integrity.
But integrity and accuracy are not identical.
A manager can be sincere and still become unreliable.
A leader can care deeply about employees and still make promises their authority cannot support.
A statement can be ethically well-intended and operationally unusable.
This distinction becomes especially important after repeated layoffs because employees have already learned that sincerity does not guarantee stability.
The manager may mean every word.
The executive may mean every word.
The organization may honestly believe the current plan will hold.
Then conditions change.
Another decision arrives.
The employee who acted on the reassurance carries the consequence.
After experiencing that cycle more than once, the employee stops asking only whether the manager is honest.
They begin asking whether the manager’s statements are safe enough to use.
That is a more demanding standard.
It is also the standard repeated uncertainty creates.
Credibility Deposits Are Small by Design
Managers often imagine that rebuilding trust requires a major event.
A powerful speech.
A transparent town hall.
A meaningful team retreat.
A bold commitment from senior leadership.
A dramatic demonstration that the future will be different.
But credibility deposits are rarely dramatic.
They are usually small enough to seem inadequate.
An update sent on the day the manager promised to send it.
A question answered after the manager said they would investigate it.
A meeting canceled because the team’s capacity was genuinely limited.
A deadline challenged rather than silently passed down.
An honest “I do not know yet” offered instead of a comforting prediction.
A piece of bad news communicated directly before employees discover it elsewhere.
A responsibility removed after the manager said priorities would be reduced.
None of these actions restores trust in one moment.
That is precisely why they are credible.
They do not require the employee to make a large emotional investment.
They create a small test.
The manager said the update would arrive Friday.
Did it?
The manager said the issue would be escalated.
Was it?
The manager said one report would be discontinued.
Did the request actually stop?
The manager said employees would hear new information directly.
Did that happen?
Each completed test deposits a small amount into the account.
The deposit is limited.
But it is real.
Withdrawals Are Larger Than Deposits
Credibility accounts are not symmetrical.
One major broken promise can create more damage than several small kept commitments can immediately repair.
This frustrates leaders.
They may follow through consistently for four weeks and wonder why the team has not become more trusting.
They may feel that employees are ignoring the progress.
They may think the group has become committed to skepticism.
But the team may simply be weighing the entries differently.
A Friday update is useful.
“This is absolutely the last round” can influence whether someone accepts a promotion, signs a lease, delays a job search, makes a major purchase, or commits to a long-term project.
The larger the behavioral decision attached to the statement, the larger the withdrawal when the statement fails.
This is why dramatic reassurance is so dangerous when credibility is already low.
The leader is asking the team to place a large transaction against an account that does not currently have enough balance to support it.
If the promise holds, the leader may gain some credit.
If it fails, the failure confirms the exact conclusion the team had already begun forming:
Leadership’s words cannot safely guide our decisions.
The promise does not merely fail.
It becomes evidence.
The Temptation to Spend What You Do Not Have
Franklin’s mistake did not come from carelessness.
It came from urgency.
The problem felt large.
The team’s distance felt large.
The fear in the room felt large.
So Franklin reached for a response that felt equally large.
This is a common leadership instinct.
When employees are deeply uncertain, a modest statement feels emotionally inadequate.
“I will tell you what I know on Friday” seems too small.
“I cannot promise there will be no further changes” feels unsatisfying.
“The budget is currently approved through the end of this quarter” does not seem strong enough to calm a team wondering whether their jobs will exist next year.
The leader therefore expands the statement.
Current approval becomes long-term protection.
An expectation becomes a commitment.
A strategic intention becomes a guaranteed outcome.
The manager believes stronger language will create stronger reassurance.
But reassurance is not measured by the emotional force of the sentence.
It is measured by whether the sentence survives reality.
A smaller statement that remains true creates more long-term security than a powerful statement that collapses later.
The urgent leader focuses on how the team will feel at the end of the meeting.
The credible leader focuses on whether the sentence will still be defensible three months later.
Large Gestures Can Backfire
A retreat may be meaningful.
A town hall may be necessary.
A carefully delivered message may provide clarity.
The problem is not the size of the event.
The problem is using a large event to make a promise the account cannot support.
When credibility is low, employees do not automatically experience a polished presentation as evidence of change.
They may experience it as a more professional version of the same unreliable pattern.
The slides are better.
The language is more empathetic.
The leader appears more vulnerable.
But the central claim still depends on events the leader does not control.
Employees recognize the structure even when the words change.
Something painful happens.
Leadership senses that trust is declining.
A meeting is scheduled.
The future is described confidently.
Employees are encouraged to reengage.
Then another decision exposes how little of that confidence was guaranteed.
The larger the meeting, the easier it becomes to remember the claim.
The stronger the wording, the easier it becomes to measure the contradiction.
A large gesture made from an overdrawn account can become the most visible withdrawal yet.
Going Quiet Is Not Safer
Some managers learn the danger of overpromising and respond by reducing communication.
They become cautious.
They wait until every detail is final.
They avoid discussing rumors, potential changes, or unresolved questions.
They tell themselves they are protecting the team from speculation.
They may also be protecting themselves from making another statement that proves wrong.
This feels safer than Franklin’s speech.
It creates a different withdrawal.
Silence does not leave an empty space.
Employees fill it.
They compare fragments of information.
They watch calendars.
They examine canceled meetings, delayed approvals, vacant positions, executive travel, consultant activity, and changes in leadership language.
They ask colleagues in other departments what they have heard.
The less information employees receive directly, the more important indirect signals become.
Eventually, the team learns something the manager already knew—or partially knew—and did not communicate.
The manager may explain that the information had not been final.
The employee experiences the delay as concealment.
Now the account is debited not because the manager promised too much, but because they appeared to withhold what little they had.
Overstatement and silence look like opposite behaviors.
They come from the same objective.
The manager is trying to control the team’s reaction.
Overstatement attempts to control the reaction through certainty.
Silence attempts to control it through omission.
Neither rebuilds credibility.
Credibility grows when the leader communicates true, appropriately sized information on a predictable schedule, even when the information does not create relief.
Being Liked Is Not the Same as Being Believed
Franklin remained personally well-liked.
Employees did not consider him cruel.
They knew he cared about the team.
Some believed he was doing the best he could inside a difficult organization.
That affection did not restore the account.
This distinction can confuse leaders because relationships often feel warm even after credibility has declined.
Employees may laugh with the manager.
They may ask about the manager’s family.
They may thank them for being supportive.
They may defend the manager when discussing senior leadership.
Yet they still do not make long-term plans based on what the manager says.
They separate the person from the signal.
“I like Franklin.”
“I believe Franklin means well.”
“I am not making a career decision based on Franklin’s reassurance.”
All three statements can exist together.
Leaders sometimes misread warmth as restored trust.
They assume that because the relationship feels less tense, employees once again believe the organization’s future-facing messages.
But credibility is revealed through behavior.
Do employees act on your information?
Do they plan further ahead after you provide an update?
Do they raise risks before confirming privately that it is safe?
Do they accept an assignment because they believe the promised resources will appear?
Do they stop maintaining a hidden contingency after you describe the future?
The question is not whether people enjoy interacting with you.
The question is whether your words alter what they are willing to risk.
The Balance Is Different for Every Employee
Managers often describe team trust as though the whole group holds one shared balance.
“My team trusts me.”
“My team no longer believes leadership.”
“The team has become skeptical.”
But credibility is held individually.
One employee may have experienced the manager as consistently reliable.
Another may remember a promise made personally to them that was never completed.
A third may have joined after the first layoff and carry less history.
A fourth may have heard the failed promise secondhand and assign it less weight.
A fifth may have reorganized their family life around information the manager provided and experienced the reversal much more deeply.
The same statement therefore lands against different balances.
This explains why a leader may notice uneven responses.
One employee begins asking questions again.
Another remains procedural.
A third openly challenges every assumption.
A fourth appears cooperative but continues searching for another job.
The manager has not necessarily communicated inconsistently in the present.
The employees are receiving the statement through different histories.
This means credibility repair cannot rely only on team-wide messaging.
Some deposits must be personal.
A workload commitment kept for one employee.
A development opportunity handled honestly.
A concern escalated and resolved.
A difficult conversation completed without retaliation.
A promised check-in that actually occurs.
The team account matters.
The individual ledgers determine how the team account is experienced.
The Debt Is Not Permanent
Credibility debt can feel permanent because the repair is slow and early progress is difficult to see.
A leader may change their behavior and receive almost no immediate emotional reward.
The team does not become enthusiastic.
Meetings do not suddenly become energetic.
Employees do not thank the manager for communicating more precisely.
The skepticism remains visible.
That does not mean the deposits are failing.
Trust often begins returning as reduced friction.
Employees stop verifying every minor detail.
A question is asked earlier.
A risk reaches the manager before it becomes a crisis.
Someone accepts a modest commitment without requesting confirmation from three additional sources.
An employee begins using “we” again while discussing the next quarter.
A team member volunteers a concern in the group meeting instead of mentioning it privately afterward.
These are not dramatic signs.
They indicate that the employee is spending less energy protecting themselves from the possibility that the manager’s words will fail.
That reduction in self-protection is the first repayment.
Full trust may still be distant.
The account has started moving.
Run a 30-Day Credibility Ledger
Managers rarely remember every commitment they make.
A statement that feels casual to the leader may be recorded as meaningful by the employee.
“I will look into that.”
“We should have an answer next week.”
“I will speak with finance.”
“We are going to reduce the reporting burden.”
“I will make sure you are included.”
“I will follow up after the executive meeting.”
Each sentence creates an expectation.
The manager may forget it among dozens of meetings and responsibilities.
The employee waiting for the answer usually does not.
For the next 30 days, record every commitment you make to the team.
Do not track only major promises.
Track small ones.
Record:
What you promised
Use the exact outcome or action you committed to provide.
When you promised it
Capture the date and the context.
When it was due
Do not leave the timeline implied.
Whether it was visibly completed
The team must be able to recognize that the commitment was kept.
Whether you closed the loop
When the original outcome was impossible, did you explain what happened rather than allowing the promise to disappear?
The purpose is not to create another administrative burden.
It is to expose the difference between your memory of being reliable and the team’s experience of your follow-through.
Most leaders discover two things.
They make more commitments than they realize.
They close fewer loops than they believe.
Private Follow-Through Does Not Always Register
A manager may complete a commitment behind the scenes and assume the team recognizes it.
They speak to finance.
They challenge a deadline.
They raise the staffing concern.
They ask senior leadership for clarification.
Nothing changes.
Because there is no visible outcome, the manager says nothing.
From their perspective, they followed through.
From the employee’s perspective, the commitment disappeared.
Visible follow-through does not require self-promotion.
It requires closure.
“I raised the deadline issue as promised. The request was not approved. Here is the reason I was given, and here is the adjustment I can make within the team.”
“I asked whether the position could be restored. The answer is no for this quarter. I will revisit the question during the next planning cycle.”
“I said I would confirm the funding. It has not been released, so we are not beginning the work yet.”
The outcome may disappoint employees.
The loop still closes.
A leader who reports an unsuccessful effort can earn more credibility than one who quietly works hard but allows commitments to vanish.
The ledger does not credit invisible intention.
It credits observable alignment between words and actions.
Make Commitments Smaller Than Your Ambition
When a manager feels responsible for rebuilding trust, they may create too many commitments.
Weekly updates.
Individual meetings.
Workload reviews.
Career conversations.
Escalations.
Process changes.
Recognition programs.
New team forums.
The plan appears comprehensive.
Then ordinary work returns.
The manager misses the Friday update.
Two one-on-ones are rescheduled.
The workload review remains incomplete.
The new forum disappears after three sessions.
A trust-rebuilding plan becomes another collection of promises that did not last.
Choose fewer commitments.
Make them smaller than your ambition.
Franklin eventually limited himself to three specific commitments each month.
Each commitment was within his direct control.
Each had a visible completion point.
Each included a timeline he could realistically protect.
This restraint felt inadequate at first.
The team’s distrust was large.
Three small commitments seemed almost insulting in comparison.
But Franklin’s previous mistake had been matching the size of the promise to the size of the emotional problem.
His new approach matched the size of the promise to the size of his actual control.
That is the more important measurement.
Watch for New Withdrawals
A credibility account can receive deposits and withdrawals at the same time.
You may communicate consistently for weeks while another organizational surprise creates a new debit.
A restructuring is announced elsewhere.
A position that was expected to open remains frozen.
A project described as strategic loses funding.
A senior executive leaves unexpectedly.
Employees may connect that event to the broader leadership system, including you.
This can make the repair feel impossible.
You keep your promises.
The organization creates new contradictions.
The balance barely moves.
The answer is not to increase the size of your promises.
It is to maintain the distinction between what belongs to the organization and what belongs to your personal account.
You cannot prevent every new withdrawal created by events above you.
You can avoid adding unnecessary personal withdrawals.
Do not pretend to know more than you do.
Do not delay information because it is uncomfortable.
Do not promise protection you cannot guarantee.
Do not announce a decision before it is real.
Do not allow a missed commitment to disappear without acknowledgment.
The broader environment may remain unstable.
Your pattern can become stable inside it.
That stability will not erase the organization’s decisions.
It gives employees one signal that becomes increasingly reliable.
What to Do When the Balance Does Not Move
A month of improved follow-through may produce little visible response.
Before deciding the team has become permanently cynical, examine three possibilities.
The withdrawal was larger than the deposits
A highly memorable promise may require a long period of repair.
Four weeks of accurate updates may not offset a statement that influenced major career or personal decisions.
The timeline may be frustrating.
That does not make it incorrect.
The deposits were not visible
You may have completed the action without closing the communication loop.
Employees cannot credit what they cannot observe.
Make the follow-through clear without turning it into a performance.
New withdrawals are occurring
Your current behavior may be improving while the organization continues generating uncertainty.
Employees may be responding to both processes simultaneously.
Continue controlling the entries that are yours.
Do not make a fresh, oversized promise in an attempt to accelerate the balance.
The desire to speed up the repair is often what creates the next withdrawal.
What Franklin Did Instead
Franklin did not schedule another speech.
He stopped trying to make the team feel differently in a single meeting.
He selected three commitments each month.
They were not inspiring.
That was intentional.
He sent an update on the date he said he would send it.
He moved a meeting after saying he would protect the team’s preparation time.
He communicated difficult information directly rather than allowing employees to hear it through another department.
He reduced the size of his language.
When he knew something, he explained what made it confirmed.
When he held an expectation, he labeled it as an expectation.
When he did not know, he stopped treating uncertainty as a leadership failure.
Five months into the new approach, a reorganization above Franklin created uncertainty about his team’s structure.
During a planning meeting, employees looked to him for reassurance.
Franklin felt the old temptation.
He could have said the team was protected.
He could have explained why he believed the reorganization would not reach them.
He could have offered a confident prediction and ended the meeting with less visible anxiety.
Instead, he said:
“I do not yet know whether this will affect our structure. I will tell you as soon as I receive confirmed information. Nothing about our immediate work has changed today.”
The statement did not make anyone feel secure.
No one thanked him for his honesty.
The meeting remained quiet.
But no one later discovered that Franklin had promised something reality contradicted.
Nobody looked reassured.
Nobody looked betrayed.
At that stage of the repair, the absence of a new withdrawal was progress.
Credibility Returns Before Confidence Does
A manager may wait for employees to appear confident before believing the account is recovering.
Confidence usually arrives later.
Credibility begins with smaller behavioral shifts.
Employees ask a question because they think the answer may be useful.
They accept a timeline without immediately constructing a backup.
They raise a concern early.
They allow a manager’s update to influence planning.
They distinguish between the manager’s current statement and the organization’s previous failures.
These moments show that the leader’s words are regaining limited purchasing power.
Not enough for a large transaction.
Enough for a small one.
That is how the account recovers.
One appropriately sized promise.
One visible completion.
One honest limitation.
One difficult update delivered directly.
Then another.
The manager does not return to the trust they held before the first layoff.
That trust was built in a different environment.
The rebuilt version is often slower, more cautious, and less dependent on optimism.
It may also be stronger.
It is not based on the belief that nothing will go wrong.
It is based on evidence that the leader will communicate accurately when something does.
Stop Asking for Credit Before You Have Rebuilt It
Leaders under credibility debt often want the team to recognize how much they are trying.
They want employees to notice the improved communication.
They want acknowledgment that they are keeping more commitments.
They want the skepticism to soften.
That desire is understandable.
It can become another form of pressure.
The leader has completed several deposits and now wants the team to release more trust than the current balance supports.
But employees determine when the account feels usable again.
The manager controls only the deposits.
You do not get to announce that trust has been rebuilt.
You do not get to decide that the team should have moved on.
You do not get to convert good intentions into immediate credit.
Your responsibility is simpler and harder:
Keep making accurate entries.
Let the balance move at the speed evidence allows.
Your Words Are Already on the Ledger
Every leader communicates from an account.
Some accounts carry a strong positive balance.
Some are approaching the line.
Some are already overdrawn.
The balance is not determined by how persuasive the leader sounds.
It is determined by the accumulated relationship between statements and reality.
After repeated layoffs, your account may have been charged for decisions you did not make.
That may not be fair.
It is still the account from which you are speaking.
You cannot repair it by explaining why the withdrawal should belong to someone else.
You cannot repair it with a larger promise.
You cannot repair it by disappearing until the team becomes less skeptical.
You repair it through debt service.
Small commitments.
Visible follow-through.
Appropriately sized language.
Bad news delivered directly.
Uncertainty named before it becomes contradiction.
The work is repetitive.
It offers little immediate recognition.
It may take longer than the original damage took to occur.
That is how credibility behaves.
Franklin wanted one meeting large enough to restore what two rounds had depleted.
What he eventually built was less dramatic.
An update that arrived.
A meeting that moved.
A question that received an answer.
A difficult fact communicated without delay.
A prediction resisted because it exceeded what he actually knew.
Roughly a year later, Franklin’s team did not trust him in the same effortless way it had before the first layoff.
The new trust was more deliberate.
Employees listened carefully.
They still verified important information.
They remained aware that Franklin did not control the organization.
But his words had regained weight.
Not because he had finally found the perfect speech.
Because he had stopped asking language to perform work only behavior could complete.
Your team may still like you.
They may respect your intentions.
They may understand that you did not make the decision.
The remaining question is more practical:
Do your words still help them decide what to do?
When the answer becomes no, credibility cannot be argued back into the relationship.
It must be deposited.
One visible, verifiable entry at a time.
Adapted from Twice Cut: Rebuilding Trust When the Layoffs Don’t Stop by Byron K. Veasey.
Available on Amazon:
https://www.amazon.com/dp/B0H8RQ4TN7
You Didn’t Make the Layoff Decision. So Why Does Your Team Experience You as Part of It?
Jul 17, 2026
Middle managers are expected to represent decisions they did not make, absorb reactions they cannot resolve, and keep delivering results while trust collapses around them. The way forward begins when leaders stop trying to control the entire situation and identify the narrow band of responsibility that is genuinely theirs.
This article is adapted from Chapter 5, “The Middle Position,” in Twice Cut: Rebuilding Trust When the Layoffs Don’t Stop. The chapter examines the difficult position occupied by managers who stand between executive decisions and the employees who must live with their consequences. It continues the narrative-driven format and practical leadership approach established in Article 3.
Terrence had a script by the second round of layoffs.
He did not think of it as a script.
He thought of it as leadership.
The organization had provided managers with approved talking points explaining why the restructuring was necessary. Market conditions had changed. Customer demand had shifted. The company needed to become more efficient, more focused, and better positioned for long-term growth.
Terrence understood the logic.
At least, he understood the version of the logic that had been shared with him.
He had not participated in the executive meetings where the final decisions were made. He had not selected the positions that would be eliminated. He had not seen every financial assumption behind the plan.
But he had been given enough information to explain the decision confidently.
So he did.
When an employee asked why one department had lost six people while another had lost only one, Terrence explained that the company had reviewed each function separately.
When someone asked why hiring had continued just weeks before the announcement, he said conditions had changed quickly.
When a senior employee questioned whether the reductions would actually solve the underlying problem, Terrence repeated that leadership had developed a sustainable operating model.
He believed most of what he said.
The parts he did not fully understand, he delivered with the confidence expected of a manager.
The meetings remained orderly.
Nobody raised their voice.
Employees returned to work.
From an operational perspective, Terrence believed he had handled the situation well.
Then the third round arrived.
This time, the team did not challenge him.
Nobody asked why the cuts were happening.
Nobody questioned the timing.
Nobody asked whether the restructuring was finally complete.
The questions had not been answered.
They had disappeared.
Terrence initially interpreted the silence as acceptance.
Perhaps the team had finally understood the business reality.
Perhaps people had become more resilient.
Perhaps his previous explanations had helped them recognize that these decisions were difficult but necessary.
Then he began noticing what the silence looked like outside the layoff meetings.
Employees who had once asked him for context began checking with people in other departments instead.
Potential problems reached him later.
Project plans became shorter.
Team members stopped asking what decisions meant for the next six months and concentrated only on what had to be completed that week.
Terrence had not persuaded the team.
He had taught them that asking him would not produce information they could safely use.
The script had ended the meetings.
It had also weakened the reason anyone would come to him with a real question.
When the third announcement arrived, Terrence made a different choice.
He stood in front of the team and said:
“Here is what I know. Here is what I do not know. I was not in the room where this decision was made, and there are parts of it I would not have chosen. I can explain what has been confirmed about our immediate work. I cannot tell you whether another round will happen, because I do not have information that would make that promise honest.”
Nobody thanked him.
Nobody visibly relaxed.
There was no sudden breakthrough.
But during the following weeks, something small changed.
An employee who had barely spoken to him since the second round asked a serious follow-up question about how a client responsibility would be reassigned.
It was not a question designed to expose a contradiction.
It was not a procedural request for proof.
It was a question that assumed Terrence might know something useful.
Terrence noticed it immediately.
The team was not trusting him again.
Not yet.
But someone had decided he might once again be worth asking.
The Position Nobody Applied For
Most managers leading teams through repeated layoffs did not create the conditions producing them.
They did not decide that growth projections had been too optimistic.
They did not approve the acquisition that failed to deliver.
They did not set the cost-reduction target.
They did not determine which roles would be eliminated.
Many managers learn about the decision only shortly before their teams do.
Sometimes the advance notice is measured in days.
Sometimes it is measured in hours.
Yet the manager still stands at the point where the decision becomes real.
An executive approves a workforce reduction in a distant meeting.
A spreadsheet identifies the positions.
Human resources prepares the process.
Legal reviews the language.
Communications approves the announcement.
Then a manager sits across from an employee whose mortgage, family plans, health insurance, and professional identity may be altered by what happens next.
The organization may understand the manager as a messenger.
The employee usually does not experience them that way.
To the employee, the manager is the visible face of the decision.
That may feel unfair.
It is also structurally predictable.
Most employees have no meaningful relationship with the executive committee.
They do not attend the meetings where tradeoffs are discussed.
They cannot ask the spreadsheet why one role remained and another disappeared.
They cannot challenge the financial model directly.
They can see their manager.
They can hear their manager’s words.
They can remember what their manager said after the previous round.
The manager becomes the interface between the institution and the person affected by it.
And interfaces are often experienced as the source.
Your Team Does Not Fully Separate You From the Decision
Managers frequently try to create distance between themselves and a decision they did not make.
They say:
“This came from above.”
“I found out when you did.”
“This was not my call.”
“I fought for the team.”
“You know I would never have chosen this.”
Some of those statements may be completely true.
But truth alone does not determine whether the statement helps.
When employees are frightened and angry, they are rarely evaluating the organizational chart.
They are evaluating whether the person in front of them can still be used as a reliable source of information, protection, and judgment.
A manager’s attempt to establish innocence may answer a question the team is not asking.
The team may already understand that the manager did not personally select every position.
Their concern is different.
What did the manager know?
When did they know it?
What did they say before the announcement?
Did they repeat assurances they could not verify?
Will they continue defending decisions they do not understand?
Will they tell the team when their information is incomplete?
Will they protect employees from the operational consequences where they can?
The question is not simply whether the manager caused the decision.
The question is what the manager will do from the position they occupy now.
This is the difficult reality of the middle position:
You are not the decision.
But your team will never experience you as entirely separate from it.
The more energy you spend proving that separation, the less energy remains for the responsibilities that are genuinely yours.
Three Demands Press on the Manager at Once
After repeated layoffs, the middle position creates three demands.
Each one is legitimate.
None can be completely satisfied.
1. Represent a decision you may privately disagree with
Managers are expected to communicate organizational decisions responsibly.
That does not mean they must personally agree with every choice.
It does mean they cannot openly sabotage the organization while continuing to lead inside it.
This creates a narrow line.
On one side is false ownership.
The manager speaks as though they designed the strategy, reviewed every option, and fully endorse the outcome.
They borrow certainty from the organization and present it as their own.
On the other side is public disownership.
The manager distances themselves so aggressively that employees are left with no leader at all.
They imply that senior leadership is incompetent, suggest that the decision makes no sense, or position themselves as another victim standing helplessly beside the team.
False ownership damages credibility because employees eventually discover that the manager’s confidence exceeded their knowledge.
Complete disownership damages stability because it tells the team that nobody in the room is willing or able to lead.
The useful position is neither defense nor abandonment.
It is honest representation.
The manager can explain what is known without claiming authorship.
They can acknowledge what they do not understand without undermining every decision.
They can say that a choice was made without pretending they would have made it the same way.
That may sound less authoritative than the traditional leadership script.
In a vigilant team, it is often more credible.
2. Absorb the team’s reaction
Employees need somewhere for their anger, fear, grief, and disbelief to go.
The manager is usually the nearest available surface.
A question about workload may carry anger about the layoffs.
A complaint about a deadline may actually be a protest against the organization’s priorities.
A challenge to the manager’s wording may be connected to something a different executive said six months earlier.
A normally measured employee may speak sharply.
Someone may quote the manager’s earlier reassurance back to them.
Another person may become silent in a way that feels more punishing than anger.
The manager absorbs all of it.
Knowing that the reaction is not entirely personal does not prevent it from feeling personal.
The words still reach the manager’s body.
The silence still fills the manager’s room.
The employee’s disappointment is still directed toward the person sitting in front of them.
Some managers defend themselves.
They explain that they did not know.
They describe how hard they fought.
They remind the team that managers are under pressure too.
Others absorb the reaction so completely that they begin treating every employee emotion as a problem they must solve personally.
Neither response works for long.
Defensiveness turns the team’s pain into a debate about the manager’s intentions.
Overabsorption turns the manager into an emotional container with no limit.
The manager’s responsibility is to receive the reaction without requiring the team to revise it immediately.
That is different from agreeing with every accusation.
It is also different from carrying every emotion home as a verdict on personal worth.
3. Keep delivering results
The work continues.
Customers still expect answers.
Projects still have deadlines.
Reports still must be completed.
Senior leadership still reviews performance.
In many organizations, the same team that lost people is expected to maintain the commitments established when those people were still employed.
The manager is therefore asked to do two kinds of work simultaneously.
They must lead through the emotional and trust consequences of the layoffs.
They must also produce operational results with fewer people and less attention.
Neither demand pauses for the other.
This is where many managers become trapped.
They believe the only way to protect the team is to personally absorb more work.
They attend more meetings.
They take over unfinished assignments.
They shield senior leadership from delivery risks because they do not want the remaining employees blamed.
They work longer hours to prevent the reduction from becoming visible in the output.
For a while, this can look like commitment.
Eventually, it hides the true cost of the decision.
The organization sees the same results with fewer people and concludes that the old staffing level was unnecessary.
The team sees the manager deteriorating and learns that survival requires unsustainable effort.
The manager becomes evidence against the capacity argument they should have been making.
Keeping the business moving is part of the job.
Making the consequences of reduced capacity invisible is not.
Why Trying Harder Does Not Resolve the Middle Position
Managers often respond to impossible conditions by increasing effort.
If employees distrust the decision, explain it more thoroughly.
If the team is angry, become more available.
If the workload is too large, work longer.
If results decline, push harder.
But the middle position is not an effort problem.
It is a boundary problem.
The manager is spending energy across three areas:
What was decided above them.
What the team directs toward them.
What they can actually do next.
Only the third area reliably converts effort into leadership value.
The decision itself may be outside the manager’s control.
The team’s emotional response may be outside the manager’s control.
The manager’s communication, follow-through, workload decisions, escalation, and daily treatment of employees are not.
This is the narrow band of leadership available inside the middle position.
It may feel small compared with everything pressing against it.
It is not insignificant.
It is the only area where the manager’s effort can consistently become evidence.
Why Defending the Decision Usually Backfires
Managers frequently defend decisions because they believe leadership requires alignment.
They worry that visible uncertainty will frighten the team.
They fear that acknowledging disagreement will make them appear disloyal.
They assume employees need a unified explanation.
So they take the organization’s rationale and strengthen it.
A statement that began as “This restructuring is expected to improve efficiency” becomes:
“This is the right decision for the business.”
An estimate becomes a conclusion.
A projection becomes a promise.
A strategy the manager did not design becomes a position they are expected to defend in detail.
This creates borrowed confidence.
Borrowed confidence feels useful in the moment because it makes communication cleaner.
The manager sounds decisive.
The meeting moves faster.
Questions are answered.
But borrowed confidence creates long-term exposure.
Employees remember who delivered the claim.
They rarely remember which executive presentation originally contained it.
If the prediction fails, the credibility loss settles on the manager who spoke with certainty.
That is what happened to Terrence.
His explanations were not necessarily dishonest.
They were simply more confident than his access justified.
Over time, employees recognized the gap.
He sounded like the source of the decision.
But he could not answer like someone who had actually made it.
The team eventually stopped testing the gap.
It routed around him.
Why Disowning the Decision Also Fails
Once managers realize that defending the decision is damaging, they may move to the opposite extreme.
They tell the team:
“I think this is a mistake too.”
“Leadership has no idea what this will do.”
“I tried to stop it.”
“There is nothing I can do.”
This may create temporary closeness.
Employees may appreciate hearing that their manager shares their frustration.
The manager may feel relief after dropping the corporate language.
But complete disownership creates a different credibility problem.
It asks employees to view the manager as powerless.
If the manager cannot influence the decision, cannot explain it, cannot protect the work, and cannot establish what happens next, employees may reasonably ask what leadership function remains.
The manager has joined the team emotionally but abandoned the position operationally.
Shared frustration is not the same as useful leadership.
Employees do not need the manager to pretend the decision was wise.
They also do not need another colleague narrating how little power anyone has.
They need someone who can identify the part that remains actionable.
The honest position may sound like this:
“I was not part of the final decision. I have concerns about the effect on our capacity, and I am documenting those concerns. The decision has been made. What I can influence now is how we reset priorities, which commitments we challenge, how responsibilities are reassigned, and how quickly I return with answers to the questions that remain open.”
That statement does not defend the decision.
It does not disown leadership responsibility.
It locates the manager accurately.
The Narrow Band You Actually Control
The manager cannot control everything the team wants changed.
But several important responsibilities remain fully within reach.
The boundary of your knowledge
You control whether you present an assumption as a fact.
You control whether you say “I know” when you actually mean “I expect.”
You control whether you promise an outcome that depends on people above you.
You control whether uncertainty is named clearly or covered with confident language.
This matters because employees are already trying to determine how much weight each statement deserves.
Helping them distinguish confirmed information from expectation is not a sign of weakness.
It reduces the amount of private interpretation they must perform.
A useful communication structure is:
What I know
The facts that have been confirmed and can be described precisely.
What I expect
The current working assumption, clearly labeled as an assumption.
What I do not know
Questions that remain open.
What I will do next
The action within the manager’s control, including when the team will receive another update.
This structure does not remove uncertainty.
It prevents uncertainty from being disguised as knowledge.
Your follow-through
Large promises are dangerous after repeated layoffs.
Small commitments become more important.
“I will send the revised priorities by Thursday.”
“I will ask whether the customer deadline can move.”
“I will return with an answer even if the answer is that no decision has been made.”
“I will schedule individual workload reviews this week.”
These commitments may appear minor compared with the organizational instability surrounding them.
That is precisely why they matter.
The team is not only evaluating the importance of the commitment.
It is evaluating whether the manager’s words still predict behavior.
Every completed follow-up reconnects those two things.
Every missed follow-up separates them further.
The workload you protect
A manager may not be able to restore eliminated positions.
They can refuse to pretend that the original workload still fits the reduced team.
They can identify what stops.
They can reduce scope.
They can challenge deadlines.
They can document capacity loss.
They can force a choice between resources and commitments rather than allowing employees to absorb both silently.
Workload protection is one of the most visible forms of post-layoff leadership because it changes the team’s lived conditions.
A manager who speaks compassionately but allows every old priority to remain has provided acknowledgment without protection.
A manager who removes two low-value reports, delays a nonessential project, and escalates a staffing risk has created evidence.
The action may not solve the larger problem.
It demonstrates that the manager sees the consequence and is willing to make it operationally visible.
The honesty of your position
You control whether you inflate your authority.
You also control whether you hide behind your lack of authority.
You can say:
“I did not make this decision.”
But the sentence cannot end there.
The useful continuation is:
“Here is what remains mine.”
That may include:
Communicating accurately.
Resetting priorities.
Protecting respectful treatment.
Escalating capacity risks.
Returning with answers.
Refusing to make promises unsupported by evidence.
Managing the work fairly.
The middle position becomes more sustainable when the manager stops measuring leadership by whether they can reverse the decision.
Leadership is measured by whether they use the authority that remains honestly and consistently.
Use a Control Inventory Before You Communicate
When a manager is overwhelmed, every problem begins to feel equally urgent and equally personal.
It helps to sort the situation before trying to solve it.
Create three columns.
Decided above me
Place organizational decisions here.
The number of positions eliminated.
The financial target.
The timing of the announcement.
The approved severance package.
The executive rationale.
Whether another restructuring will eventually occur.
These issues may deserve escalation or challenge.
But the manager should not confuse influence with control.
A decision can affect you deeply without belonging to you operationally.
Reactions I absorb
Place the team’s responses here.
Anger.
Silence.
Distrust.
Questions you cannot answer.
Disappointment directed toward you.
Skepticism about positive news.
Complaints about previous assurances.
These reactions are real information.
They should be heard.
But they cannot be forced into resolution.
You cannot require the team to trust faster.
You cannot make someone feel safe through managerial effort alone.
You cannot argue an employee out of the memory of what happened last time.
Actions actually mine
This is the working agenda.
What will you communicate?
What will you stop promising?
Which workload assumptions will you challenge?
What question will you escalate?
When will you follow up?
Which meeting can be canceled?
Which responsibility must be reassigned clearly?
Where is an employee carrying an unfair burden?
What can you make more predictable this week?
The first two columns explain the pressure.
The third column identifies the leadership.
This separation is not an attempt to become emotionally detached.
It is a way to stop spending finite energy on outcomes that effort alone cannot produce.
Do Not Ask the Team to Prove You Are Innocent
There is a subtle temptation in the middle position.
The manager wants the team to understand.
They want someone to say:
“We know this was not your fault.”
“We know you tried.”
“We know you are under pressure too.”
Sometimes employees will say those things.
They may even mean them.
But the manager cannot make that recognition a condition of leading well.
The team is already carrying the consequences of the decision.
It should not also be asked to manage the leader’s need for moral separation from it.
This does not mean managers should suppress every feeling.
They need somewhere to process anger, guilt, and uncertainty.
But that place may be a trusted peer, mentor, coach, therapist, partner, or private journal.
The team cannot become the primary audience for the manager’s defense.
When a manager repeatedly explains that the decision was not theirs, employees may begin feeling pressured to comfort them.
The direction of care reverses.
The people with less authority become responsible for reassuring the person with more.
That weakens the very leadership relationship the manager is trying to protect.
What Terrence’s New Sentence Actually Changed
Terrence did not gain access to executive decision-making before the third round.
He did not receive better information.
He did not suddenly agree with every part of the restructuring.
He did not obtain proof that another round would never happen.
The circumstances were largely the same.
His position inside them changed.
“Here is what I know” established the boundary of confirmed information.
“Here is what I do not know” removed the performance of certainty.
“I was not in the room where this decision was made” described his actual access.
“There are parts of it I would not have chosen” acknowledged distance without asking the team to join him in attacking leadership.
“Here is what I can tell you about what happens next” returned attention to the actions that were genuinely his.
“I cannot promise another round will not happen” prevented a new withdrawal from an already damaged credibility account.
Terrence did not become more powerful.
He became more precise.
That precision created a reason to ask him a question again.
The First Sign of Recovery May Be Disagreement
Managers often look for warmth as evidence that trust is returning.
They want meetings to feel lighter.
They hope employees will become more enthusiastic.
They watch for smiles, volunteering, and visible optimism.
Those signs may eventually appear.
They are not always the first ones.
The first sign may be an objection.
An employee challenges a project assumption.
Someone raises a risk early.
A team member asks a difficult question instead of checking privately with colleagues afterward.
A high performer explains why a deadline is unrealistic.
These moments can feel uncomfortable.
They are also evidence.
The employee has decided that speaking into the leadership relationship may once again produce value.
Silence protects the employee.
A real question creates exposure.
The person asking it is taking a small risk that the manager will respond honestly, act usefully, or at least avoid punishing the challenge.
Terrence’s employee did not tell him that trust had improved.
They asked him a question that required trust to be possible.
That was enough.
The Middle Position Is Not a Fairness Question
Managers can spend months asking whether it is fair that employees associate them with decisions made above them.
The answer may be no.
It may also be irrelevant to the work that follows.
The team experiences the organization through the manager.
That experience creates responsibility even when it does not create fault.
Responsibility and fault are not the same thing.
Fault looks backward and asks who caused the damage.
Responsibility looks forward and asks who can influence what happens next.
A manager can reject unfair blame without rejecting responsibility.
They can acknowledge:
“I did not create this situation.”
And still decide:
“I will lead accurately inside it.”
This is not accepting guilt for someone else’s decision.
It is accepting the reality of the position.
You are standing where decisions and consequences meet.
You cannot control the pressure coming from above.
You cannot control every reaction coming from below.
You can control what happens in the narrow band between them.
That is where your credibility will be judged.
Not by whether you explain the restructuring perfectly.
Not by whether the team immediately forgives the organization.
Not by whether you work hard enough to make reduced capacity invisible.
Your credibility will be judged by whether your words match your knowledge.
Whether your commitments predict your behavior.
Whether you make the workload honest.
Whether you describe your position without performance or escape.
Whether people who bring difficult information are safer after doing so.
Whether you become useful even before you become fully trusted.
Stop Trying to Win the Case
The middle manager often feels as though they are standing trial.
The team is the jury.
The organization supplied the evidence.
The manager’s previous statements are being quoted back.
Every new announcement feels like another opportunity to prove that they meant well.
But the objective is not to win the case.
You may never convince every employee that you handled the earlier rounds correctly.
You may never receive acknowledgment for the decisions you challenged privately.
You may never be able to explain everything you knew or did not know at the time.
Trust will not return because the team finally accepts your defense.
It will return, if it returns, because your current behavior becomes consistently usable.
Terrence’s team did not need a better explanation of his intentions.
It needed a more accurate experience of his leadership.
That experience began when he stopped borrowing confidence from decisions he did not own.
It continued when he stopped asking the team to treat him as separate from the organization.
He accepted the middle position without pretending it was fair.
Then he led from the part of it that was actually his.
The result was not immediate loyalty.
It was a question.
A real one.
That question meant an employee had allowed Terrence’s answer to matter again.
After repeated layoffs, that is not a small development.
It is the beginning of restored usefulness.
And usefulness often returns before trust has a name.
You may not have made the decision.
You may disagree with it.
You may have warned against it.
Your team may still experience you as part of it.
The leadership question is no longer whether that is fair.
It is whether you will exhaust yourself defending what is not yours, abandon the position because you did not choose it, or work honestly inside the narrow band that remains.
The decision came from above.
The reaction is coming from below.
Your leadership lives between them.
That is the middle position.
You did not apply for it.
But now that you are standing there, accuracy matters more than innocence.
Adapted from Twice Cut: Rebuilding Trust When the Layoffs Don’t Stop by Byron K. Veasey.
Available on Amazon:
https://www.amazon.com/dp/B0H8RQ4TN7
About the Author
Byron K. Veasey is a career strategist and leader in data quality engineering focused on helping professionals navigate job searches, burnout, and career reinvention.
He writes Career Strategies, a Substack newsletter read by over 4,900 professionals navigating today’s evolving job market.
👉 Subscribe to Career Strategies