The Alignment Tax

Track one number for your data team: days from request to first real use.
Start the clock when someone asks for a new dashboard, source or metric, and stop it when they use the result to make a decision. Then split the days into two columns: days spent working, and days spent waiting.
When I’ve done this with teams, the waiting column usually wins. Mostly it’s access to a source, or nobody has agreed what “active” means yet. Sometimes everything waits for the one person who can touch the orchestrator.
I call that column the alignment tax. A velocity chart never shows it, because no ticket is in progress while you wait for a reply. So the team stays busy, and the people who asked keep waiting.
What to do depends on which wait is biggest:
- Access: request it the day the work is approved.
- Definitions: agree them in writing before anyone builds.
- One-person bottlenecks: pair someone with that person until two people can make the change.
A spreadsheet is enough, and I’d be surprised if build time turns out to be your biggest number.
Which wait eats most of your team’s time? Tell me and I’ll reply with how I’d shrink it.
Fractional Data Architect helping startups and scaleups build data platforms that scale.
More about Thomas Nys →