The Vapourware Index: How to spot fake progress in 30 minutes
There is a specific kind of silence that falls over a boardroom when I ask to see the product.
Not the slide deck. Not the Figma prototype. Not the "architecture vision." The product. The thing that customers log into. The thing that takes credit card details.
If there is a pause, a shuffle of papers, or a sentence that starts with "Well, we are currently refactoring...", then I know we are in trouble.
I call it the Vapourware Index.
It is a measure of the distance between the story you are telling investors and the code you are actually shipping. In a healthy company, that distance is zero. In a distressed asset, it is a chasm.
Here are the three signs that your "Digital Transformation" is actually just expensive theatre.
1. The "Enabler" Trap
Look at your roadmap. Count the number of tickets or initiatives labeled as "Enablers," "Foundation," or "Refactoring."
If they make up more than 30% of your work, you aren't building a product. You are building a shrine to engineering vanity.
Engineers love "enablers." They love building frameworks, setting up Kubernetes clusters, and debating the merits of Rust vs. Go. It feels like work. It looks like work. But until it puts a feature in front of a user, it is waste.
2. The "Green" RAG Status
We have all seen the reports. The status is "Green." The burn rate is impressive. The slide decks are optimistic. And yet, the user count remains stubbornly at zero.
How is that possible? Because the industry has learned to measure "activity" rather than "outcome."
Teams hit their sprint goals. They hold their retrospectives. They update their Jira tickets. By their own internal logic, they are succeeding. But commercially, they are stagnant.
If your status reports measure "velocity" but not "revenue" or "adoption," you are flying blind.
3. The Architecture Diagram is Too Clean
Real software is messy. It has legacy bits, weird hacks, and bits of duct tape holding the API together.
When I see an architecture diagram that looks like a Mondrian painting—perfect boxes, clean lines, perfect microservices separation—I get suspicious.
Usually, it means the architecture exists only on a whiteboard. It is a theoretical construct, not a living system.
The Fix
The cure for Vapourware is painful but simple: Radical Truth.
Stop the "Enablers." Stop the "Refactoring." Force the team to ship a vertical slice of value—from the database to the UI—by Friday.
If they can't, you don't have a tech stack. You have a crime scene.