Set Standards for Large Programs

Five workstreams. Five different ways of doing the same thing. One reports RAG based on delivery progress. Another reports RAG based on vibes. One uses Jira, another Trello, a third tracks everything in a spreadsheet. Six months in, the program lead spends half their week translating between formats instead of leading the program.

The deeper problem is that nobody owns standards as a deliberate thing to set up. It's treated as admin. It's not. It's the operating system of your program.

So one of three things happens. Standards arrive as a 40-page document and become shelf-ware on day two. Or they get set at kickoff and are never enforced, exactly when things get busy is exactly when they get skipped. Or every workstream invents its own approach and the program lead becomes a translator.

This toolkit replaces all of that with seven standards, set once on day one and applied everywhere after.

• Tooling — One tool. Jira for delivery, Confluence for documentation
• Status Definitions — RAG based on delivery AND benefit metrics, not just delivery
• Reporting Cadence — Submitted, not chased. Same day. Same time. Every week
• Document Storage — One location. One folder structure. If it's not there, it doesn't exist
• Naming Conventions — Simple convention. No exceptions. No detective work
• Meeting Norms — If it wasn't written down, it didn't happen
• Definition of Done — Acceptance criteria upfront. Reviewer named. Sign-off owner named

Set them at kickoff. Apply them everywhere. Review them quarterly.

What you get

• Excel template with three tabs: Start Here, a fully-worked Example for a platform migration program (all seven standards filled in with Program Sprint defaults), and a blank Your Project tab pre-filled with the defaults so you only customise what's specific to you.
• 7-page PDF guide explaining why most programs never set standards, the seven standards in detail, a worked example, and a 6-step process for setting standards up for your own program.
• Color-coded standard pills built into the template (Tooling violet, Status cyan, Cadence coral, Storage teal, Naming amber, Meetings indigo, Done green) — visually distinct so each standard is recognisable at a glance.

Who this is for

• Program managers running multi-team programs who need to set up operating norms from scratch
• PMO leads who want a baseline set of standards across multiple projects
• Anyone who has spent months translating between five different reporting formats

What's it like to use

Open the Example tab. See seven standards filled in with real, specific operating norms — the kind that actually survive contact with reality. That's the bar. Then move to the Your Project tab where the Program Sprint defaults are already there, and customise the right-hand column for your program. Share it with every workstream on day one. Run it for a month. Reject anything that doesn't follow the format. Then prune anything that's drifted into theatre.

This isn't a 40-page operating manual that lives in a SharePoint folder. It's a one-sheet operating system your team can run from day one.

About Structured Way

Standards for Large Programs is part of the Structured Way toolkit family. Practical tools for running programs and projects, built by program manager, for program managers.

Visit structuredway.com to explore the rest.