Category / Demo séance
Shiny Demo, Hollow Soul
Dear frAGILE, I just did a demo where I pretended we had progress. The backend is not built. The design is not approved. But I smiled and clicked through Figma like it was live. I hate how good I am at this.
Reply: You are not faking success. You are faking certainty because the room rewarded the illusion. Next time, label the demo correctly: prototype, concept, or theater with clickable buttons. The truth is cheaper before the applause.
Category / Alignment fatigue
Alignment on Alignment
Dear frAGILE, I have been in back-to-back alignment meetings for three weeks. We are aligning on alignment. The work is not moving. I do not even know what we are building anymore.
Reply: You are trapped in the Alignment Spiral, where fear of misstep outranks movement. Ask what decision is required, who owns it, and what changes after the meeting. If nobody knows, cancel the sequel.
Category / Backlog guilt
Landfill Refinement
Dear frAGILE, My backlog is a landfill. I cannot look at it. Refinement just means moving trash from one pile to another. I feel like I am failing my team.
Reply: Backlogs are not sacred scrolls. They are compost piles. Archive the noise. Find the signal. Your team needs a compass, not a hoarder with admin permissions.
Category / Priority fog
Everything Is Critical
Dear frAGILE, Every stakeholder says their thing is priority one. Leadership says we need focus, then forwards twelve “small asks” with visible urgency and invisible tradeoffs.
Reply: If everything is priority one, priority is dead. Ask what gets delayed, deprioritized, or unfunded. Watch the room discover math. It is painful, but so is pretending capacity is a personality trait.
Category / Dependency séance
The Dependency Has Feelings
Dear frAGILE, We committed to a date before confirming the dependency team even knew we existed. Now we are “partnering closely,” which seems to mean sending them increasingly haunted Slack messages.
Reply: A dependency is not real until another team names the owner, date, interface, risk, and escape hatch. Until then, you have a wish wearing a program-plan lanyard.
Category / Retro déjà vu
Same Sticky, New Wall
Dear frAGILE, We keep identifying the same retro themes every sprint. Communication. Clarity. Dependencies. Then we create action items, forget them, and return to the scene of the crime two weeks later.
Reply: That is not continuous improvement. That is organizational karaoke. Pick one action, assign one owner, define one visible consequence. Otherwise the retro is just group journaling with colored squares.