Team Vital Signs — Domondon Dominium™

Private by design: your answers are saved only in this browser (you can clear them anytime below). Never enter patient information or anything confidential — describe your system, not the people in it. Prefer paper for a team meeting? Download the printable worksheet.

1 · Receives demand

List every channel through which work reaches your team — including the hallway. Which channels does nobody watch?

Strong — we see all our demand Strained — some channels leak Failing — work manages us

I flinched writing this one.

2 · Applies judgment

Who decides what a request is, whether it's urgent, and whether it's yours? Name the actual humans — not "the team."

Strong — named and consistent Strained — depends on the day Failing — nobody could say

I flinched writing this one.

3 · Performs work

Your team's five recurring outputs. Just five. If you can't list them, that is itself the finding.

Strong — clear and repeatable Strained — everything is custom Failing — couldn't name five

I flinched writing this one.

4 · Coordinates people

Every standing meeting and update — and what each one is actually for. Be honest about which could be a written brief.

Strong — handoffs close the loop Strained — meetings carry everything Failing — things fall between people

I flinched writing this one.

5 · Uses knowledge

Three things your team knows that exist only in someone's head. Name the heads. What happens when they retire?

Strong — written, current, findable Strained — half folklore Failing — it walks out at shift change

I flinched writing this one.

6 · Manages risk

The last thing that went out and shouldn't have. What check would have caught it — and does that check exist today?

Strong — gates exist and reject things Strained — checks are habits, not designs Failing — we find out from the recipient

I flinched writing this one.

7 · Produces outputs

Who receives your work, and what do they do with it next? Would they describe your output the way you would?

Strong — we know our downstream Strained — we ship and hope Failing — no idea what happens next

I flinched writing this one.

8 · Improves over time

The last time a lesson became a changed procedure — not a reminder, a changed checklist or step. If you can't remember one, write that down too.

Strong — lessons become architecture Strained — retros happen, nothing changes Failing — same incident, every quarter

I flinched writing this one.

Your team's vital signs

The "prompt for your AI" wraps your answers with instructions for a governed AI system (one running the governance core) to propose first moves — drafts for your review, never actions. Next step after this: the four-week Minimum Viable Version.