I've been embedded in a lot of teams that weren't shipping. The contexts vary — fintech, public sector, scale-ups — but the pattern that shows up is almost always the same. Three things break at once, and because each one looks manageable on its own, nobody names the system that's failing.
Symptom 1 — the roadmap keeps moving
Not because priorities changed. Because nothing actually landed. Q1 slips into Q2. Q2 gets "reprioritised." By Q3 everyone's stopped counting. The board has a lot of green tickets and production has nothing new in it.
This is almost never a planning problem. It's a clarity problem. Teams that don't ship don't know what "done" means until it's already late. The acceptance criteria are vague, the definition of ready was never written, and the sprint goal is aspirational at best.
When you can't agree on what "done" looks like, you'll never agree on whether you got there.
Symptom 2 — the team spends its days in meetings
Daily, grooming, refinement, sprint review, retrospective, alignment call, stakeholder update. On a bad week, that's half the calendar. On a really bad week, it's more.
The irony is that none of these meetings are useless in isolation. They become useless when they replace the thing they were supposed to support: the actual work. When the team is using the daily to catch up on what Slack didn't surface, something is already broken.
- Meetings multiply when communication is unclear.
- Communication is unclear when context isn't shared.
- Context isn't shared when the team doesn't trust the process to hold it.
Fix the process, the meetings shrink. Not the other way around.
Symptom 3 — product and engineering aren't talking
Two teams in the same open space. Two definitions of what's being built. One has a roadmap. The other has a backlog. Neither maps to the other.
This is the most expensive one to ignore. By the time it shows up clearly — in a post-mortem, in a resignation letter, in a sprint where engineering built exactly what was asked and it was exactly wrong — it's already been months in the making.
What to do about it
The three symptoms above aren't separate problems. They're three outputs of the same broken system. You can't fix the roadmap without fixing communication. You can't fix communication without fixing how product and engineering share context.
Start with a week of observation. Don't restructure, don't introduce a new tool, don't hold a workshop. Just watch. Ask obvious questions. Read the tickets. Sit in the meetings. The signal is always there — it's just never been named out loud.
Once you've named it, the team usually already knows what to do. They just needed someone with no stake in the current setup to say it first.