Hi Reader,

Your supervisor hands you an assignment. It sounds straightforward enough. You nod. You take notes. You want to be easy to work with. Capable, competent, trusted.

Then you walk back to your desk, sit down, open the file, and realize you don't actually know what "good" looks like.

Here's what happens next for most of us. You do one of two things, and both of them cost you.

You guess, because you don’t want to look unsure.

Or you stall, because you don’t want to get it wrong.

Guessing leads to rework. Stalling kills momentum. And both quietly chip away at trust, because the work either misses the mark or it lands late and rushed.

Years ago, I had a new executive director walk into my office and hand me what he called "a quick community needs assessment" for a grant we were writing. He gave me the name of the grant, the submission deadline, and a warm "I trust you." Then he left for a meeting.

I sat there nodding at his closed door.

I did not know what “good” looked like.

I didn't know if he wanted three pages or thirty. I didn't know if the assessment should focus on the population the grant would serve or the gaps in existing services. I didn't know if "needs assessment" meant interviews and focus groups or just a clean synthesis of existing data. I didn't even know what he had already told the funder to expect.

And I did not want to look unsure. I wanted him to trust me.

So I guessed.

I spent the better part of a week building what I thought was a strong needs assessment. I walked it into his office feeling proud. He flipped through it, nodded politely, and said:

"Oh. I was thinking more like a two-page summary of the three populations we'd prioritize. But this is… helpful context."

I had worked nights on “helpful context.”

The worst part wasn't the wasted hours. It was knowing that one question at the handoff, just one, would have saved all of it.

The people who look most confident at work aren't the ones who never ask. They're the ones who ask early, ask clearly, and ask in a way that signals they're aiming for the outcome, not just completing the task.

If you feel that pull to guess or stall, these are the four questions to ask instead. They're the exact mirror of the four things I gave you last month for the delegator's side of the handoff, flipped around for when you're the one receiving the work.

1. "What does success look like when this is done?"​
This gets you the actual target. What's the real outcome, not just the task? What matters most here: quality, timing, stakeholder experience, risk, something else?

2. "What exactly do you want me to deliver?"​
Sometimes the confusion isn't the work. It's the work product. An outline? A draft? A decision memo? A two-pager? A set of options with a recommendation? What are the must-haves versus the nice-to-haves?

3. "What are the guardrails, and what can I decide on my own?"​
Which decisions are yours, which are shared, and which need to come back for a conversation? Are there constraints you should plan around, like budget, policy, approvals, or political sensitivities? What risks or watch-outs should you be thinking about?

4. "When do you need it, and when should we check in?"​
Not just the final deadline. The first checkpoint too, early enough to course-correct before the wrong version becomes the finished version.

You don't have to ask all four every time. But I'll tell you this: the one you skip is usually the one you'll wish you'd asked.

One more thing I want to name out loud, because it's real.

Asking for clarity is a different kind of risk for different people. If you've learned, through experience, that your missteps get judged more harshly because of your role, your identity, or the dynamics of your workplace, asking for clarity isn't just a work habit. It's a protective practice. Naming expectations out loud is how you get the rules put on the table instead of guessing at them.

The four questions are the same. The stakes of asking them are not. And if you're leading a team, it's worth remembering that some of your people are running a version of this calculation every time you hand them work.

So here's your practice move for this week.

The next time someone hands you a piece of work and you feel that familiar hesitation, the nodding, the note-taking, the quiet panic, try this:

Before you leave the conversation, say, "I want to make sure I'm aiming at the right target. Can I ask you two quick things?" Then pick the two that matter most for this particular piece of work.

And if the conversation moves too fast, or the questions only occur to you afterward, put them in writing. A short "confirming what I heard" email does the same job. It gives you a record, and it lets you think before you ask.

It's not defensive. It's not needy. It's not uncertain.

It's ownership.

Hit reply and tell me which of the four you skip most often. I read every message personally, and knowing where people get stuck shapes what I build next.

To clarity at the handoff,
Sheila

P.S. I turned those four questions into a one-page Clarifying Questions Card, the companion to the Delegation Clarity Card I sent last month, built for the other side of the handoff. It fits on a desk, in a notebook, or inside the folder you bring to your next 1:1. Grab it here (it's free)