Setting Clear Expectations

You spent the last unit diagnosing where trust frays. One of the quietest sources of erosion never shows up as a dramatic breakdown: it's the slow drip of unclear expectations. When a report doesn't know what "done" looks like, who decides what, or where your support starts and stops, they either stall waiting for permission or guess wrong and redo the work. Either way, your reliability takes the hit even when you did nothing visibly wrong. Setting expectations with clarity is how you build trust on purpose instead of repairing it after the fact.

RACI sorts everyone on a piece of work into four roles. Responsible is whoever does the actual work. Accountable is the single person who owns the outcome, usually you, and it should be exactly one name. Consulted are the people whose input you gather before a decision. Informed are the people you update after a decision is made.

The two mistakes that cost you most are blurring Accountable and Responsible so no one knows who owns the result, and over-stuffing the Consulted column so every call needs a committee. Before you hand anything off, write the names down. If you can't name a single Accountable person, the work isn't ready to delegate.

• Jessica: Before I pull the segment data, do I need sign-off from Legal first?
• Ryan: Legal is Consulted, not a gate. Get their input on the privacy language, but the call on which segments to include is yours.
• Jessica: And if a sales lead pushes back on the scope?
• Ryan: That's yours too. You're Responsible, I'm Accountable. Loop me in only if a scope change blows the August deadline.
• Jessica: Got it. I keep moving unless the timeline's at risk.

Notice Ryan didn't just assign roles; he told Jessica exactly which decisions she can make alone. That's the line between RACI as a chart and RACI as a working agreement.

A spoken handoff feels efficient and disappears by week three. A short written delegation brief makes the expectations durable and surfaces the gaps before they become friction. Structure it around four parts.

Start with Outcomes in observable terms. Not "good research" but something you could hold up and verify: "three segment briefs, executive-readable, with a recommendation each, by August 30." Then name Constraints: the budget, the headcount, the non-negotiable dates, and any methods that are off the table.

Third, spell out Decision Rights using RACI explicitly, and go one step further by listing which specific calls the person can make without you versus which they must surface. Finally, define Support: the standing check-in cadence, the access you'll unblock, the point where you'll review a draft, and the escalation path when they're stuck.

The test of a good brief is simple. Could the person act for two weeks without coming back to you for permission on things they could decide themselves? Vagueness here doesn't read as freedom; it reads as a trap, and conscientious people respond to it by over-checking.

The brief sets the terms; the kickoff conversation makes them stick. Run it as a teaching conversation, not a status update. Open by asking what stood out and what they want to push on, so you hear their read before you correct it. Walk them through the priority order for when parts of the work collide, because they will. Then surface the risks the brief didn't fully name: the review window that's tighter than it looks, the stakeholder who slow-walks work they didn't ask for.

The most important move is to confirm decision rights by testing them, not restating them. Hand over a specific scenario and ask "what's your call?" When they answer with a real decision instead of "what would you do?", you know the expectation transferred. Close by having them name back the priorities, the top two risks, and the decisions they own.

Clarity isn't bureaucracy; it's the form trust takes before the work begins, because a person who knows exactly what they own can act without waiting for you. Next you'll spot-check that instinct by matching real project scenarios to the right RACI role, then build a delegation brief you could hand to someone this week, and finally take it into a live kickoff where the expectations get pressure-tested out loud.