Anti-PMO · 07/02/2026
Local Product Manager Successfully Launches 'Revolutionary Feature' That No Human Being Ever Requested
Some of us have sat through a memo praising a menu bar that moved three pixels after six months of debugging. I still treat that celebration as a task that never met an outcome.
I have been invited to launch parties for work that had no request. Different year. Same memo: “A revolutionary experience,” which means nobody wrote the week down and a menu bar moved three pixels after six months of debugging.
A celebration photographs well. You leave with a screenshot, a date, and a parking lot. You do not leave with a story a stranger can retell. I have watched forty people spend ninety minutes applauding a pixel while the submitter still emailed a spreadsheet every Friday. That sentence should have been the launch.
A pixel is not a decision
If the person closest to the work cannot write what happens today, who is stuck, and what better looks like, you do not have a feature. You have a rumor with a release note. I have never seen a pixel invent those three facts. I have seen pixels bury them under a slide titled Impact.
Do not schedule the party to extract the paragraph. Send the two missing answers back. The Anti-PMO playbook for software intake is blunt about this: preferred vendors wait. Architecture opinions wait. The revolutionary pixel invented in the elevator waits.
Start with a paragraph, not an invitation
Use software project intake so the request exists before anyone books a launch. The submitter is the operations lead, the clerk, the person who still runs the workaround. A facilitator is optional. A written week is not.
One launch that produced a charter and no owner for the workaround. We spent the quarter celebrating the charter. The workaround is still there. That is not a cute story. It is the default.
Let the meeting decide instead of discover
Once somebody can name the user and the outcome, the launch review has a real decision to make. The software delivery management features path records the questions, estimate, and yes or no. No confetti is required.
If you need a launch memo to find the request, you scheduled the wrong event. Cancel it. Ask for the paragraph. I have canceled more revolutionary features than I have regretted.