Post Decision Drag
The Meetings, Workarounds, and Headcount You Inherited from Decisions Nobody Remembers Making
By Jason Abdo
Your team claims they have no capacity. Yet half their sprint goes toward servicing choices made two years ago by people who no longer work at your company.
Open your calendar and find the recurring meeting nobody remembers starting.
Someone created it. They created it to manage a problem. That problem came from a decision, and the decision happened long enough ago that everyone stopped asking why the meeting exists. Now four people attend it every Thursday and call it operations.
That invisible tax or meeting is called post decision drag.
Drag shows up across organizations in four distinct ways:
Meeting Drag: Recurring calendar holds that exist solely to re-litigate or babysit past choices.
Operational Drag: Manual workarounds that quietly turn into permanent job descriptions.
Technical Drag: System debt traceable directly to a single skipped discovery step.
Trust Drag: Teams over consulting on every minor change because a past choice went wrong.
Decision Reversibility unfortunately is not just a yes or no. Reversibility is a closing window of time. Some windows stay open forever. Other windows are shut the moment integration code touches production.
The decision before the decision is setting your evaluation effort to match how fast that reversal window closes.
EXAMPLE 1: CREATING TRUST DRAG ON A SIMPLE UI CHANGE
The Drag Audit: Six hours of meeting time across five people is a minor waste. The real damage is Trust Drag.
You taught five co creators and stakeholders that a two pixel UI change requires full consensus.
Congrats, you may have just injected friction into every future release.
EXAMPLE 2: WASTING THE REVERSAL WINDOW ON AN IRREVERSIBLE VENDOR
The Drag Audit: The executive who signed the contract did not pay for that haste. The store associates and operations hires pay for it every single day at the register.
EXAMPLE 3: DEFENDING THE PAUSE TO ELIMINATE DRAG
The Drag Audit: You spent decision effort while the reversal window was open. You eliminated operational drag before it started.
SORT YOUR DRAG BEFORE YOU FIX IT
Some drag fades. Your team gets fast at the workaround, the pain shrinks, and the cost flattens out. You live with that kind for years and stay healthy.
Some drag compounds. Every new SKU makes the tax problem worse. Every new region adds another jurisdiction. Every new hire needs training on the workaround. This kind grows on its own while you sleep.
Sort your drag into those two buckets before you fix anything.
Compounding drag earns a spot on your roadmap. Fading drag earns your patience.
THE DRAG YOU CHOOSE ON PURPOSE
You will accept drag to hit a date. That is a legitimate call, and strong product leaders make it regularly.
The failure comes later, when nobody writes it down. Six months on, the workaround looks like policy. New hires assume someone designed it that way. A temporary choice becomes permanent furniture.
Write down what you accepted, what it costs your team per week, and what triggers a revisit. Ten minutes of documentation keeps a deliberate trade off from turning into architecture.
RUN A DRAG AUDIT THIS WEEK
Lets get a bit tactical here. You can uncover the hidden tax in your own organization today.
Pick your three most persistent manual processes and your three most stubborn recurring meetings.
For each item, ask three questions:
Which past decision created this process or meeting?
Who made that decision, and who pays for it now?
Does this cost grow every quarter or hold flat?
This audit reveals the unbudgeted operational spend your team carries every week.
THE TAKEAWAY
Before you schedule your next alignment meeting or sign a vendor contract, make the decision first.
Ask yourself:
How fast is would our reversal window close?
Who will pay the daily drag if we get this wrong?
Match your decision effort to the true speed of that window. You will save your team hundreds of hours and shrink your drag load every quarter.
Interested in how to make a great decision? Check out some of our other Protege Pulse substack content.
Until next time!
Jason
First published in Protege Pulse, the Product Protégé newsletter. Read it on Substack.
