Your First Moves as CTO: Turn Narratives Into Clarity
How to turn uncertainty into shared clarity in your first weeks.
Ivan Peralta
Engineering
Mar 16, 2026
The Honeymoon Window
When I join a company as CTO (or VP Engineering), I always feel the same pressure in the first weeks: my credit is limited. I was hired for a reason, and people expect movement. But I also can’t afford fast, misinformed decisions. The problem is simple: I don’t get the time required to understand 100% of reality before I’m asked to act.
And the moment I start listening, I hear multiple “truths” at once. Founders feel engineering is too slow. Product feels friction everywhere. Finance questions cost and headcount. Sales can’t close a deal without one more feature. Engineering feels whiplash from shifting priorities, underinvestment in tools, and chronic overwork. Is everyone wrong? Probably. Is everyone right? Also probably—partially. The hard part is turning all those perspectives into a coherent diagnosis, fast.
Then there’s the human factor. I’ve walked into organizations where the previous leader was downgraded or removed. Psychological safety is fragile. People are cautious. Some test you, others disappear. Even when the team is supportive, they can only share what they’ve lived—and their view is shaped by their layer, incentives, and scars.
So how do you navigate this high-uncertainty moment without burning trust on one avoidable wrong move? And how do you “turn the lights on” quickly—so decisions are grounded in evidence, not only conversations?
What You’re Actually Optimizing For
In this period, your real KPI isn’t “shipping more.” It’s time-to-truth without breaking trust. You need to see reality fast enough to make decisions, while keeping the org calm enough to keep operating.
That means resisting two failure modes:
Action too early: you “fix” the wrong thing, and lose credibility.
Learning too slow: you look thoughtful, but stakeholders conclude you’re not driving.
The goal is a minimum viable diagnosis: a defensible view of what’s happening, what matters most, and what you will not change yet. Not perfect. Just solid enough that your next move is directionally right, and fast enough to matter.
Back to the 5 Key Questions
The danger isn’t that people lie. It’s that you start leading based on the most persuasive story instead of the most testable truth.
So treat narratives as inputs, not conclusions. Capture what each group believes, then translate it into a small set of verifiable questions. That’s how you move fast without gambling your credibility.
I keep coming back to five questions because they force clarity without pretending the world is simple:
Do we have the right team?
Do we get the best from them? (efficiency, leverage, friction)
Are we working on the right problems? (alignment, bets, tradeoffs)
Are we reliable? (quality, rework, operational load)
Are we getting any better? (trends, momentum, compounding change)
Don’t debate narratives. Convert them into hypotheses. If you can’t map an opinion to a question you can verify, it remains a story—and stories are a risky foundation for early executive decisions.
Your first job is translation: from narratives to testable hypotheses.
Turning the Lights On
A visibility layer is how you shorten the path from “I’m hearing a lot” to “I’m confident enough to act.”
It doesn’t replace conversations. It pressure-tests them. It helps you answer: Which narratives are directionally correct? Which are local truths? Which are outdated?
For this to work, the layer must stay “healthy.” That’s less about tooling and more about posture:
focus on teams, workflows, and systems (not individuals)
be transparent about what’s being observed and why
use it for diagnosis and improvement, not judgement
Used well, it accelerates trust because decisions become explainable. People might not love the tradeoff you make, but they can see why you made it.
Answer the questions with evidence
When you walk into a new org, you’ll hear strong opinions fast. Visibility is what lets you respond with: “I hear you, let’s validate what’s true.”
1. Do we have the right team?
Forget raw talent for a moment. The real question is: can this organization deliver without being dependent on a few people? If outcomes depend on one or two people, you’re exposed. If ownership is unclear, accountability becomes politics. And if collaboration is noisy, you’ll spend months “restructuring” what is really a coordination problem.
A few signals make this visible quickly: ownership concentration, talent density, and how work flows across teams. You also start seeing the “lighthouses”: the people and teams others naturally orbit to get things done. That’s not a ranking. It’s a map of where the org actually holds together.
2. Do we get the best from them?
In most companies, the bottleneck isn’t effort. It’s friction.
“You can feel it in long cycles, stalled initiatives, slow reviews, constant context switching, and the silent tax of rework. And now there’s an additional amplifier: AI adoption. Not because AI is trendy, but because it’s a leverage and cost signal. If your org is paying for AI tools but not translating them into net contribution (more output with stable quality), you’re not getting leverage — you’re paying for activity.”
So the question becomes: are we converting capacity into value, or into churn? Baselines help here—both your own history and external references—because “we’re slow” is meaningless until you can say where and why.
3. Are we working on the right problems?
This is where onboarding gets uncomfortable: you’re not only asked to align to strategy, you’re also expected to challenge it.
Visibility helps you see where effort truly goes beyond what the roadmap claims. You can separate investment into the main bets from “invisible work”: KTLO, maintenance, operational load, architectural bottlenecks, and shadow projects that exist because the platform can’t support what the business wants.
Often the real story isn’t misalignment by intent. It’s misalignment by constraints.
4. Are we reliable?
Most teams think they have a delivery problem. Then you discover they actually have a rework loop: bugs, follow-ups, hotfixes, incident work, recurring firefights that drain planned capacity. Once you see the pattern, you can quantify the quality tax without blaming anyone.
AI makes this sharper: if AI increases throughput but quality degrades, you don’t get leverage, instead you get acceleration into rework. The framing stays simple: are we using speed to reduce pressure, or to create more of it?
5. Are we getting any better?
The most important signal isn’t where you are versus “world class.” It’s whether the system is improving or decaying.
Trends cut through posturing. Improvements that stick matter more than one good month. And when you can make progress visible—even small steps—you build trust because people can see the path forward is real, not rhetorical.
What changes in the conversations (this is the real payoff)
This is what “turning the lights on” looks like in practice: less debate, more shared reality.
“Engineering is slow” becomes “A meaningful share of capacity is being consumed by interrupts and rework and here are the drivers.”
“Tech debt is killing us” becomes “The quality tax concentrates here, and it costs us this each week.”
“We need more headcount” becomes “Here’s the constraint; adding people won’t help unless we reduce X first.”
“Priorities are clear” becomes “Here’s where effort actually went versus what we said mattered.”
You don’t win because you have charts. You win because early decisions feel grounded, fair, and explainable, especially when the org is still deciding whether to trust you.
Closing: Earn Trust Faster by Reducing Guesswork
This transition isn’t about proving you’re the smartest person in the room. It’s about proving you can find the truth, make tradeoffs, and move the organization forward without breaking trust.
Conversations will always be necessary. But when they’re your only input, you’re forced to bet your credibility on incomplete stories.
A visibility layer enables inspected trust: you listen first, measure the system, and then decide with evidence. In the first 90 days, that difference is material—fewer avoidable mistakes, faster alignment, and trust built on reality.
If you’re stepping into a new CTO/VP Engineering role and want fact-based visibility early—delivery signals, alignment, talent density, collaboration, reliability, trends—Pensero can be your partner to help you turn uncertainty into a clear, defensible diagnosis without turning measurement into surveillance.
If you’ve ever tried to understand your team through data — and felt the frustration of doing it with spreadsheets, or with tools that only rely on ticket lifecycles or member surveys, without getting a holistic and factual view — stay tuned. We’re building something for you.
And if you want to join a blue-ocean opportunity — and help shape how engineering teams navigate this new technology age — check out our careers page.
The Honeymoon Window
When I join a company as CTO (or VP Engineering), I always feel the same pressure in the first weeks: my credit is limited. I was hired for a reason, and people expect movement. But I also can’t afford fast, misinformed decisions. The problem is simple: I don’t get the time required to understand 100% of reality before I’m asked to act.
And the moment I start listening, I hear multiple “truths” at once. Founders feel engineering is too slow. Product feels friction everywhere. Finance questions cost and headcount. Sales can’t close a deal without one more feature. Engineering feels whiplash from shifting priorities, underinvestment in tools, and chronic overwork. Is everyone wrong? Probably. Is everyone right? Also probably—partially. The hard part is turning all those perspectives into a coherent diagnosis, fast.
Then there’s the human factor. I’ve walked into organizations where the previous leader was downgraded or removed. Psychological safety is fragile. People are cautious. Some test you, others disappear. Even when the team is supportive, they can only share what they’ve lived—and their view is shaped by their layer, incentives, and scars.
So how do you navigate this high-uncertainty moment without burning trust on one avoidable wrong move? And how do you “turn the lights on” quickly—so decisions are grounded in evidence, not only conversations?
What You’re Actually Optimizing For
In this period, your real KPI isn’t “shipping more.” It’s time-to-truth without breaking trust. You need to see reality fast enough to make decisions, while keeping the org calm enough to keep operating.
That means resisting two failure modes:
Action too early: you “fix” the wrong thing, and lose credibility.
Learning too slow: you look thoughtful, but stakeholders conclude you’re not driving.
The goal is a minimum viable diagnosis: a defensible view of what’s happening, what matters most, and what you will not change yet. Not perfect. Just solid enough that your next move is directionally right, and fast enough to matter.
Back to the 5 Key Questions
The danger isn’t that people lie. It’s that you start leading based on the most persuasive story instead of the most testable truth.
So treat narratives as inputs, not conclusions. Capture what each group believes, then translate it into a small set of verifiable questions. That’s how you move fast without gambling your credibility.
I keep coming back to five questions because they force clarity without pretending the world is simple:
Do we have the right team?
Do we get the best from them? (efficiency, leverage, friction)
Are we working on the right problems? (alignment, bets, tradeoffs)
Are we reliable? (quality, rework, operational load)
Are we getting any better? (trends, momentum, compounding change)
Don’t debate narratives. Convert them into hypotheses. If you can’t map an opinion to a question you can verify, it remains a story—and stories are a risky foundation for early executive decisions.
Your first job is translation: from narratives to testable hypotheses.
Turning the Lights On
A visibility layer is how you shorten the path from “I’m hearing a lot” to “I’m confident enough to act.”
It doesn’t replace conversations. It pressure-tests them. It helps you answer: Which narratives are directionally correct? Which are local truths? Which are outdated?
For this to work, the layer must stay “healthy.” That’s less about tooling and more about posture:
focus on teams, workflows, and systems (not individuals)
be transparent about what’s being observed and why
use it for diagnosis and improvement, not judgement
Used well, it accelerates trust because decisions become explainable. People might not love the tradeoff you make, but they can see why you made it.
Answer the questions with evidence
When you walk into a new org, you’ll hear strong opinions fast. Visibility is what lets you respond with: “I hear you, let’s validate what’s true.”
1. Do we have the right team?
Forget raw talent for a moment. The real question is: can this organization deliver without being dependent on a few people? If outcomes depend on one or two people, you’re exposed. If ownership is unclear, accountability becomes politics. And if collaboration is noisy, you’ll spend months “restructuring” what is really a coordination problem.
A few signals make this visible quickly: ownership concentration, talent density, and how work flows across teams. You also start seeing the “lighthouses”: the people and teams others naturally orbit to get things done. That’s not a ranking. It’s a map of where the org actually holds together.
2. Do we get the best from them?
In most companies, the bottleneck isn’t effort. It’s friction.
“You can feel it in long cycles, stalled initiatives, slow reviews, constant context switching, and the silent tax of rework. And now there’s an additional amplifier: AI adoption. Not because AI is trendy, but because it’s a leverage and cost signal. If your org is paying for AI tools but not translating them into net contribution (more output with stable quality), you’re not getting leverage — you’re paying for activity.”
So the question becomes: are we converting capacity into value, or into churn? Baselines help here—both your own history and external references—because “we’re slow” is meaningless until you can say where and why.
3. Are we working on the right problems?
This is where onboarding gets uncomfortable: you’re not only asked to align to strategy, you’re also expected to challenge it.
Visibility helps you see where effort truly goes beyond what the roadmap claims. You can separate investment into the main bets from “invisible work”: KTLO, maintenance, operational load, architectural bottlenecks, and shadow projects that exist because the platform can’t support what the business wants.
Often the real story isn’t misalignment by intent. It’s misalignment by constraints.
4. Are we reliable?
Most teams think they have a delivery problem. Then you discover they actually have a rework loop: bugs, follow-ups, hotfixes, incident work, recurring firefights that drain planned capacity. Once you see the pattern, you can quantify the quality tax without blaming anyone.
AI makes this sharper: if AI increases throughput but quality degrades, you don’t get leverage, instead you get acceleration into rework. The framing stays simple: are we using speed to reduce pressure, or to create more of it?
5. Are we getting any better?
The most important signal isn’t where you are versus “world class.” It’s whether the system is improving or decaying.
Trends cut through posturing. Improvements that stick matter more than one good month. And when you can make progress visible—even small steps—you build trust because people can see the path forward is real, not rhetorical.
What changes in the conversations (this is the real payoff)
This is what “turning the lights on” looks like in practice: less debate, more shared reality.
“Engineering is slow” becomes “A meaningful share of capacity is being consumed by interrupts and rework and here are the drivers.”
“Tech debt is killing us” becomes “The quality tax concentrates here, and it costs us this each week.”
“We need more headcount” becomes “Here’s the constraint; adding people won’t help unless we reduce X first.”
“Priorities are clear” becomes “Here’s where effort actually went versus what we said mattered.”
You don’t win because you have charts. You win because early decisions feel grounded, fair, and explainable, especially when the org is still deciding whether to trust you.
Closing: Earn Trust Faster by Reducing Guesswork
This transition isn’t about proving you’re the smartest person in the room. It’s about proving you can find the truth, make tradeoffs, and move the organization forward without breaking trust.
Conversations will always be necessary. But when they’re your only input, you’re forced to bet your credibility on incomplete stories.
A visibility layer enables inspected trust: you listen first, measure the system, and then decide with evidence. In the first 90 days, that difference is material—fewer avoidable mistakes, faster alignment, and trust built on reality.
If you’re stepping into a new CTO/VP Engineering role and want fact-based visibility early—delivery signals, alignment, talent density, collaboration, reliability, trends—Pensero can be your partner to help you turn uncertainty into a clear, defensible diagnosis without turning measurement into surveillance.
If you’ve ever tried to understand your team through data — and felt the frustration of doing it with spreadsheets, or with tools that only rely on ticket lifecycles or member surveys, without getting a holistic and factual view — stay tuned. We’re building something for you.
And if you want to join a blue-ocean opportunity — and help shape how engineering teams navigate this new technology age — check out our careers page.
