student-team · storey-2026-triple-debt

By week eight, one team hit a wall. Simple changes were breaking things in unexpected places, and progress had stalled. When I met with them, they initially blamed technical debt: messy code, hurried implementations, architectural shortcuts. But as we dug deeper, a different problem emerged. No one on the team could explain why certain design decisions had been made, or how different parts of the system were supposed to work together.