A CTO’s Roadmap For Test Management Maturity

The Spreadsheet Era That Lasted A Tad Too Long

Let me start by describing a scene I’ve walked into more times than I can count: There’s a shared drive and a random folder, something like “QA_FINAL_v3_REVISED_USE_THIS_ONE.xlsx.” It’s packed with thousands of rows of test cases, maintained by misaligned teams, has unnecessarily color-coded tabs that barely anyone understands and there’s a total lack of both usability and transparency. Or at least transparency that can be obtained with reasonable effort.

In regulated industries (e.g., finance, healthcare, energy, manufacturing, etc.), it doesn’t help with an external audit. For regular businesses, spreadsheets are widely considered a massive waste of time.

Across 200-plus enterprise accounts I’ve worked with, I’ve seen this play out again and again. The bottleneck is almost never the quality of the tests. Instead, it’s usually the absence of a system that connects requirements to test cases to execution results in a way that anyone, including an auditor, can follow.

Test Management Maturity: The Five Stages

When I talk about test management maturity, it’s never an argument for buying a particular tool or using a specific practice. Instead, I prefer to foster the culture or, even better, the shared philosophy of approaching documentation as a discipline. From my experience advising business owners and growing aqua cloud, a test management platform, there’s a certain sequence of stages. Companies undergo them both when scaling as an organization and improving their system as per external and internal factors. ​

When I talk about test management maturity, it’s never an argument for buying a particular tool or using a specific practice. What matters more is the shared philosophy of treating documentation as a discipline. From experience, there’s a sequence most organizations go through, both when scaling and when responding to external pressure.

Five stages:

Stage 1 – No structure: Requirements and tests exist in isolation. There is no link between them, and compliance documentation is assembled from scratch every time it’s requested.

Stage 2 – Spreadsheets: Documentation exists but in formats that are difficult to version, impossible to trust at scale and illegible to anyone outside the immediate team.

Stage 3 – A dedicated Tool: Tests and results are hosted in one place. Traceability becomes achievable but remains dependent on consistent manual discipline.

Stage 4 – Connected Documentation: Requirements, test cases and execution results are linked end to end. Coverage gaps become visible. Audit preparation is an ongoing practice.

Stage 5 – Ongoing Compliance: The audit trail exists because of how work is structured. Compliance becomes an ongoing state. Anomalies are flagged in their early existence phases.

The spreadsheet burden should end between stages 2 and 3 when a company switches to a dedicated solution. You may be curious how exactly your tech stack supports stages 4 and 5. The answer is simple: In later test management maturity stages, you may use a single tool, an array of tools or a dedicated QA platform-based ecosystem with many integrations. At this point of maturity, a company should have a proven methodology that is constantly upgraded to stay in line with compliance. No single, universal advice or practice can work here.

The jump from stage 2 to 3 is the most disruptive. Stages 3 to 4 are the most technically complex. But stage 4 to 5 is where real competitive advantage can be gained.

Where AI Helps And Where It Doesn’t​

AI is a tool to use for acceleration in processes that are established and well understood. You can’t ground traceability solely on the ability of LLM to quickly analyze massive data and yield results with sometimes acceptable results. Instead, you should use AI to accelerate tried and tested procedures.

Let’s take a look at AI applied to three specific test management maturity problems:

• Data Migration And Cleanup. Moving from spreadsheets means years of accumulated test data in inconsistent formats, duplicate entries, broken links and undocumented logic. It handles the extraction, normalization and restructuring for the ease of transitioning from Stage 2 to Stage 3.

• Traceability Mapping: When a new requirement is added, it proposes links to existing test cases based on historical patterns. The documentation stays connected without someone manually maintaining it.

• Audit Trail Integrity: It surfaces gaps in execution records, missing result documentation and coverage regressions.

There are other ways to make an audit-proof QA with the help of AI. There’s also an endless number of instances where AI can assist QA engineers and developers. And other specialists are involved. My point here is that we absolutely should use AI, but it should be used as an accelerator and never as a quick fix to systematic traceability and compliance problems.

Organizational Difficulty And Best Practices

In 2026, picking the technology is not the hard part of this journey. After all, we can already generate some useful functionalities with the help of AI, so the ways to color yet another text field are limitless.

The hard part is organizational. It’s getting development teams to accept that test management is a shared responsibility. It’s getting product managers to write requirements in a form that’s actually traceable. It’s getting leadership to understand why structured test management pays back in every audit, every release cycle, every compliance renewal.

The CTOs who actually drive this maturity curve share a few traits:

• They frame test management as a business risk concern.

• They tie compliance readiness to revenue.

• They make the transition gradual enough that teams can absorb it without grinding to a halt.

Twenty-five years in this industry have taught me that audit-proof QA can hardly be a derivative of a single tool or methodology. Internalizing why quality matters and building your very own test management policy and system is what it takes instead.

The spreadsheet era has lasted far too long, along with QA practices that were rendered obsolete three to four years ago. With discipline, the right structure and leadership willing to point out unnecessary procedures and the lack of traceability, any company, from an SMB to an enterprise, can surge to stages 4 and 5 in a reasonable time frame.

Forbes Technology Council is an invitation-only community for world-class CIOs, CTOs and technology executives. Do I qualify?