The pen is hovering over the yellow Post-it, the Sharpie fumes hitting my nose before the ink even touches the paper. I know exactly what I am going to write. I wrote it fifteen days ago. I wrote it forty-five days ago. The ink bleeds slightly into the fiber, forming the words: ‘Communication gaps between teams causing delays.’ I feel a strange sense of deja vu, not the mystical kind, but the bureaucratic kind where you realize you are trapped in a revolving door and you are the one pushing it. Across the table, Mark is nodding. He’s always nodding. He looks like he’s really absorbing the gravity of the situation, but I suspect he’s just wondering if there are any oatmeal raisin cookies left in the breakroom. We are here again, in the ritual of the retrospective, doing the dance of improvement without ever actually moving our feet.

I reached into my pocket just as Sarah started talking and felt the crisp edge of a $20 bill I’d forgotten in these jeans five months ago. It was a tiny, unearned victory. For a split second, I felt like a genius, a man of sudden wealth and foresight, even though I’d simply been too lazy to check my pockets before the last wash. That is exactly what these retrospectives have become. We find a problem, we feel the momentary dopamine hit of ‘identifying’ it, and we mistake that feeling for actual progress. We treat the discovery of a flaw like the resolution of it. We are essentially finding $20 in our old jeans and thinking we’ve solved our long-term financial planning issues. It’s a comfortable delusion, a way to feel productive while the underlying structure remains as cracked as it was 25 sprints ago.

The Vector Point of Change

Nova M., a typeface designer I know who obsesses over the negative space in a lowercase ‘e’ for 45 hours straight, once told me that if you don’t change the vector points, the letter stays the same no matter how much you talk about its personality. She works in a studio that is almost pathologically organized, a stark contrast to our digital chaos. She spends 105 days on a single family of fonts, ensuring that the 555th character has the same soul as the first. When she sees a flaw, she doesn’t write a note about it; she moves the point. She adjusts the weight. She actually touches the work. We, on the other hand, seem terrified of touching the work. We prefer to talk around it, creating a buffer of sticky notes between us and the actual friction of change. It’s easier to complain about the ‘silo effect’ than it is to actually walk over to the 15th floor and talk to the person who is blocking your pull request. We’ve professionalized the act of pointing at things without picking them up.

This reminds me of how we often ignore the physical environment when we’re trapped in these digital loops. I was staring at the radiator in our meeting room, which is a surprisingly heizkörper anthrazit, and I realized that we value the aesthetics of the process more than the outcome. The radiator has a job: it provides heat through a clear, physical mechanism. If it stopped working, we wouldn’t sit in a circle and write ‘Better warmth’ on a piece of paper. We would call someone to fix the pipes. But when our software delivery pipeline breaks, or when our team culture turns toxic, we treat it as an abstract concept that can be managed with better adjectives. We’ve traded engineering for linguistics.

I’ve made this mistake myself. I once spent 35 minutes arguing that we needed ‘more transparency’ in our Jira tickets. Everyone agreed. We even made it a ‘High Priority’ action item. The next day, I didn’t change a single thing about how I wrote my tickets. I just felt better because I’d ‘voiced my concern.’ It’s the ultimate corporate sedative. We use these meetings to vent our frustrations, and once the frustration is aired, the pressure to change evaporates. We leave the room feeling lighter, not because the problem is gone, but because we’ve successfully offloaded the guilt of ignoring it onto a document that no one will read until the next 15th of the month.

The Silence of Amnesia

There’s a specific kind of silence that follows the ‘Action Items’ portion of a retrospective. It’s the silence of collective amnesia. We write ‘Improve communication’ and we don’t assign an owner. We don’t set a deadline. We don’t define what ‘improve’ looks like in a measurable way. Is it 25% fewer emails? Is it 5 more face-to-face meetings? We don’t care. We just want the meeting to end so we can go back to the work that is being delayed by the very problems we just refused to solve. It’s a cycle that has repeated itself for 255 days in this company alone. We are addicted to the reflection, but we are allergic to the transformation. It’s like standing in front of a mirror and complaining that your hair is messy, then walking away without picking up a comb. You’ve seen the truth, but you haven’t acted on it, which in many ways is worse than being ignorant of the mess in the first place.

Nova M. would never allow this. In typeface design, there is no room for ‘vague improvement.’ If the kerning is off by 5 units, the word looks broken. You can’t just ‘hope’ it looks better in the next version. You have to go into the software and change the mathematical relationship between the letters. Our teams are just letters on a page, and our processes are the kerning that keeps us readable. When we ignore the gaps, the whole story becomes illegible. I once saw her delete an entire week’s worth of work because she realized the foundation of the ‘s’ was 5% too heavy. It was painful to watch, but it was honest. We lack that honesty. We would rather keep the heavy ‘s’ and just write a note to ‘be more mindful of letter weight’ in the future.

The Comfort of ‘Safe’

I wonder if the problem is that we’ve made these meetings too ‘safe.’ We’re so worried about psychological safety that we’ve eliminated psychological accountability. No one wants to be the person who says, ‘Hey, we’ve talked about this 15 times and nothing has changed. Why are we still failing?’ That feels like an attack, even when it’s just an observation of reality. So we stay in the shallow end, where the water is warm and no one has to swim. We’ve created a culture where the appearance of collaboration is more important than the reality of coordination. We are all very nice to each other while the project slowly sinks under the weight of its own unaddressed inefficiencies. I’ve probably been the biggest culprit of this, smiling and nodding while knowing full well that the action item I just accepted will be buried under 45 unread emails by tomorrow morning.

Moving the Points

Actually, I think I’ll stop nodding. The $20 in my pocket feels like a reminder that some things happen by accident, but real change never does. If we want a different result in 15 days, we have to do something that feels uncomfortable today. We have to stop writing ‘Communication gaps’ and start writing ‘John will call Mary every Tuesday at 10:05 AM to discuss the API integration.’ We need the granular, the specific, the boring details of execution. We need to stop being poets of our own failure and start being mechanics of our own success. The Sharpie is still in my hand. I look at the Post-it I just wrote. It’s 5 words of nothing. I crumple it up. The sound of the paper crinkling is the loudest thing in the room.

Everyone looks at me. Mark stops nodding. Sarah stops typing. I feel the heat of 5 pairs of eyes on me. I realized that my own fear of being ‘difficult’ was the very thing keeping the cycle alive. I was a participant in the stagnation. I find myself thinking about the $20 again. It’s a gift from the past, a little nudge from a version of me that was less tired, less cynical. Maybe that’s what a real retrospective should be: a gift to our future selves, a way to make the next 15 days slightly less frustrating than the last. But that requires more than ink. It requires the willingness to move the vector points, to change the weight of the line, and to admit that the way we’ve been doing things is simply not working. I take a new Post-it. I write a name. I write a time. I write a specific, measurable task. It’s not elegant. It doesn’t have the broad, sweeping appeal of ‘culture change.’ But it’s a point moved. And in the world of design, as in the world of work, that is the only thing that actually matters.

The Map vs. The Journey

We often mistake the map for the journey. We spend so much time drawing the route, highlighting the pitfalls, and discussing the scenery that we never actually put the car in gear. We’ve become a society of map-makers who are afraid of the road. But the road is where the progress happens. It’s messy, it’s loud, and it’s full of 105 different things that can go wrong, but it’s the only way to get anywhere. The retrospective is just the map. If we don’t use it to drive, it’s just a colorful piece of paper. I look at the 45 other sticky notes on the wall. They look like a mosaic of missed opportunities. We could build something beautiful with all this feedback, or we could just let it gather dust until the next sprint ends. The choice isn’t made in the meeting; it’s made in the 5 minutes after the meeting ends, when we decide whether to actually do the thing we said we’d do.

I think about Nova M. again, sitting in her 15-square-meter studio, meticulously adjusting a single curve. She isn’t waiting for a meeting to tell her the curve is wrong. She knows it’s wrong because she’s looking at it. She’s engaged with the reality of her craft. We need to be more like that. We need to stop waiting for the bi-weekly permission to improve and start fixing the things we see in front of us. If a pipe is leaking, you don’t wait for a retrospective to put a bucket under it. You just do it. We’ve outsourced our common sense to a framework, and we’re paying for it in 25-day increments of wasted potential. It’s time to stop writing notes and start moving the points.