The pattern nobody names
Nearly every 'unexpected' project problem was visible at kickoff to anyone who asked the unglamorous questions. It's easy to recognize once you see it, but most teams never name it directly — they just feel the friction it causes, sprint after sprint, without tracing it back to its source.
What actually fixes it
The fix usually isn't a new tool or a new meeting. It's making the relevant information visible at the moment a decision is being made, instead of buried in someone's memory or a document nobody reopens. That's a structural change, not a discipline problem — it works because it removes the need to remember, not because it asks people to remember harder.
Where teams stop too early
Most teams get partway there: they adopt the practice for one planning cycle, see it help, and then let it lapse the moment things get busy — which is exactly when it matters most. The version of this that survives a busy quarter is deliberately lighter than the version that looks impressive in a workshop.
Keep it next to the actual work
Whatever you put in place here only stays accurate if it lives next to where the work itself is tracked — on the same board, updated by the same motion that updates status — rather than in a separate document that quietly drifts out of date within a few weeks.