“Any feedback for me?” is easy to answer with “Keep doing what you’re doing.” It leaves you with little guidance for your next piece of work or a promotion case. A designer who has revised an onboarding flow needs a more precise conversation: Was the problem-framing sound? Did the collaboration help the team make a decision? Is there evidence that the change improved the experience? How to ask your manager for feedback depends on which of those questions you need answered now.
Do you need feedback on work that is still in progress?
Ask while there is time to change your approach. Bring the decision you are facing, the options you have considered, and the constraint that makes the choice difficult. A broad request for an opinion invites a broad reaction; a specific decision gives your manager a way to help.
You might say, “I’m choosing between simplifying the first screen and moving the explanation later. My concern is that either choice could hide information new users need. Which risk would you investigate first?” Your manager may point out a consideration you missed or suggest a way to test the choice. Leave with the next action written down, then note why you chose it. That decision record can become useful evidence of your judgment later.
Has the work finished, but you are unsure what mattered?
Ask about the result and your contribution separately. You may know that a new flow shipped without knowing whether your manager sees your research, design decisions, or cross-functional work as the strongest part. Bring a short account of what changed and whatever evidence you can responsibly share.
Try: “The team adopted the revised flow, and I led the usability work that changed its direction. Which part of my contribution had the most value, and where was my approach less effective?” This makes room for criticism without turning the conversation into a request for reassurance. Record the answer alongside the work itself. If the outcome is still being measured, label it that way rather than treating a launch as proof of success.
Are you trying to understand promotion readiness?
Name the scope you are aiming for and ask for a comparison grounded in your work. “Am I ready?” asks for a verdict that may depend on evidence neither of you has assembled. A better question gives your manager an example and asks what it demonstrates.
For instance: “I led the onboarding redesign from the initial research through the handoff, including resolving conflicting feedback. Which parts show the independence expected at the next level, and what would you still need to see?” Ask for concrete gaps you can act on, such as a larger problem to own or stronger proof of an outcome. Do not assume one successful project settles the case. Promotion discussions also depend on the expectations and process where you work, so clarify those with your manager rather than guessing.
If those expectations are vague, this guide to understanding your promotion criteria can help you translate them into observable work.
Did the feedback sound too general to use?
Follow up on the same example before changing topics. “Be more strategic” could refer to problem selection, the way you weigh evidence, or how you explain tradeoffs. Ask your manager to identify a moment when a different choice would have helped.
A useful follow-up is: “When you say I should involve partners earlier, which decision would have benefited from their input?” You can then agree on a behavior to try during the next project and a point when you will revisit it. Write down the example your manager gives you. Without that detail, vague feedback is hard to test and easy to misremember.
What should you do with the answer afterward?
Keep the feedback next to the relevant accomplishment, not in a disconnected list of comments. Note what your manager observed, what you plan to change, and which future work could show progress. On your next check-in, return to the same point: “I brought partners into the problem-framing discussion before drafting options. Did that address the concern you raised?”
ImpactLogr can help you preserve the work example and the feedback together, so a later review does not depend on remembering the conversation perfectly. To make the next discussion more concrete, keep your work and feedback in ImpactLogr after your check-in. Record the substance of the conversation without transferring confidential files or private customer information.