Hi, I'm Shape and Ship
Practical frameworks for CTOs, CPOs, tech&product leaders scaling teams, delivery, and AI adoption. From a CTPO who ships with the teams she works with. Strategy, metrics, and field lessons from scale-ups of 20 to 120 people.
Everyone is busy, nothing ships
Everyone is busy and nothing ships. The problem isn't that people aren't productive enough. It's that they're too productive, in the wrong place.
From Copilot to harness engineering
Individual AI initiatives are everywhere. Going from there to a team that builds and maintains its own AI harness is a different problem. The gap is smaller than it looks.
AI doesn't replace junior developers. But it changes how we train them.
AI speeds up production, not learning. Cutting junior hiring is rational today and a disaster in 5 years. The real question is whether we still know how to train them.
Let it burn - Why the best organizations choose what they don't fix
Three projects max. The rest burns. Why triage and iteration beat reorgs for improving team efficiency
Devs produce twice as many PRs. Delivery hasn't moved.
Devs produce twice as many PRs with AI. Delivery hasn't kept pace. The real ROI isn't in the tokens burned, it's in what teams do with the time AI frees up.
Feature Overdose
A team ships 11 features in a quarter. The board is happy. Delivery is green. When someone checks the usage data, 3 are actually adopted. The other 8 exist in the product, in the documentation, in the support scope. Not in user habits.
Cheap to build, costly to keep
AI has broken the cost of writing code. It hasn't touched the cost of owning it. How to measure what your velocity dashboards won't show you.