Learning Cadence editorial, , 7 min readHow we work
You ask how you did and hear that everything was fine. You still do not know which part worked or what to change. Make the request smaller: one situation, one observable part of it and one question the other person can answer.
This guide is for learning from a colleague, manager or collaborator. The conversations and exercises are original fictional examples, not accounts of real employees or tested performance results. Use the worksheet without an account.
The short answer
Name the task, the question and the next attempt.
Choose someone who saw the work. Ask about one part you want to improve, invite a concrete example, then ask what to try next time. Repeat the suggestion back, choose a change you can test and return to the same question after your next attempt. A useful reply helps you act; it does not have to be flattering.
The method
Prepare a request the other person can answer.
A clear question reduces guesswork. It cannot make an unwilling observer candid or turn an opinion into a fact.
01
Choose an observer
Ask someone who saw the part of the work you want to discuss. A colleague who read the final email can comment on its clarity, but may not know how you handled the earlier conversation.
02
Name one task and one focus
Replace How am I doing? with a question about the update, handover or conversation they observed. Pick the part you can change, such as the order of your explanation.
03
Ask for a moment and a next move
Ask where they became uncertain, what helped, or what they would change next time. If the reply is a broad label, request one example before deciding what it means.
04
Agree on what you will try
Repeat the suggestion in your own words. Choose one action within your control and a later opportunity to check it. You can consider advice without promising to follow every suggestion.
A request after a confusing update.
Original situation: you gave a work update. The audience asked several questions about the decision you needed. A colleague heard the whole exchange. You want to improve how you explain that decision.
A broad request would be: How was my presentation? A more useful request for this situation is: Could I ask about today's update? At what point was the decision I needed unclear, and what would you change in the opening next time?
The revised question names the event, invites an observation and points toward a change. It does not ask the colleague to judge your overall ability or agree that the update was bad. Ask when they have time; a request is not an obligation to give an immediate answer.
Turn a vague reply into something you can test.
Suppose the colleague says: You need to sound more confident. That is an evaluation, not yet an instruction you can use. Confidence could refer to pace, volume, wording or how directly you asked for a decision.
Try: Which part gave you that impression? Suppose they reply: I only understood what you wanted when someone asked at the end. Now you have an observation about the order of information. It does not prove that your voice or personality was the problem.
You could check: So next time I should state the decision first, then explain the background. Is that the change you mean? The proposed action now matches the example. If they meant something else, this is the moment to correct your understanding.
Check the change against the original problem.
For the next update, write the decision request before the background. Afterward, ask the same colleague whether the requested decision was clear from the opening and which sentence helped or confused them.
That follow-up checks the specific change. A compliment is welcome, but it does not answer whether the audience understood the decision. Other differences between meetings can affect the result, so one better exchange does not establish that the new opening caused an improvement.
Keep a short private note: the observed problem, the change you tried and what you learned afterward. Avoid copying confidential work or comments about other people into a public worksheet, an app or a shared document.
Ask what to do next, as well as how it went.
Yoon and colleagues reported four experiments in which requests for advice elicited more actionable input than requests for feedback. Their explanation is that advice directs attention toward future action. They also found that a development focus could make feedback similarly actionable, and noted that novices may need encouragement.
The practical lesson is to ask for a usable next move, not to treat advice as a magic word. Their research does not validate this worksheet, guarantee an honest answer or establish that every recommendation is correct.
After an email: Which sentence made the next action unclear, and how would you rewrite that part? Ask a reader of the email, rather than someone who only knows your intentions.
After a handover: What did you have to ask me again before you could start? What should I include next time? This focuses on missing information rather than whether the colleague likes your handover style.
After facilitating a discussion: Was there a moment when I closed down an idea too early? What could I ask at that point next time? If the person did not notice such a moment, accept that answer rather than pressing them to invent one.
Try a different case.
Original practice case: you handed a task to a colleague. Later they said the handover was messy. You do not know whether the problem was timing, missing information or ownership. Before reading on, write a follow-up question and one thing you would wait to learn before changing your process.
One reasonable answer: When did you first have to stop and ask for something, and what was missing then? I would wait to learn what caused that interruption before deciding to write a longer handover.
Why it works: the question asks for an observable moment and a specific gap. A longer document might add noise if the real issue was that nobody knew who could approve the work. Another answer can pass if it names the actual task, invites evidence without leading the witness and leaves room for the diagnosis to change.
Handle disagreement and power carefully.
A manager asking a direct report for criticism creates a different situation from two peers reviewing an email. The person may not feel free to disagree. Do not demand a public answer, promise anonymity you cannot provide or treat silence as approval. Offer time and an appropriate existing channel instead.
If two people disagree, ask which audience, task or moment each is describing. Advice for a short decision update may conflict with advice for a detailed reference note. Resolve the context before averaging the suggestions together.
You do not have to accept personal insults as useful feedback. Separate any specific work example from the label. Serious workplace concerns belong in the appropriate support or reporting process, not in an exercise that promises a better script can fix them.
Practice the conversations behind the request.
If asking a clear question is only part of your goal, try Cadence. We make the app. Describe the conversation you want to handle, then answer the setup questions to build a course around your starting point. You can work on listening, clarifying and responding through lessons and practice.
The linked course pages are starting goals you can adapt, not fixed lessons or a promise that a colleague will respond differently. The request and worksheet here are complete on their own. Cadence does not observe your workplace or verify that someone's advice is accurate.
Free feedback worksheet
Prepare one request and one follow-up.
Keep workplace details private. The worksheet is a blank planning aid with an original practice case and answer check.
FEEDBACK REQUEST WORKSHEET
Learning Cadence | Original exercise | 30 October 2026
Keep confidential work and information about other people out of this file.
PREPARE
Work I want to improve:
Person who observed it:
One part they can comment on:
My question about a specific moment:
What I could ask about a next attempt:
MAKE THE REPLY USABLE
Specific observation (not a label):
What remains unknown:
Suggestion in my own words:
One change I can try:
Next opportunity to check the same question:
What I observed afterward:
PRACTICE CASE
A colleague calls your handover messy. You do not know whether timing, information or ownership caused the problem. Write a follow-up question. What would you wait to learn before changing the process?
ONE REASONABLE ANSWER
When did you first have to stop and ask for something, and what was missing then? Wait to identify the interruption before assuming a longer document would help. Other answers can pass if they name the work, invite a concrete example without assuming the cause, and allow the diagnosis to change.
A script cannot guarantee candor, safety or better performance.
Put it into practice
Build the skill behind a clearer conversation
If you want to practice asking, listening and responding, try Cadence. Describe your goal and answer the setup questions to build your course. Cadence is our app.
Name a task they observed and the part you want to improve. Ask for an example and a suggestion for your next attempt. Agree on a suitable time rather than expecting an immediate answer.
What if the answer is just that I did fine?
Ask what specifically worked and what they would change next time. If they have nothing to add, accept that. An absence of criticism does not prove that every part was effective.
Should I ask for advice instead of feedback?
A future-focused request can help make input actionable. Ask what to try next, while checking that the person understood the task. No single word guarantees useful advice.
Can I use the worksheet without the app?
Yes. Read the complete exercise here or download the plain-text worksheet without an account. Cadence is optional further learning.
See it in concrete terms
Explore example courses for your goal.
These are starting goals. Adapt the goal to your conversation and answer the setup questions in Cadence. They are not fixed workplace training or a guarantee of performance.
We separated an observed work example, a broad evaluation and a suggested action. The worked update and new handover case show how the diagnosis changes the next question. All conversations are fictional.
What we checked directly: On 30 October 2026 we read the authors' Harvard-hosted research summary, including its development-focus comparison and novice limitation. We checked that the practice answer does not assume an unobserved cause.
Limits of this review: We did not test this worksheet with employees, observe workplace conversations or measure performance gains. Cadence does not verify the advice a colleague gives.
