Anti-PMO and no-jargon
This Anti-PMO and no-jargon blog publishes tight posts that support lean intake. Each one hardlinks back to the feature pages so the original request stays the spec.
Anti-PMO · August 20, 2026
I have watched a hallway sentence die in four dialects before lunch. Keep one living record. If the requestor cannot read the page at release, you translated the work away.
move software requests without a glossaryNo Jargon · August 13, 2026
I have sat through standups where the only shared language was a glossary. Alignment is not nodding. It is a page a business user can read and say, yes, that’s my week.
replace agile ceremony words with shared factsAnti-PMO · August 6, 2026
I’ve watched lean teams hire a translator and call it process. Twenty-eight years later, the fix is still shorter: the person closest to the work writes the story, then you stop.
stop hiring a project office to translate intakeAnti-PMO · July 30, 2026
I’ve watched leadership pick a Friday and call it planning. I remember the late nineties version of that slide. The date was real. The sequence was a wish.
a software launch date is not a planNo Jargon · July 23, 2026
I have sat with a clerk who described a broken Friday export, then watched us turn it into “As a user, I want…” until she no longer recognized her week. Twenty-eight years of that habit has not made the template wiser.
stop translating software requests into user storiesAnti-PMO · July 16, 2026
I've sat through kickoffs that existed only because nobody wanted to write the request. Twenty-eight years later, I still treat a calendar hold as a confession: the story is missing.
don't schedule a software kickoff until the request existsOptional cookies
We use optional technologies only with your choice. Strictly necessary cookies for sign-in and security always run. Cookie Policy
