What Your CTO Is Not Telling You About the Engineering Team
At some point in the past 12 months, something happened in your engineering organisation that you found out about later than you should have.
A key engineer who was quietly considering leaving. A technical debt problem that had been accumulating for months before it surfaced as a delivery crisis. A team dynamic that the CTO had been managing at their level without escalating because they believed they were handling it. You found out when the problem became undeniable, not when it became manageable.
This is not a personal failure, yours or your CTO’s. It is a structural feature of the relationship between a technical CTO and a non-technical CEO, and it costs Nigerian startups significant money and time because neither party has a clear incentive to name it directly.
The problem is information asymmetry. And trust, as comfortable as it is, does not eliminate it. It simply makes it more comfortable to live with.
The Asymmetry Is Structural, Not Personal
A CTO who reports to a non-technical CEO holds specialised knowledge that their manager cannot independently evaluate. They are the only person in the leadership conversation who knows, with real precision, whether the engineering team can build what the roadmap requires, whether the technical debt has accumulated to a dangerous level, whether the senior engineers are genuinely motivated or quietly preparing to leave, and whether the architecture decisions being made today are creating problems that will surface in 18 months.
Most CTOs do not withhold this information deliberately. They filter it: translating technical reality into business language, managing up the way any leader does, calibrating how much complexity the CEO can absorb and act on, and sometimes protecting the team or themselves from scrutiny they believe would be unproductive.
The result is that the CEO’s understanding of the engineering organisation is systematically incomplete. Not because the CTO is dishonest, but because the information translation between technical reality and executive communication is inherently lossy, and the CEO has no independent means of verifying what is lost in translation.
This is the structure of most non-technical founder and CTO relationships in Nigerian tech. It does not require dishonesty or dysfunction to produce significant blind spots. It only requires the normal incentives of a manager communicating upward to a stakeholder who cannot independently verify what they are being told.
The Questions That Surface What You Are Not Being Told
Non-technical founders who want to close this gap do not need to become engineers. They need to ask different questions: ones that are harder to answer with reassuring generalities.
Most founders do not ask these questions because they feel like expressions of distrust. They are not. They are the questions that allow a CTO to surface difficult truths in a context that frames those truths as useful information rather than failures to be defended against.
“What is the biggest architectural decision we made in the last six months that you would make differently if you were starting again?” A CTO who cannot answer this question has either not been making architectural decisions with appropriate self-reflection, or is not comfortable being honest about technical debt with their CEO. Either answer is informative.
“If you had to reduce the engineering team by 30% tomorrow, who would you keep and why?” This question reveals the CTO’s actual assessment of team capability, the gap between the official team picture and the real one. It also reveals whether the team has critical dependencies on specific individuals that create operational risk.
“What would it take for our two best engineers to leave in the next six months?” This forces an honest conversation about retention risk: the salary gaps, the growth ceiling frustrations, the management dynamics, and the international recruitment attention that the CTO may be managing quietly without surfacing to the CEO.
“What is the thing about our technical architecture that our most senior engineers complain about most?” The answer reveals both the actual state of the codebase and the degree to which the CTO is in genuine dialogue with their team, rather than managing upward a version of the team that is more cohesive than the reality.
The Three Gaps That Appear Most Often
In Nigerian tech companies specifically, three categories of information tend to be under-communicated between CTOs and non-technical founders.
1. Technical debt accumulation.
Every fast-moving startup accumulates technical debt. The question is whether the CEO has an accurate picture of how much, where it lives, and when it will demand attention. The standard communication pattern is that technical debt is acknowledged in general terms and rarely surfaced with the specificity needed for the CEO to make informed resourcing decisions. The CEO discovers its magnitude when a feature that should take three weeks takes three months, and by then the debt is a crisis rather than a managed liability.
2. Senior engineering retention risk.
The CTO is usually aware, earlier than anyone else, when a key engineer is becoming disengaged: arriving later, contributing less in architecture discussions, receiving LinkedIn messages they used to ignore. This information is rarely escalated because the CTO is trying to resolve it at their level, which is appropriate, but it means the CEO has no visibility into retention risk until it becomes a resignation.
3. Team capability variance.
Most CTOs maintain an internal assessment of their engineers that is more differentiated than the picture they present to the CEO. The “strong team” the CEO believes they have may contain two or three engineers who are genuinely excellent, several who are competent, and one or two who the team is quietly working around. The CEO who believes the team is uniformly strong will make different and worse resourcing decisions than the CEO who has the accurate, differentiated picture.
Building a Better Information Channel
The solution is not to become technical. It is to create structures that give the CEO access to signal that is not fully mediated by the CTO.
Regular skip-level conversations with senior engineers, not management conversations but genuine curiosity about what they are building and what is getting in the way, surface information that does not travel up through the CTO. Periodic external technical reviews from trusted advisors who can speak candidly about architecture and team health provide an independent perspective. Metrics that are owned at the engineering level and reviewed at the CEO level, not vanity metrics but substantive indicators of delivery velocity and system health, create a conversation grounded in data rather than narrative.
None of this is a substitute for a CTO relationship built on genuine trust. But trust does not eliminate information asymmetry. It simply makes the asymmetry more comfortable to live with, which is not the same as making it less costly.
The Bottom Line
The gap between what your CTO knows about your engineering organisation and what you know is not a personal failure. It is a structural feature of the relationship. Closing it requires asking better questions, creating independent signal channels, and building a culture where difficult technical truths are surfaced as useful management information rather than filtered out of the executive conversation to maintain confidence.
The founder who manages only what they are told manages the wrong map. The founder who builds the structures to see the real one makes better decisions in the months before a problem becomes a crisis.
When you need an independent assessment of your technical team’s capability and structure, or when engineering roles need to be filled with people you can trust, Revent Technologies provides vetted technical talent with transparent assessment frameworks.
Start here: www.reventtechnologies.com/site/hire-a-developer
Research Sources
– Harvard Business Review: Information asymmetry between technical and non-technical leadership
– McKinsey & Company: Engineering team health and leadership communication in technology organisations
– Cogn-IQ: Affinity bias and evaluation accuracy in leadership assessment
– Techpoint Africa: Nigerian tech leadership and engineering team dynamics 2025