Decision Rights
and Decision-Rules
Decision Rights
and Decision-Rules
The decisions that keep circling aren't a communication problem. They're a design problem.
The decisions that keep circling aren't a communication problem. They're a design problem.
Decision Rights
and Decision-Rules
The decisions that keep circling
aren't a communication problem.
They're a design problem.
One working session.
A shared taxonomy.
A document you'll actually use.
One working session. A shared taxonomy. A document you'll actually use.
One working session. A shared taxonomy. document you'll actually use.
Limited to 2-4 partnerships only
Limited to
2-4 partnerships only
You know the pattern.
A decision gets made — or seems to. Then three weeks later it's back on the table. Or one partner moves forward and the other finds out in a team meeting. Or you've had the same conversation about a hiring call, a client commitment, a spending threshold, four times now — and each time it closes a little less cleanly than the time before.
You know the pattern.
A decision gets made — or seems to. Then three weeks later it's back on the table. Or one partner moves forward and the other finds out in a team meeting. Or you've had the same conversation about a hiring call, a client commitment, a spending threshold, four times now — and each time it closes a little less cleanly than the time before.
You know the pattern.
A decision gets made — or seems to. Then three weeks later it's back on the table. Or one partner moves forward and the other finds out in a team meeting. Or you've had the same conversation about a hiring call, a client commitment, a spending threshold, four times now — and each time it closes a little less cleanly than the time before.
It's not that you can't make decisions. It's that the process for making them was never designed. Who decides what. At what level. With what input from the other person. What it means for a decision to actually be close
Most partnerships built that process by accident — through habit, through whoever stepped up first, through goodwill carrying what explicit agreement should have. That works for
a while. It stops working when the business grows past it.
The decisions that are circling now aren't circling because of who you are. They're circling because the system was never built to close them.
It's not that you can't make decisions. It's that the process for making them was never designed. Who decides what. At what level. With what input from the other person. What it means for a decision to actually be close
Most partnerships built that process by accident — through habit, through whoever stepped up first, through goodwill carrying what explicit agreement should have. That works for
a while. It stops working when the business grows past it.
The decisions that are circling now aren't circling because of who you are. They're circling because the system was never built to close them.
It's not that you can't make decisions. It's that the process for making them was never designed. Who decides what. At what level. With what input from the other person. What it means for a decision to actually be close
Most partnerships built that process by accident — through habit, through whoever stepped up first, through goodwill carrying what explicit agreement should have. That works for
a while. It stops working when the business grows past it.
The decisions that are circling now aren't circling because of who you are. They're circling because the system was never built to close them.
You know the pattern.
A decision gets made — or seems to. Then three weeks later it's back on the table. Or one partner moves forward and the other finds out in a team meeting. Or you've had the same conversation about a hiring call, a client commitment, a spending threshold, four times now — and each time it closes a little less cleanly than the time before.
You know the pattern.
A decision gets made — or seems to. Then three weeks later it's back on the table. Or one partner moves forward and the other finds out in a team meeting. Or you've had the same conversation about a hiring call, a client commitment, a spending threshold, four times now — and each time it closes a little less cleanly than the time before.
You know the pattern.
A decision gets made — or seems to. Then three weeks later it's back on the table. Or one partner moves forward and the other finds out in a team meeting. Or you've had the same conversation about a hiring call, a client commitment, a spending threshold, four times now — and each time it closes a little less cleanly than the time before.
It's not that you can't make decisions. It's that the process for making them was never designed. Who decides what. At what level. With what input from the other person. What it means for a decision to actually be close
Most partnerships built that process by accident — through habit, through whoever stepped up first, through goodwill carrying what explicit agreement should have. That works for
a while. It stops working when the business grows past it.
The decisions that are circling now aren't circling because of who you are. They're circling because the system was never built to close them.
It's not that you can't make decisions. It's that the process for making them was never designed. Who decides what. At what level. With what input from the other person. What it means for a decision to actually be close
Most partnerships built that process by accident — through habit, through whoever stepped up first, through goodwill carrying what explicit agreement should have. That works for
a while. It stops working when the business grows past it.
The decisions that are circling now aren't circling because of who you are. They're circling because the system was never built to close them.
It's not that you can't make decisions. It's that the process for making them was never designed. Who decides what. At what level. With what input from the other person. What it means for a decision to actually be close
Most partnerships built that process by accident — through habit, through whoever stepped up first, through goodwill carrying what explicit agreement should have. That works for
a while. It stops working when the business grows past it.
The decisions that are circling now aren't circling because of who you are. They're circling because the system was never built to close them.
What decision drag actually is.
Not a trust problem. Not a failure to communicate. An absent structure.
When decision authority isn't explicit — who decides what, at what level of agreement, with what process when you can't agree — two things happen at once.
Decisions that could close in ten minutes take three conversations. And the decisions that actually need both of you get buried under the ones that don't.
The fix isn't more conversation. It's a Decision Rights Charter — a working document that makes the implicit explicit. Who has authority for what category of decision. What level of agreement each category requires. What happens when you reach genuine deadlock.
Built once. Referenced continuously. Revised as the business changes
What decision drag
actually is.
Not a trust problem. Not a failure to communicate.
An absent structure.
When decision authority isn't explicit — who decides what, at what level of agreement, with what process when you can't agree — two things happen at once.
Decisions that could close in ten minutes take three conversations. And the decisions that actually need both of you get buried under the ones that don't.
The fix isn't more conversation. It's a Decision Rights Charter — a working document that makes the implicit explicit. Who has authority for what category of decision. What level of agreement each category requires. What happens when you reach genuine deadlock.
Built once. Referenced continuously. Revised as the business changes
What you leave with.
Inform. Consult. Consent. Consensus. Four levels. One shared language for classifying any decision so the right process matches the right stakes — and so you stop treating everything like it requires full agreement when most of it doesn't.
A working first draft of your Decision Rights Charter
Not a template with your names on it. A real document with your actual decisions classified, spending thresholds established, client commitment thresholds named, escalation paths agreed, and personnel decision authority made explicit. This is what you take away.
An agreed meta-decision maker mechanism
What happens when you reach genuine deadlock. Agreed in advance — not negotiated in the moment, which is the worst possible time to figure out how to resolve a disagreement.
A two-week practice commitment
Three specific decisions to run through the Charter before the next session.
A baseline metric to track. The beginning of a practice, not the completion of a workshop.
What you leave with.
Inform. Consult. Consent. Consensus. Four levels. One shared language for classifying any decision so the right process matches the right stakes — and so you stop treating everything like it requires full agreement when most of it doesn't.
A working first draft of your Decision Rights Charter
Not a template with your names on it. A real document with your actual decisions classified, spending thresholds established, client commitment thresholds named, escalation paths agreed, and personnel decision authority made explicit. This is what you take away.
An agreed meta-decision maker mechanism
What happens when you reach genuine deadlock. Agreed in advance — not negotiated in the moment, which is the worst possible time to figure out how to resolve a disagreement.
A two-week practice commitment
Three specific decisions to run through the Charter before the next session.
A baseline metric to track. The beginning of a practice, not the completion of a workshop.
This is a working session.
The final thirty minutes are for something harder than the Charter build: working a live, charged decision through the full Disagreement Protocol. Not a simulation. A real decision your partnership hasn't been able to close — with the Charter in hand, the meta-decision maker agreed, and a facilitator in the room coaching the process in real time.
Most partnerships have never run a structured disagreement process on a real decision. The experience of doing it — seeing that the process can hold a genuinely difficult conversation and produce a genuine closure — is the most important thing the session produces.
You leave with a document and a practice. The document gets stronger every time you use it.
This is a working session.
The final thirty minutes are for something harder than the Charter build: working a live, charged decision through the full Disagreement Protocol. Not a simulation. A real decision your partnership hasn't been able to close — with the Charter in hand, the meta-decision maker agreed, and a facilitator in the room coaching the process in real time.
Most partnerships have never run a structured disagreement process on a real decision. The experience of doing it — seeing that the process can hold a genuinely difficult conversation and produce a genuine closure — is the most important thing the session produces.
You leave with a document and a practice. The document gets stronger every time you use it.
This is for you if:
• Your partnership is three or more years in and the informal way you've been making decisions is showing its limits. Decisions keep being revisited. Authority is fuzzy.
• You've had the same conversation about who owns what more than once without it fully resolving. You're both committed to the partnership and ready to do the structural work — not just talk about whether to do it.
• Both partners are attending. Or one is attending now and bringing the Charter back to their partner afterward.
This is not for you if:
• Your primary challenge right now is interpersonal — trust that's been damaged, recurring conflict that has a relational quality, conversations that go badly in ways that feel personal rather than structural. That work is real and it matters. It belongs in a different session. If that's where you are, the CPR Workshop is designed for it. The structural work we're doing here builds on a foundation of sufficient relational safety — it doesn't substitute for it.
This is for you if:
• Your partnership is three or more years in and the informal way you've been making decisions is showing its limits. Decisions keep being revisited. Authority is fuzzy.
• You've had the same conversation about who owns what more than once without it fully resolving. You're both committed to the partnership and ready to do the structural work — not just talk about whether to do it.
• Both partners are attending. Or one is attending now and bringing the Charter back to their partner afterward.
This is not for you if:
• Your primary challenge right now is interpersonal — trust that's been damaged, recurring conflict that has a relational quality, conversations that go badly in ways that feel personal rather than structural. That work is real and it matters. It belongs in a different session. If that's where you are, the CPR Workshop is designed for it. The structural work we're doing here builds on a foundation of sufficient relational safety — it doesn't substitute for it.
This is for you if:
• Your partnership is three or more years in and the informal way you've been making decisions is showing its limits. Decisions keep being revisited. Authority is fuzzy.
• You've had the same conversation about who owns what more than once without it fully resolving. You're both committed to the partnership and ready to do the structural work — not just talk about whether to do it.
• Both partners are attending. Or one is attending now and bringing the Charter back to their partner afterward.
This is not for you if:
• Your primary challenge right now is interpersonal — trust that's been damaged, recurring conflict that has a relational quality, conversations that go badly in ways that feel personal rather than structural. That work is real and it matters. It belongs in a different session. If that's where you are, the CPR Workshop is designed for it. The structural work we're doing here builds on a foundation of sufficient relational safety — it doesn't substitute for it.
The details
Session format:
90 minutes core working session + 30 minutes experiential
Both partners strongly recommended
— one partner can attend and bring the Charter back
Virtual: Zoom
Date: April 23, 2026
Time: 4pm PT / 7pm ET
A note on the pilot.
This is one of the first runs of this session.
Capacity is limited to up to 4 partnerships only.
Participants are asked to complete a brief pre-session diagnostic beforehand
and share observations after — your experience directly shapes how the
session develops. If you want to be in the room while something is being
refined rather than after it's been polished, this is that moment.
Capacity is limited to up to 4 partnerships only.
Participants are asked to complete a brief pre-session diagnostic beforehand and share observations after
— your experience directly shapes how the
session develops. If you want to be in the room while something is being refined rather than after
it's been polished, this is that moment.
WHAT COMES NEXT
This is the first of several modules.
The Charter you build today has one intentional gap:
Domain Ownership. The decisions you couldn't classify — because it wasn't clear whose domain they live in — are the agenda for the next session.
Role Clarity and Ownership Map closes that gap. It establishes who owns which domains, where authority actually lives versus where it's assumed, and how gray areas get handled. Decision rights without domain ownership float — they attach to people rather than functions, and they drift. Role Clarity is what anchors the Charter you're about to build.
These two sessions together — Decision Rights and Role Clarity — form the structural core that every other OS module builds on. Operating Rhythm. Repair Protocol. Partnership Accord. Each one assumes the Charter and the Role Map are in place.
The full Partnership OS Program is nine modules over nine months. This session is the beginning of that arc — or a standalone starting point if you want to see what the work actually feels like before committing to the full program.
WHAT COMES NEXT
This is the first of several modules.
The Charter you build today has one intentional gap: Domain Ownership.
The decisions you couldn't classify — because it wasn't clear whose domain they live in — are the agenda for the next session.
Role Clarity and Ownership Map closes that gap. It establishes who owns which domains, where authority actually lives versus where it's assumed, and how gray areas get handled. Decision rights without domain ownership float — they attach to people rather than functions, and they drift. Role Clarity is what anchors the Charter you're about to build.
These two sessions together — Decision Rights and Role Clarity — form the structural core that every other OS module builds on. Operating Rhythm. Repair Protocol. Partnership Accord. Each one assumes the Charter and the Role Map are in place.
The full Partnership OS Program is nine modules over nine months. This session is the beginning of that arc — or a standalone starting point if you want to see what the work actually feels like before committing to the full program.
WHAT COMES NEXT SECTION
This is the first of several modules.
The Charter you build today has one intentional gap:
Section 1, Domain Ownership. The decisions you couldn't classify — because it wasn't clear whose domain they live in — are the agenda for the next session.
Role Clarity and Ownership Map closes that gap. It establishes who owns which domains, where authority actually lives versus where it's assumed, and how gray areas get handled. Decision rights without domain ownership float — they attach to people rather than functions, and they drift. Role Clarity is what anchors the Charter you're about to build.
These two sessions together — Decision Rights and Role Clarity — form the structural core that every other OS module builds on. Operating Rhythm. Repair Protocol. Partnership Accord. Each one assumes the Charter and the Role Map are in place.
The full Partnership OS Program is nine modules over nine months. This session is the beginning of that arc — or a standalone starting point if you want to see what the work actually feels like before committing to the full program.
WHAT COMES NEXT SECTION
This is the first of several modules.
The Charter you build today has one intentional gap:
Section 1, Domain Ownership. The decisions you couldn't classify — because it wasn't clear whose domain they live in — are the agenda for the next session.
Role Clarity and Ownership Map closes that gap. It establishes who owns which domains, where authority actually lives versus where it's assumed, and how gray areas get handled. Decision rights without domain ownership float — they attach to people rather than functions, and they drift. Role Clarity is what anchors the Charter you're about to build.
These two sessions together — Decision Rights and Role Clarity — form the structural core that every other OS module builds on. Operating Rhythm. Repair Protocol. Partnership Accord. Each one assumes the Charter and the Role Map are in place.
The full Partnership OS Program is nine modules over nine months. This session is the beginning of that arc — or a standalone starting point if you want to see what the work actually feels like before committing to the full program.
WHAT COMES NEXT
This is the first of several modules.
The Charter you build today has one intentional gap: Domain Ownership.
The decisions you couldn't classify — because it wasn't clear whose domain they live in — are the agenda for the next session.
Role Clarity and Ownership Map closes that gap. It establishes who owns which domains, where authority actually lives versus where it's assumed, and how gray areas get handled. Decision rights without domain ownership float — they attach to people rather than functions, and they drift. Role Clarity is what anchors the Charter you're about to build.
These two sessions together — Decision Rights and Role Clarity — form the structural core that every other OS module builds on. Operating Rhythm. Repair Protocol. Partnership Accord. Each one assumes the Charter and the Role Map are in place.
The full Partnership OS Program is nine modules over nine months. This session is the beginning of that arc — or a standalone starting point if you want to see what the work actually feels like before committing to the full program.
The business you're running now requires more from your partnership than the one you started.
The informal agreements that got you here aren't wrong. They were built for an earlier version of the business — a version where the decisions were smaller, the team was smaller, and goodwill could carry what explicit structure should. The business has grown. The structure hasn't kept pace.
What you build in this session is the beginning of a design that fits the stage you're actually in.
Alignment you can feel and measure.
Reserve your spot
Have an account? Sign in
