Set up

Roles and decision rights

Questions ask who decides, and they ask for a role rather than a person so the answer survives turnover. Set the department that owns each call, how the role decides when the team is working async, and which role it has to agree with before anything is final.

Add a role

Add one

Name a role

The task you will do most

Governance decides by role so the answer survives turnover, but a live session still needs to know who is in the seat today. Name the role, then name the person holding it. The role is what the deck asks about; the person is who gets chased when a card is waiting.

RoleHeld by (person)DepartmentHow this role decides asyncPaired with

Or start from a template

Templates

Start from a kit

Loads in one click, edit anything after

Nobody should start governance from a blank form. Each kit is a working set of roles with departments, decision modes, and pairing already reasoned through for a common shape of team. Load the closest one, then edit until it matches how you actually work.

Product team

Product, design, and engineering shipping on a release cadence.

Craft calls stay with the practice leads, scope and timing calls stay with product, and nothing ships without one named signer.

Product LeadDesign LeadEngineering LeadContent Lead

Internal business transformation

Cross-functional change programs with executive sponsorship and real budget.

Decision rights are explicit across functions, so the program stops stalling on who gets to call it.

Transformation SponsorWorkstream LeadOperations OwnerChange and Comms LeadRisk and Compliance Lead

Design system governance

Teams stewarding a shared system they use daily but did not build.

Component changes get a named owner and a review gate, so detaching under deadline stops being invisible.

System OwnerContributing DesignerAccessibility ReviewerBrand Owner

AI usage guardrails

Any team where staff are already using AI daily and nobody has written the rules down.

What AI may draft, what it may never finalize, and who reviews output before it ships all become named, checkable rules.

AI Usage OwnerPractice LeadData and Privacy ReviewerOutput Reviewer

Regulated content operations

Pharma, financial services, and any team shipping claims through a review gate.

Nothing reaches a public surface without medical, legal, and regulatory sign-off recorded against a role.

Medical Review LeadRegulatory LeadBrand OwnerCreative Director

Your roles

Current

Your roles

5 active

These are the options your team will see on every decider card during gather. Edit a role and the change reaches the whole session.

Creative

Creative Director

Held by Dana Whitfield

Decides aloneNo pairing

Settles open questions without waiting. Fastest, and the reason carries the weight.

Strategy

Strategy Lead

Held by Marcus Reyes

Consults, then decidesPaired with Project Lead

Gathers input async, then calls it. Input is required, agreement is not.

Design Ops

Design Lead

Held by Priya Anand

Consults, then decidesPaired with Creative Director

Gathers input async, then calls it. Input is required, agreement is not.

Brand

Brand Owner

Held by Jo Nakamura

Consensus with paired rolePaired with Creative Director

Both roles must agree before a card is reconciled. Slower, and harder to overturn later.

Delivery

Project Lead

Held by Sam Ortiz

Escalates to a leadNo pairing

Does not resolve alone. Routes the card up with the divergence attached.