Something to doFeedback
Ask what advice they'd have given you
A simple exercise to hear what someone really thought of work you've already finished
Why it’s worth your time
Asking what someone would have advised tends to get a more specific, more candid answer than asking what they thought. Feedback asks them to judge you after the fact; advice asks them to help, which feels safer to give and points at next time. The past-tense version means you don't have to wait for the next project to ask.
How to ask for feedback after a project
You’ll come away with one thing to keep doing and one to think about changing, from someone who saw the work.
We’ll turn this into a checklist you can tick off.
- Pick one finished thing and one person who saw it.
A project that just wrapped, a launch, a presentation, a tricky thread you handled. Choose someone close enough to have a view, whose judgment you'd trust if you had to do it again.
Tip: Recent is better. Within a couple of weeks, the details are still there for both of you.
- Ask the hindsight question.
In person or in writing. Writing gives them a minute to think, which often gets you a better answer. Say what the thing was and that you're trying to learn from it before the next one.
To: someone who saw the workCould I get your advice on the thing you finished? Now that it's done, I'm trying to learn from it before the next one.
If I'd come to you before I started, what advice would you have given me? I'm especially curious what you'd keep and what you'd think about changing.
A few lines would be plenty, or we could talk it through over coffee if that's easier.
Swap the highlighted parts for your thing. Works on Slack, in email, or said out loud. - Listen for what to keep, not only what to change.
The keep side is easy to skim past, and it's where some of the most useful information hides. If all you hear is that it went great, ask about one specific choice.
You“If it had been yours, what's one call you'd have made differently?” - Thank them and write down one of each.
One thing to keep doing, one to try differently. You don't have to act on everything they said.
Tip: Let them see the advice show up in the next piece of work. That's what makes people glad they answered.
Good moments for this: a week or two after something wrapsafter a presentation or a launchwhenever you missed the chance to ask beforehand
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
A peer who sat in every meeting often knows more about how it went than a senior person who only saw the result.
What might make this harder
Say so simply and without a defense. Owning it tends to build more trust than explaining the choice.
Questions people ask
How do I ask for feedback after a project is finished?
Ask one person who saw it what advice they'd have given you if you'd come to them before you started. It tends to get more specific, more useful input than asking what they thought, because it points them at what you could do next.
What's the difference between asking for feedback and asking for advice?
Feedback asks someone to judge what you did. Advice asks what they'd suggest. Advice tends to feel safer to give, so people are often more candid.
Is it too late to ask for input once the work is done?
No. Asking afterward still tells you what to keep and what to change next time. It works best within a week or two, while the details are fresh.
Why this works, and where it comes from
Once something is finished, asking for feedback puts people in an awkward seat. It's done, it can't be changed, and anything critical now sounds like a grade on you rather than help with the work. So most people say it went well and move on. Asking what they'd have advised you beforehand turns a verdict into a favor. They get to help rather than judge, and the question points at your next attempt instead of your last one.
The before-you-started frame also gives them permission. They aren't saying you got it wrong; they're saying what they would have mentioned if you'd asked. That small shift is often enough to surface the thing they'd been keeping to themselves. And because it's about one specific piece of work, it's answerable in a few minutes.
Listen hard for the keep side. Much of what makes work go well is invisible to the person doing it: the way you set up a meeting, the update you sent before anyone asked, the call you made early. The things you did right are the ones you're most likely to stop doing by accident. Someone who watched can tell you which they were.
It isn't the right move every time. If the work had real consequences for them, like a missed deadline that landed on their team, start with a plain acknowledgment and a direct conversation about what happened; an advice question there can feel like a sidestep. Reassurance is worth asking for too, just not with this question.
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 October 29, 2026. We sell a career membership; where that’s relevant above, we say so.