The Clarity Framework

The Problem

Your team isn't slow because they're lazy. They're slow because your requests are vague. You say "get the arm working" and then wonder why nobody moved for a week. It wasn't resistance. It was confusion dressed up as hesitation. They didn't know what "working" meant, what it connected to, what would break if they got it wrong, or what you'd sacrifice to get it done. So they waited. And you called it a performance issue.

Most team delays trace back to the same root: unclear asks. Not unclear strategy, not unclear vision — unclear requests. The day-to-day, person-to-person asks that move work forward or leave it stuck. Fix the request, and accountability shows up on its own. You don't have to chase it.

Who This Is For

Founders and operators who keep finding that their team "didn't do what I asked" — and are ready to consider that the problem might be the asking.

What You'll Need

• Time commitment: 5 minutes to structure any request using the 5Cs. 15 minutes to rewrite a past request as practice. Zero additional meetings.
• Prerequisites: At least one recent example of a request that didn't land the way you expected. You'll use it as your worked example.
• Tools: Nothing. The 5Cs are a mental filter. You can run them on paper, in Slack, on a whiteboard, or in your head before you open your mouth.

The Protocol

Why Requests Break

A request has one job: transfer enough information that the other person can act with confidence. Most requests fail not because they lack detail but because they lack the right detail. You give them the "what" but skip the "why it matters." Or you paint a vivid picture of the outcome but forget to mention that three other workstreams depend on their timeline.

The 5Cs are five lenses. Apply them to any request — verbal, written, formal, informal — and you close the gaps that cause delays, confusion, and rework.

The 5Cs

1. Context

Widen the lens. How does their piece of work connect to other projects, other departments, other outcomes? What past experience do they need to understand? Are there stakeholders they should loop in that they wouldn't think to include?

Context is the "zoom out." Most people work with a narrow frame — their task, their deadline, their inbox. Your job when making a request is to give them the wider picture so they can make smart trade-offs without coming back to you for every judgment call.

2. Colour

Paint "done" so vividly they can see it. What does the finished work actually look like? Is this a polished deliverable or a quick test? Is speed more important than precision? What are the red flags that would make you want to know immediately?

Colour is the difference between "get the report done" and "I need a one-page summary with the three biggest cost drivers highlighted — we're using it to decide whether to kill the project by Friday. If the data looks off, flag it before you spend hours cleaning it."

3. Connective Tissue

How does this request connect to other plans, experiments, or decisions already in motion? What are the ripple effects — tomorrow, next week, next quarter? If their work ships late or ships differently than expected, what downstream dominoes fall?

This is the one most leaders skip. They assume the connection is obvious. It isn't. The person doing the work is inside their own scope. They can't see what you see unless you tell them.

4. Cost

What resources does this actually require? Time, money, focus, priority shifts. Can the person realistically carry it alongside everything else on their plate? What existing commitments would need to move? What agreements with other people need renegotiating?

Cost is where honesty matters most. If you're asking for something that requires them to drop everything else, say that. Don't smuggle a priority shift inside a casual ask and then act surprised when something else slips.

5. Consequences

What happens if this doesn't get done, gets done poorly, or misses the deadline? What's at stake for the business, for the team, for a client relationship? What opportunities disappear? What reputation damage lands?

Consequences give weight. Without them, every request feels equally important — which means none of them feel important. When someone understands what's actually on the line, they calibrate their effort accordingly.

Worked Example: The Warehouse Robot

Sarah is a software developer. David is a mechanical engineer. They're building a warehouse robot together. Sarah needs the robotic arm moving so she can test her sorting algorithms. Here's how she walks through the 5Cs before making the request.

Context: "The arm is our biggest dependency right now. Without it, my entire software team is stalled — we can't test sorting algorithms on simulated data alone. That pushes QA back, which pushes the client demo back. I want you to understand the full chain before I ask you to shift priorities."

Colour: "What 'done' looks like: the arm moves on X and Y axes without jamming, can lift a 1kg box, and accepts coordinate commands via USB. I don't care about aesthetics. I don't care about finished housing. Functionality only. Red flags I'd want to hear about immediately: motors overheating during sustained runs, or the gripper dropping boxes at anything above walking speed."

Connective Tissue: "Once the arm is moving, here's the sequence: my team runs sorting tests, then the safety team calibrates sensors around the arm, then we move to volume tests, then we shoot a sales demo video. That video is for the logistics conference in eight weeks. Every day the arm slips, the whole chain compresses."

Cost: "This means shifting your focus away from the battery charging station and the aesthetic casing. Both get pushed. I need you to tell me honestly — is that realistic given your current workload? If it means pulling someone off another project, let's talk about that now rather than discovering it in two weeks."

Consequences: "If you can commit: we'll debug over the weekend, validate the grip mechanism, and make the call on ordering expensive servo parts before the price lock expires. If you can't: my team's timeline pushes right, we risk missing the demo window, and our pilot client — the one who's been patient so far — starts questioning whether we can deliver."

Then she closes with the commitment question: "What's a realistic commitment you can make? Walk me through how you'd get there."

That's it. No ambiguity. No chasing. David knows exactly what's being asked, why it matters, what trade-offs are on the table, and what's at stake. He can make a real commitment instead of a vague "I'll try."

What You'll Find

The first time you run the 5Cs on a real request, you'll probably discover you've been operating on one or two Cs at most. Context and Colour tend to come naturally — most leaders can describe what they want and give some background. It's Connective Tissue, Cost, and Consequences where the gaps live. Those are the Cs that require you to think beyond your own perspective and into the other person's reality.

The second thing you'll notice: the 5Cs slow you down by about two minutes per request. That feels like friction. It isn't. Those two minutes replace the two days of follow-up, clarification, rework, and quiet frustration that vague requests generate. You're not adding time. You're moving it from the back end (where it's expensive) to the front end (where it's cheap).

Within a few weeks of consistent use, something shifts in how your team operates. People stop waiting for permission. They stop asking "what did you mean by that?" They start making decisions within their scope because they actually understand the scope. Accountability stops being something you have to enforce and becomes something that happens because the conditions for it exist.

Adaptations

Async teams (remote/distributed): The 5Cs become even more important when you can't read body language or ask a quick clarifying question across the desk. For any written request longer than a sentence, run the 5Cs as a literal checklist before hitting send. Label them if it helps — put "Context:" and "Consequences:" right in the message. What feels over-structured in person feels like a gift in Slack.

Receiving requests (managing up): Flip the framework. When your board, your investors, or your co-founder makes a vague ask, use the 5Cs as clarifying questions. "Can you give me the Connective Tissue — how does this connect to the fundraise timeline?" You're not being difficult. You're being precise. Most senior leaders respect the push-back because it signals you're thinking beyond the task.

High-frequency environments (daily standups, sprint planning): You don't need all five Cs every time. For routine tasks with established context, Colour and Cost might be enough. Save the full framework for requests that cross team boundaries, carry deadline pressure, or involve trade-offs the other person can't see. The skill is knowing when a request needs two Cs and when it needs all five.

Where This Came From

The 5Cs structure draws from Brené Brown's work on clear communication and accountability — specifically her concept that "clear is kind, unclear is unkind." Brown's research showed that most workplace conflict traces back not to bad intentions but to unstated expectations. The 5Cs take that insight and give it operational teeth: five specific categories of information that, when present, make expectations explicit enough to act on. The adaptation into this framework came from watching founders make the same request-clarity mistakes across dozens of coaching sessions — always surprised when smart people didn't deliver, never examining whether the ask itself was the problem.

Related Protocols

• Daily Communication Clarity Protocol — The daily practice companion to this framework. Uses the 5Cs as a diagnostic filter for every interaction, with an evening review to build the habit over 30 days.
• The Effective Feedback Protocol — When the issue isn't a vague request but a performance gap that needs a direct conversation. How to deliver hard truths without triggering defensiveness.
• The Decision Architecture — Once your requests are clear and your team is delivering, this protocol helps you make the high-stakes decisions that determine what gets requested in the first place.