How to Write a Message Asking What Success Looks Like
The most expensive misunderstanding at work is the one about what “good” means. You are handed a task, you build what you think is right, and you find out at the end that the person wanted something else entirely. Asking what success looks like before you start prevents that, but people avoid the question because they worry it signals they do not know how to do their job. It signals the opposite. The people who ask what “done well” means are the ones who deliver it.
The skill is asking in a way that gets a concrete answer, not a vague “you know, just make it good.” A well-framed question pulls the real criteria out of someone who had not articulated them even to themselves.
Ask For The Criteria, Not The Vision
“What’s your vision for this?” produces a speech. “How will you judge whether this is successful?” produces criteria. You want the criteria, because those are what you will actually be measured against, and they are usually more specific and more revealing than the vision.
Framing the question around judgment also surfaces constraints the person forgot to mention: the audience, the length, the one stakeholder who must approve, the thing that absolutely cannot happen. The clarifying instinct is the same one in how to ask a clarifying question when the brief is vague.
Offer Your Own Definition First
The fastest way to get a precise answer is to propose one and ask them to correct it. People find it far easier to react to a concrete definition than to generate one from scratch, so hand them something to react to.
Before:
Before I start, can you tell me what you’re looking for with this project? I want to make sure I understand your expectations and deliver something that meets your needs. What does success look like to you?
After:
Before I dig in, let me check I’m aiming at the right target. My assumption: success here is a one-page summary the exec team can read in five minutes and use to approve or reject the budget, so it needs the recommendation and the three numbers behind it, not the full analysis. Is that the right bar, or are you actually looking for something more detailed?
The second version offers a specific definition and a specific alternative, which is far easier to confirm or correct than an open question. It also demonstrates you have thought about it. For turning the answer into a working document, how to write a one-page project brief is the next step.
Pin Down What “Good Enough” And “Too Much” Both Mean
Success has two edges people forget: the floor and the ceiling. Ask not just what a great result looks like, but what the minimum acceptable version is, and whether there is such a thing as over-building it. Knowing the floor lets you ship something useful under time pressure; knowing the ceiling stops you gold-plating a task that wanted a quick answer.
This is also where you catch the mismatch between effort and expectation early, before you have spent a week on something that wanted an afternoon. Goal-setting that avoids this trap is covered in how to write OKRs that are not a task list.
Confirm It In Writing
Whatever the answer, write it back in one line and get a yes. A verbal “yeah that sounds right” evaporates; a written “so success is X, confirmed?” is something you can point to when the definition quietly shifts later. This is the same record-keeping value as confirming any agreement.
A Wrivio Context for asking what success looks like could say:
Rewrite this as a concise message asking someone to define success for a task before I start. Frame it around the criteria they will judge by, offer my own specific definition for them to confirm or correct, and ask for the minimum acceptable version too. Keep every detail, number, and name exactly as written. Do not make it sound uncertain about my ability, and do not turn it into an open-ended request for their vision.
Press Ctrl+Shift+Space, paste your draft, and check the diff to confirm it offers a concrete definition rather than an open question. The plain language guidelines reinforce that specific questions get specific answers.
Common Questions
How do I ask what success looks like without seeming unsure?
Frame the question around the criteria they will judge by and offer your own specific definition for them to confirm or correct, which demonstrates you have thought it through rather than signaling you do not know your job.
Why offer my own definition first?
Because people find it far easier to react to a concrete definition than to generate one from scratch, so proposing “my assumption is X, is that right” pulls a precise answer faster than an open “what’s your vision.”
What should I ask besides the ideal outcome?
The floor and the ceiling: the minimum acceptable version, which lets you ship something useful under pressure, and whether the task can be over-built, which stops you gold-plating something that wanted a quick answer.
Should I confirm the answer in writing?
Yes, write the agreed definition back in one line and get a yes, because a verbal “sounds right” evaporates while a written confirmation is something you can point to when the definition quietly shifts later.
Download Wrivio for Windows to rewrite a vague “what are you looking for” into a sharp question that gets a real answer.
Read Next
How to Write a Message Asking a Vendor for a Better Price
Negotiating a vendor's price in writing without souring the relationship. How to ask for a discount so it reads as a reasonable business request, not a squeeze.
How to Ask for Written Confirmation of a Verbal Agreement
You agreed something out loud and want it on record. How to confirm a verbal agreement in writing without sounding like you distrust the other person.
How to Tell a Client You Used AI on Their Work
A field-tested way to tell a client you used AI on their deliverable that leads with your judgment and answers the confidentiality question directly.
How to Write a Message Handing Back Work That Is Not Ready
Someone sent you work that is not good enough yet. How to hand it back so it gets fixed, without crushing the person or triggering a defensive rewrite war.
This article is filed underWorkplace Writing, which has 261 articles.