Skip to main content

Anti-PMO · 06/18/2026

Architect Appears in Dream to Warn Developers That the Database Is Held Together by Duct Tape

I've been visited, in the useful sense, by a senior engineer who left three years ago and still owns the Excel file that runs Friday. The tape was real.

A hidden file is the plan until someone writes it down. I have sat in rooms where the database “just works,” the only map lives in a departed architect’s head, and someone said “we’ll document it after the release.” Then engineering inherited duct tape. The tape had no first increment and one Excel workbook named FINAL_v7.

Planning is what comes first, what is blocked, and what the first release will actually include. A dream visitation is none of those. I have funded beautiful architectures. I have rarely seen them survive the first missing spreadsheet.

Stop publishing the build before the brittle path exists

If no one can name the first-release result in the requester’s language, you do not have a design. You have folklore. Folklore creates overtime, then blame. The label changes; the undocumented dependency does not.

Write the week. Attach the unknowns. Record the yes. Then sequence. software project planning is that step—not a new dialect, and not a séance with a former principal.

Make the real constraint visible

Busy season, the Excel file that feeds payroll, the clerk who is the only trainer: those are the plan. They belong on the same thread as the request. A diagram invented so leadership has a picture belongs in the drawer with the other pictures.

Use requirements gathering software so the hidden dependency attaches instead of migrating into a myth. When the tape fails, the reason should still be readable by the person who reported the pain.

Let the user's day provide the final evidence

I have signed off on launches that hit every box and missed the week because FINAL_v7 moved. The ticket closed. The workaround stayed. That is not delivery. That is filing.

I have seen the invisible spreadsheet reappear later in why project managers get blamed for missed deadlines. Apparently ghosts also need an accountable owner.

The complete delivery path is described in How to move software projects in real English. If the requester cannot read the page at release, the dream was a stand-in. Ask whether their Friday changed. Document the brittle path while its human map is still awake and available for questions.