Why the Current Workaround Is Your Best Software Specification

I have been invited to “replace the manual process” before anyone observed it. The spreadsheet had six tabs, the email had an unofficial approval code, and one clerk knew which exceptions mattered. The workshop called these details resistance. I called them the specification we had failed to read.

A nicer process photographs well. You leave with a future-state map, a date, and a parking lot. You do not leave with the Friday that already happens. I have watched forty people spend ninety minutes designing a portal while the submitter still emailed a spreadsheet. That sentence should have been the spec.

The ugly week is the request

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 project. You have a redesign with a conference room. I have never seen a workshop invent those three facts better than the workaround sitting in someone’s sent folder.

Do not schedule the room to extract a future state. Send the two missing answers back. The Anti-PMO playbook for software intake is blunt about this: preferred vendors wait. Architecture opinions wait. The go-live date invented in the elevator waits.

Write the workaround before you invite the building

Use software project intake so the workaround exists on a page before anyone books an hour. The submitter is the operations lead, the clerk, the person who still runs the ugly Friday. A facilitator is optional. A written week is not.

One redesign that produced a future-state charter and no owner for the workaround. We spent the quarter building the charter. The workaround is still there. If the form keeps collecting polished solutions instead of lived steps, diagnose why stakeholders hate the intake form. The ugly details are where the requirement lives.

Meet only when a stranger can retell the Friday

Once the workaround is understandable, review can decide whether to keep it, replace it, or postpone the work. The software delivery management features path records the questions, estimate, and decision without pretending the future-state workshop was the specification.

If you need a workshop to find the workaround, you scheduled the wrong event. Cancel it. Ask for the paragraph. I have canceled more redesigns than I have regretted.