13. Adapt the Frame, Never the Truth¶
The CEO came down on it directly.
The business wanted the product to move faster. The pressure landed on me, and the message underneath it was simple: engineering needs to work harder.
That was not the truth.
The truth was that the app had real tech debt. Ownership inside the product was unclear. UX support was thin. Too many business requests were competing for the same week of capacity. Pushing harder on top of that system would not produce speed. It would produce rework, bugs, and a team that lost trust in its own roadmap.
That truth had to go to three audiences in the same week. The CEO. The tech team. The business stakeholders.
Same truth. Three different doors.
To the CEO, I did not lead with "the team is overloaded." A CEO under pressure does not buy defensive. I framed it as a decision: "We can move faster, but we have to be aggressive in the right way. The risk is not only timeline. The bigger risk is shipping unstable work, or rebuilding the same thing twice because we did not fix the root cause. So we cut scope, define ownership, and move in phases."
The CEO needed trade-offs and a decision frame. Not workload. Not feelings.
To the tech team, I did not say "leadership is pushing us again." Resentment turns into hidden blockers later. I told them: "I will handle the pressure upward. But internally we need more discipline. Clear estimates. Early escalation. No hidden blockers. No vague updates. If something is risky, raise it now. I can protect the team from unfair blame. I cannot protect unclear ownership."
The team needed two things at once. Protection from above. Standards from within. One without the other does not work.
To the business stakeholders, I did not expose the internal mess. Tech debt, capacity issues, unclear ownership — in raw form, that does not earn credibility. It loses it. Stakeholders do not want to manage another team's internal problems. They want to know what to expect. So I said: "We are handling this in phases to reduce disruption. The first priority is stabilizing the current experience. Then we release improvements step by step. I will share what changes now, what changes later, and what trade-offs we are accepting."
They needed managed expectations and a continuity story. Not internal dirty laundry.
The CEO trusted the plan. The team moved. The stakeholders waited for results. That bought enough buffer to actually execute. The technical problem stayed a technical problem. It did not turn into a political problem on top of a technical problem.
What bad leadership usually does¶
Most leaders do one of two things in this situation.
The first move is one frame, everywhere. The same deck, the same language, the same emphasis goes to the CEO, the team, and the stakeholders. Then the leader wonders why the CEO is confused, the team is disengaged, and the stakeholders are anxious. They are not difficult people. They are different audiences hearing a message that was not built for any of them.
The second move is worse. The leader changes the truth instead of the frame.
Severity gets softened for the CEO, because the CEO is intimidating. Business implications get hidden from the team, because the leader does not want to deal with the reaction. Stakeholders get kept vague, because clarity would invite questions the leader does not want to answer.
Both failures share the same root. The leader is communicating for their own comfort, not for the audience's understanding.
That is not honesty. That is convenience dressed as honesty.
The principle¶
Adapt the frame. Never the truth.
Hold the facts constant. Change the entry point.
Why it matters¶
Different audiences hear differently. Not because they are difficult. Because their role, their context, and what they care about are different.
A CEO is making capital and priority decisions. A tech lead is making implementation and trade-off decisions. A business stakeholder is making expectation and timeline decisions. The same fact lands differently depending on which decision the person is sitting in front of.
A leader who refuses to adapt to that is not being more honest. They are being less useful. The truth is the same, but it does not reach anyone in a form they can act on.
And when the truth does not reach people in usable form, they fill the gap themselves. The CEO assumes the team is slow. The team assumes leadership is unrealistic. The stakeholders assume the product is unreliable. Each audience builds a private version of reality, and the leader ends up managing the gap between three stories instead of solving the one problem underneath them all.
What better leadership looks like¶
Stay rigidly honest on the facts. Be deliberately flexible on the framing.
Before each conversation, the move is the same. What does this audience need to understand? And what is the entry point that will actually get them there?
The truth does not shift. The emphasis does. The vocabulary does. The level of detail does.
The point is not to be all things to all people. The point is to make the truth land.
The ethical boundary — load-bearing¶
This principle lives one step away from manipulation. The line must be clear.
Framing is legitimate. Different entry points to the same truth.
Manipulation is not. Changing facts. Omitting material information. Softening severity to protect yourself. Creating a different impression in different rooms.
The test is simple. If the audience would feel deceived once they had the full information, the line was crossed.
A sharper version of the same test, for the moment of writing the message: if the omitted detail would change what the audience chooses, it is not framing. It is concealment. Material risk has to reach the people whose decision depends on it, in language they can act on. Sparing them the raw mess is framing. Sparing them the consequence is something else.
The CEO in my story got a "speed with control" frame. Not an "everything is under control" lie. If the CEO had walked into the engineering room and heard the team's version, nothing would have contradicted what I had said upstairs. The emphasis was different. The facts were the same.
The most common slip on this principle is upward. It is easier to stay honest with a team that reports to you than with a CEO who can fire you. Power pulls the framing toward self-protection. That is where leaders quietly cross the line and call it "managing up."
The standard applies upward too. If anything, it applies harder upward.
Change the language. Never the truth.
The tool — audience-to-focus map¶
Before any high-stakes message, force yourself through one pass:
- CEO / senior leadership — business impact, risk, decision needed.
- Tech team — root cause, trade-offs, ownership, what discipline is required internally.
- Business stakeholders — user-facing consequence, timeline, what to expect and what to hold off on.
- External partner — facts, accountability, the next concrete step.
- Junior team member — context first, then instruction, then expectation.
Same situation. Five doors. The fact base behind each door is identical. The first sentence behind each door is not.
Write your opening line for each audience before you send anything. If the opening lines contradict each other on facts, you are not framing. You are spinning.
Simple rules¶
- Hold the facts constant across every audience.
- Change the entry point, the vocabulary, and the level of detail.
- Lead with the decision the audience needs to make, not the explanation that is easiest for you to give.
- Never soften severity upward to protect yourself.
- Never expose internal mess downward or sideways just to look transparent.
- Apply the deception test before every important message: would this audience feel misled if they heard the full picture?
- If you cannot put all your framings in one room without contradicting yourself, rebuild the message.
Reflection questions¶
- In my last important message, did I change the frame or did I change the facts?
- If the three audiences I spoke to this week compared notes, would anything contradict?
- When I framed something for a CEO, was I making the truth land — or was I protecting myself from a hard conversation?
- Did I expose internal problems to a stakeholder because it was useful to them, or because it was easier for me?
- What did I leave out of my last update, and would the audience feel deceived if they found out later?
A short admission¶
I did not learn this in a leadership course. I learned it as a child. Talking to my parents needed one frame. Talking to my teachers needed another. Talking to my grandparents needed a third. The truth did not change. The way I had to deliver it did, or the person could not actually hear it. By the time I sat in the operator's chair, it was already instinct.
Reminder¶
Change the language. Never the truth.