Drift
2026-05-02 / 2 min read / projects/drift.mdx
A team-health read on the invisible coordination cost AI work creates. Surfaces the decisions and assumptions that go missing when shipping speeds up.
Drift is about the hidden cost of moving fast with AI.
The question is not whether the team is using AI. The question is whether the team is gaining leverage or just moving complexity into places no one is watching.
The Pattern
- More code, less ownership.
- More chats, less shared memory.
- More speed, less trust.
- More automation, more invisible decisions.
What It Measures
The lightweight version is a 15-minute assessment. The deeper version is a score that keeps watching the signals teams usually hand-wave:
- AI reliance patterns.
- Code ownership concentration.
- Review depth.
- Knowledge silos.
- Decision traceability.
The output is a Drift Score from 0 to 100, but the score is only useful if it points to behavior. A team does not need shame. It needs to know where the invisible coordination cost is compounding.
What It Can Become
The quiz can stay simple, but the product can grow into benchmark reports, team dashboards, and a steady content pipeline that turns real anonymized patterns into useful writing. The good version helps a team talk about the mess before it becomes folklore.
Why It Bugs Me
The tools can make work appear faster than a team can understand it. That gap becomes drift. I want the diagnostic to make that gap visible before it turns into a culture problem.