# Role Clarity Matrix


### [Your Business Name]

**Prepared by:** Whitney Radacina — The Founder-Proof Method

**Date:** [Date]

**Version:** 1.0 — The Founder-Proof Kit

---

> **What this document is:** This is your team's operating clarity document. It defines what each person on your team owns — not just what they do, but what results they are accountable for, what they are empowered to decide without you, and where their role begins and ends. This document exists so you stop being the answer to every question, and your team stops waiting for permission to lead.
>
> **How to use it:** Share this with your full team. Walk through it together. Every person should leave that conversation knowing exactly what is theirs, what isn't, and who to go to when something falls outside their lane. Review and update it every 90 days or when a role changes.

---

## FOUNDER ROLE — [Founder Name]

**Title:** Founder + CEO

---

### What You Own

*These are the outcomes only you should be driving. If you're spending significant time on anything outside this list, something in the architecture needs to change.*

| Outcome | What It Means in Practice |
| --- | --- |
| Business vision + strategic direction | Where the business is going, what it stands for, what it doesn't do |
| Key client relationships | High-stakes relationship moments — not day-to-day communication |
| Revenue growth + offer development | New offers, pricing decisions, growth strategy |
| Hiring + team culture | Who joins this business and what it feels like to work here |
| Final financial decisions | Anything above $[threshold] — you set this number |

---

### What You Are No Longer The Default For

*These are the things that have been routing to you that now have a defined owner. Your job is to stop answering these — and trust the architecture.*

- [Routine client communication and updates]
- [Day-to-day project management decisions]
- [Operational problem-solving below the escalation threshold]
- [Team task management and follow-up]
- [Scheduling and logistics]

---

### Your Decision Threshold

*The line between what you decide and what the team decides.*

**You decide:** Anything strategic, anything above $[X], any decision that changes how the business operates, any client situation that puts the relationship at risk.

**The team decides:** Everything else. If it falls within their defined role and below the escalation threshold — it's theirs. They don't need to check with you first.

---

## TEAM ROLES

---

## [Team Member Name] — [Role Title]

**Reports to:** [Founder / Ops Manager / etc.]

**Primary category:** Client Experience / Team & Decision Architecture / Systems & Operations

---

### Owned Outcomes

*What this person is accountable for — the results, not just the tasks. If these outcomes aren't being hit, this is the person responsible.*

| Outcome | What Success Looks Like |
| --- | --- |
| [Outcome 1] | [Specific, measurable, observable] |
| [Outcome 2] | [Specific, measurable, observable] |
| [Outcome 3] | [Specific, measurable, observable] |
| [Outcome 4] | [Specific, measurable, observable] |

---

### Day-to-Day Responsibilities

*The recurring work that drives the outcomes above.*

- [Responsibility 1 — specific to this role]
- [Responsibility 2]
- [Responsibility 3]
- [Responsibility 4]
- [Responsibility 5]

---

### Decision Authority

*What this person is fully empowered to decide and act on — without checking with the founder first.*

**Can decide independently:**

- [Decision type 1 — e.g. Responding to routine client questions and updates]
- [Decision type 2 — e.g. Approving or declining meeting requests on the founder's behalf]
- [Decision type 3 — e.g. Managing project timelines within the agreed scope]
- [Decision type 4 — e.g. Purchasing tools or resources up to $X without approval]

**Does not decide without escalating:**

- [Decision type — e.g. Anything that changes the scope of a client engagement]
- [Decision type — e.g. Any financial commitment above $X]
- [Decision type — e.g. Any communication that could affect the client relationship at a strategic level]
- [Decision type — e.g. Hiring or ending a contractor relationship]

---

### Interface Points

*Who this person works with regularly and what they coordinate on.*

| Person | What They Coordinate On | Cadence |
| --- | --- | --- |
| [Founder] | [Strategic updates, escalations, high-stakes decisions] | [Weekly / As needed] |
| [Team Member] | [What they hand off or collaborate on] | [Daily / Weekly] |
| [Client] | [What client-facing communication they own] | [As defined by communication protocol] |

---

### Escalation Triggers

*The specific situations where this person stops and escalates — upward to the founder, or sideways to another team member.*

**Escalate to [Founder / Ops Manager] when:**

- [Trigger 1 — e.g. A client expresses dissatisfaction that can't be resolved with a standard response]
- [Trigger 2 — e.g. A decision is needed that falls outside defined authority]
- [Trigger 3 — e.g. Something breaks that affects multiple clients or the entire delivery system]
- [Trigger 4 — e.g. A request comes in that would change the agreed scope]

---

### What's Not Their Job

*Explicit boundaries — what this role does not own and should not be absorbing.*

- [Boundary 1 — e.g. Strategic client relationship management]
- [Boundary 2 — e.g. Financial decisions of any kind]
- [Boundary 3 — e.g. Setting or changing business priorities]

---

## *(Duplicate this block for each team member)*

---

## ROLE OVERVIEW — AT A GLANCE

*A consolidated view of who owns what across the business. Use this as your quick reference.*

| Role | Person | Primary Ownership | Decision Authority Level | Escalates To |
| --- | --- | --- | --- | --- |
| Founder / CEO | [Name] | Vision, growth, key relationships, culture | Full — sets the standard | — |
| [Role Title] | [Name] | [Primary outcome area] | [High / Medium / Defined threshold] | [Founder / Ops Manager] |
| [Role Title] | [Name] | [Primary outcome area] | [High / Medium / Defined threshold] | [Founder / Ops Manager] |
| [Role Title] | [Name] | [Primary outcome area] | [High / Medium / Defined threshold] | [Founder / Ops Manager] |

---

## OWNERSHIP GAP LOG

*Anything that surfaced during the build that currently has no clear owner. These need to be assigned before this document is considered complete.*

| Workflow / Outcome | Currently Falling To | Recommended Owner | Action Required |
| --- | --- | --- | --- |
| [e.g. Mid-project client check-ins] | Founder by default | [Team Member] | Reassign + add to role doc |
| [e.g. Tracking project completion against timeline] | Nobody | [Team Member] | Assign + build SOP |
| [e.g. Following up on unpaid invoices] | Founder | [Team Member / VA] | Reassign + automate where possible |

---

## HOW TO MAINTAIN THIS DOCUMENT

**Review cadence:** Every 90 days — or immediately when a role changes, a new hire joins, or a new offer launches.

**Who owns the update:** [Founder / Ops Manager]

**What triggers an immediate update:**

- A team member's responsibilities shift significantly
- A new hire joins the business
- A role is eliminated or restructured
- Recurring escalations reveal that a decision boundary needs to be redrawn

---

*Role Clarity Matrix built as part of The Founder-Proof Method by Whitney Radacina. Prepared for [Your Business Name].*
