Roles & Decisions

The point of this section is to end ownership ambiguity at 18 people. Each role has a card saying what it owns, what it does NOT own, and who it hands off to. See the org chart for the reporting structure.

The five pages, and which question each answers

If you’re asking…	Read
“What am I accountable for?”	Role Cards
“What does my day actually look like?”	The Daily Loop
“Am I doing enough at my level?”	Expectations by Level
“Who owns this specific thing?”	Who Owns What
“Who makes the final call?”	Decision Rights (DACI)

Read them in that order the first time. After that, only Who Owns What is meant to be looked up rather than read.

RACI across the delivery lifecycle

R = does the work · A = accountable (one per row) · C = consulted · I = informed

Stage	CEO	PM	BA	Team Lead	Dev	QA
Discovery	I	A	R	C	I	I
Estimate & SOW	A	R	C	C	I	I
Build	I	A	C	R	R	C
QA & UAT	I	A	C	C	C	R
Handover	I	A	C	R	I	C
Warranty & support	A	C	I	R	R	C

Note

The PM stays Accountable for delivery even when the client is late with feedback — chasing that is the PM’s job, not a reason work stalls.

How the layers fit together

Ownership questions get answered at one of three altitudes. Reaching for the wrong one is what turns a small question into an argument.

flowchart TD
  RC["Role Cards<br/>standing accountability"] --> WOW["Who Owns What<br/>the gray-zone artifacts"]
  WOW --> DR["Decision Rights<br/>the six recurring calls"]
  RC -.- L["The Daily Loop<br/>how the work actually flows"]
  RC -.- EL["Expectations by Level<br/>what good looks like"]

Tip

If something is disputed and isn’t on any of these pages, decide it in the moment — PM for delivery and client matters, CTO for technical ones — then add the row to Who Owns What the same day.