Something to doFeedback
Share it when it's ready, and say what you need
A simple exercise to show your work at its best, and get the input you actually need
Why it’s worth your time
People answer the question you ask them, and they judge the version they see first. Sharing once the work is solid, with the input you want named at the top, uses both. What comes back is input you can use, not notes on what's already settled.
How to share work for review and get useful input
You’ll come away with work that's seen at its best, and input on the part you can still change.
We’ll turn this into a checklist you can tick off.
- Get it to solid, not perfect.
Solid means the thinking is done, it hangs together, and you'd be comfortable if it were forwarded. It doesn't mean every sentence is final.
Tip: A quick test: would you mind if it reached someone senior today? If not, it's ready.
- Decide what you need back.
Pick one: a sense check (does this hold up?), a decision (yes or no on a choice), a close edit (line-level notes), or just visibility (no reply needed). Then decide what's settled and not up for change.
- Put the ask in the first lines when you share it.
The ask goes before the work, not at the end, with the date you need it by. Busy people often read the top and skim the rest.
To: the people reviewing itHere's the document, plan or deck for what it's for. It's ready for review.
What would help most: the input you want, for example a check that the numbers hold up. What's settled, for example the timeline is agreed, so no need to look at that part.
Anything by when would be perfect, and a few lines is plenty.
Swap the highlighted parts for your thing. Works on Slack, in email, or said out loud. - Reply to what comes back, briefly.
Thank people and say what you'll change. If someone reopened something that was settled, say why it's staying. A short answer keeps them willing to review next time.
Good moments for this: whenever you share work with people who'll judge itbefore a presentation to senior people or clientswhen past reviews turned into rewrites
We’ll turn this into a checklist you can tick off.
Keep going with Truest
Small actions add up. Truest helps you find the next thing worth doing, make the space to do it, and keep a record of your progress. It’s a private place to work on your career, and it’s yours, not your employer’s.
- It actually happensDo it now, and you’ve invested in your career today.
- Kept with the thing it was aboutSave what comes back in your Vault, next to the work it was about.
- It’s yours to keepEach thing you do is saved to your private record, there when your next review or job search comes around.
Anything else we can help you with this week?
Making it work for you
Every workplace is different. Here’s what to think about before you start, and what might get in the way.
Things to think about
For a close colleague, solid might mean a tight outline. For an executive, it might mean nearly final. Match the bar to the person, not to your own comfort.
What might make this harder
Ask someone who's been there longer what people usually expect to see, or ask your manager what state they like work in when it reaches them.
Questions people ask
How do I ask for specific feedback on a document?
Put the ask in the first lines: what you want checked, what's already settled, and when you need it. People tend to answer the question you ask.
Should I share work before it's finished?
It depends on your workplace and your reader. Where early versions get judged as finished, wait until it's solid. Where people are used to drafts, sharing early can save you rework.
How do I stop people rewriting my work in review?
Say what's settled and what kind of input you want. A lot of over-editing comes from reviewers guessing what's expected of them.
Why this works, and where it comes from
First impressions stick at work, and that includes impressions of work. A senior person who sees a half-built version may quietly file it as not there yet, and that view can outlast every improvement you make afterward. In plenty of workplaces, the version people see first is the version they remember. That isn't unfair so much as busy: they may only look once.
Reviewers have a problem of their own. Handed a document with no instructions, they have to guess what you want. Many fall back on what's easy to comment on, the wording, the formatting, their own preferences, and the one thing you needed checked gets a line at the end. Naming the input you want gives them a job they can do well. Naming what's settled saves them time they'd otherwise spend on something you can't change.
Being explicit can feel a little presumptuous, as if you're telling senior people how to review. It rarely lands that way. It tends to read as someone who knows what they're doing and respects the reviewer's time, and it gets you a faster answer.
Waiting isn't right for every piece of work. When you're unsure the approach is right at all, you can't polish your way to certainty. A rough look from one trusted colleague will tell you more than another day of finishing.
Other simple things to consider
More in Feedback
See allRead this alongside your role page
Tell Truest what you’re dealing with
We read every one, and we write guides for the things that come up most. Leave your email if you’d like to hear when we do.
An exercise written by Truest, based on our experience. Last updated September 25, 2026. We sell a career membership; where that’s relevant above, we say so.