Standard operating procedures
When the answer is a rule,
not a screen.
Procedure the Project Management Office writes and owns. Each one states what it covers, why it exists, and what it stops going wrong quietly.
Adding or changing a tool
Every card on this page is generated from the TOOLS array at the bottom
of this file. Add an entry, and the card, its node on the culm, its fade-in delay, its
line in the masthead index and the count above all follow. Nothing else needs editing.
Each band runs two abreast; an odd tool out closes it across the full width.
band decides which group a tool sits in — delivery,
portfolio, inbound or reference, defined in the
BANDS array. To move a tool, change that one field. To add a group, add a
BANDS entry; band order there is band order on the page, and it follows
how often people open things rather than the order work happens in. A tool whose band
key matches nothing still renders, in a flagged Unfiled group at the bottom,
so a typo shows up as a red heading instead of quietly losing a card.
tagline is the single line under the tool name. Write it so that someone
who reads nothing else on the card still knows what the tool is. meta is
the row of small stamps under the prose — where the numbers come from and how often
they refresh. That row is what answers “can I trust what I am looking at”, so keep it
factual: sources and cadence, not adjectives.
short is optional and only affects the masthead index, where a long name
like “Project Management Office Roster by Track” will not fit a narrow column. The card
itself always uses the full name.
Written procedure comes from the SOPS array below it. Those are documents,
not applications, so they read as ruled entries rather than cards — a node band, no culm
through it. An SOP with no href shows a link-needed flag unless its status
is planned, which is how a document that exists but nobody can open stays
visible as a problem.
Keep why about what changes for the business. A feature list tells nobody
whether the tool is worth opening.
Leave note off unless it stays true indefinitely. Version numbers and
build dates go stale here without anyone noticing, and a stamp nobody trusts is worse
than no stamp — each tool shows its own version when you open it.