Are you running a tech company or a tech museum?
Twelve questions that reveal whether your technology estate is building forward or preserving the past. The maturity assessment every CEO should run.
The difference between a tech company and a tech museum has nothing to do with the age of the systems. The fastest-moving organizations in the world run on infrastructure that is years old; the most paralyzed run on systems built months ago that already exceed anyone’s ability to understand or change. The separating factor is posture: whether the organization controls its technology or the technology controls the organization.
This assessment tells you which one you are.
The 12 questions
Answer each question based on what is actually true in your organization today, not on what you aspire to.
1. Can your team ship a meaningful product change in a week?
A meaningful product change means a new feature, a significant improvement, or a customer request going from decision to production in five business days. Hotfixes and copy edits do not count. If the answer is yes, reliably and without heroics, that is a signal of a functioning organization. If the answer is “it depends,” “sometimes,” or “only for small things,” that is also an answer.
2. When something breaks at 2am, how many people get called?
The healthy answer is one or two people following a documented runbook, who resolve the issue and go back to sleep. A chain of phone calls until someone reaches the person who actually understands the system, followed by an undocumented investigation that runs until morning, is the museum answer. The number of people required to handle an incident measures directly how well the system is understood.
3. Can your three most recently hired engineers describe how your core product works?
The test is operational: where data enters, how it moves, what depends on what, what breaks if a specific component fails. If engineers hired in the past six months cannot answer this without asking someone who was there when the system was built, the knowledge is concentrated in the wrong places.
4. Do you know, right now, how many SaaS tools your company is paying for?
The exact number, the annual total, and the renewal dates, without estimating or delegating to finance. Organizations where the answer is readily available are managing their estate. If the answer requires two weeks and a finance audit, the shadow stack is already larger than you know.
5. Has your architecture changed meaningfully in the past two years?
The question asks about meaningful architectural change: a component rebuilt, a dependency removed, a system replaced, a pattern deprecated. Incremental updates and patches do not qualify. Organizations that are building forward make architectural changes. Organizations that are preserving the past maintain what exists and defer changes that feel risky. Deferral is how museums are built.
6. When a key engineer leaves, what breaks?
This is the bus factor question. If the honest answer is “we’d have real problems,” name the systems. If you cannot name them, nobody has asked the question before. Both answers indicate the same underlying condition: knowledge that has never been mapped, documented, or distributed.
7. What percentage of your engineering team’s time goes to maintenance versus new development?
If you know this number, you are managing it. If you have to estimate it, you are not. Organizations where maintenance consumes more than 40% of engineering capacity are in a structural deficit: the estate is demanding more than the team can invest in forward progress. Deloitte’s 2026 Global Technology Leadership Study puts technical debt at 21 to 40% of IT spending. The organizations at the high end of that range are spending on preservation rather than creation.
8. Can a non-engineer update your website’s content without filing a ticket?
This is a content platform question and an organizational architecture question. If the marketing team requires developer time to change a headline, that signals where the technical dependencies are and who controls what. Organizations that have resolved this dependency have separated concerns correctly; the rest pay a developer tax on every content change.
9. Are your vendor contracts actively managed or passively renewed?
Actively managed means someone knows when each significant contract renews, has evaluated whether it is still the right tool, and negotiates rather than accepts the renewal price. Passively renewed means the invoice arrives, finance approves it, and the same tools continue for another year regardless of whether they are being used or whether better alternatives exist.
10. Do you have a plan for AI, or do you have a slide about AI?
A plan specifies which workflows AI will change, the infrastructure those workflows require, an owner, and a timeline. A slide has the word “AI” next to strategic priorities with a budget number unconnected to any specific initiative. The difference matters because legacy systems are routinely the thing that stalls AI adoption, and identifying which legacy systems are in the way requires engagement with specifics that a slide cannot provide.
11. When was the last time a system was decommissioned?
The question asks about permanent decommissioning: turned off, contract cancelled, infrastructure deprovisioned. Upgrades and migrations do not qualify. Organizations that regularly decommission systems are managing their estate with intention. Organizations that only add and never remove are building museums one exhibit at a time.
12. If your CTO left tomorrow, would the board know what questions to ask?
The specific questions about the estate itself: what is in production, what it costs, what the critical dependencies are, what would break and when. Organizations where the board has this visibility are running technology as a managed asset. Organizations where the board would have to start from scratch are running technology as a black box, and the risk embedded in that black box is invisible until it surfaces at the worst possible moment.
Your score
Count the questions where your honest answer reflects a functioning, forward-moving organization. Then find your tier.
10 to 12: Workshop or studio
Your organization treats technology as infrastructure that serves the business. Systems are understood, estates are managed, and architectural change is routine rather than exceptional. The risk at this level is complacency: the posture that got you here requires ongoing investment to maintain. The highest-leverage question is whether your current posture is investment or maintenance; run this assessment again in six months.
7 to 9: Library
You have most of the foundations but specific gaps. The questions you answered unfavorably point to the highest-leverage areas for investment. A library knows what it has, organizes it reasonably well, and serves its users, but it is not building new things. The gap between library and workshop is usually organizational: a handful of specific decisions about ownership, documentation, and architectural intent. Pick the two or three questions where your answer was weakest and start there.
4 to 6: Reading room
The organization has functional technology that largely works, but control is partial and understanding is uneven. Knowledge is concentrated in specific people, vendor relationships are more passive than active. Architectural change is deferred more often than it happens, the reading room is the most common place for mid-market organizations to be, and it is a manageable condition with a known set of interventions. The most important first step is a dependency map: what the estate actually contains, who understands it, and what the highest-risk concentrations are.
0 to 3: Museum
The organization is maintaining exhibits rather than building products. The estate is understood by a small number of people, expensive to operate, resistant to change, and structurally unable to support the AI and product initiatives the board is asking about. The condition is organizational rather than technical: the decisions that created it were made by people in positions of authority, and reversing them requires the same level of authority. Deloitte’s 2025 Tech Value Survey found that nearly 60% of leaders believe 21 to 50% of value remains trapped within their current tech, data, and people. Museums are where value goes to be preserved rather than created. This condition requires outside perspective before outside execution, because internal teams that built the museum have professional cost to naming it clearly.
The questions organizations do not ask
The twelve questions above surface the estate’s condition. Three additional questions surface the organization’s posture toward it.
“What are we maintaining that we should not be?”
This is the decommissioning question. It is rarely asked because the answer implicates decisions that someone made and defended. Asking it requires the organizational safety to name things that are not working without those names becoming political.
“What would it cost to leave our largest vendor?”
Switching cost is the wrong frame: it is easy to overestimate and hard to calculate with precision. The productive version of the question is what would have to be true for leaving to be feasible. Organizations that have answered that question have vendor relationships built on genuine value. Organizations that have never asked are in relationships held together by inertia.
“What does our technology estate look like to a new CTO?”
The framing matters: someone arriving without prior knowledge, given a week to assess what exists and what it costs, will see a different estate than the team that built it. The gap between those two pictures is the blind spot.
If this assessment produced a score lower than you expected, the next step is understanding specifically what is driving it.
FAQ
-
What is a technology maturity assessment?
A technology maturity assessment evaluates how effectively an organization understands, manages, and evolves its technology estate. It examines documentation practices, architectural change velocity, vendor management discipline, knowledge distribution, and the ratio of maintenance to new development. Google developed a four-level technical debt maturity model for internal use that evaluates teams on their ability to inventory, measure, and manage technical debt systematically. The assessment in this article applies similar principles at an organizational rather than team level.
-
What is the difference between a tech company and a company with technology?
A tech company treats technology as a managed asset that is actively directed toward business outcomes: new capability is created, outdated systems are decommissioned, and the estate is understood by more than a handful of specialists. A company with technology has systems that work well enough to support current operations but are not actively managed as assets. The distinction matters because organizations in the second category tend to accumulate debt silently and discover it at the worst possible moment, typically during an acquisition, a major incident, or an AI initiative that reveals the underlying infrastructure cannot support it.
-
How often should an organization run a technology maturity assessment?
Once per year as a baseline, and any time a significant change is being considered: a new CTO or VP Engineering, a major platform investment, an acquisition, or a fundraising round where technical due diligence is expected. The value of the assessment is not the score itself but the specific questions it reveals as answered weakly. Those questions are the highest-leverage areas for investment.
-
What does "bus factor" mean in this context?
Bus factor refers to the number of people whose departure would leave the organization unable to operate or maintain a critical system. A bus factor of one means a single engineer's exit creates a critical operational gap. Question 6 in this assessment surfaces the bus factor condition: if specific people's absence would cause systems to break, the knowledge is dangerously concentrated.
-
What does technical debt consuming IT budget mean in practice?
Deloitte's 2026 Global Technology Leadership Study puts technical debt at 21 to 40% of IT spending. In practice, when a significant portion of technology spend goes to keeping existing systems running rather than building new capability, that is capital tied up in preservation rather than progress. Organizations that bring this ratio down through systematic debt reduction free up engineering capacity for forward work.
A structured discovery maps the technology estate, identifies the highest-cost debt concentrations, and produces a prioritized plan for addressing them.
Sources
We're booking content platform
engagements for 2026.
Twenty-five minutes to walk through the work and decide if we're the right team for it. Scoping and a fixed price come after.