Career Growth
Ask for Feedback on a Skill You Are Practicing Without Asking for a General Rating
Request focused feedback before a practice opportunity by agreeing the behavior, evidence and debrief with an observer. A complete request comparison and two fictional rehearsals show how to retain useful actions, identify a remaining gap and choose another practice target without claiming mastery or asking for a general rating.
Ask for feedback on a skill by naming the next situation, the behavior you want observed and the kind of evidence that would help you practice again. Give the observer a narrow job: notice what you did, show you an example and discuss one change. “Am I good at this?” asks for a general judgment that may not tell you what to do next.
You do not need a formal rating to improve a small part of your work. This LandOffer.ai guide shows a completed request comparison and a two-rehearsal feedback record. The conversations and observations are entirely authored fiction. They illustrate a usable practice loop; no employee was assessed or improvement measured.

Choose a behavior someone can actually observe
Start with a situation coming soon: a requirements conversation, a short technical explanation or a written recommendation. Then select one behavior within it. “Become more strategic” is too broad for a colleague observing five minutes. “Summarize the request and its constraint before proposing a solution” gives that colleague something specific to notice.
Keep the practice goal separate from the whole job. Someone could summarize a request well while still misunderstanding the technical domain. Conversely, a useful technical suggestion does not prove they listened carefully. Ask for the observation that fits the skill rather than treating a favorable outcome as evidence for everything.
MIT Human Resources recommends choosing an experienced, trusted colleague, defining the focus and boundaries of a feedback request, and asking for specific examples. That supports a bounded request; it does not guarantee that any particular colleague's view is accurate or complete. MIT coaching guidance.
Choose evidence the observer can supply. A reviewer of a document can point to a sentence but cannot tell you whether you let someone finish speaking. A colleague who watched only the closing minute cannot reliably describe the opening. Match the request to what the person will see. An empty observation field should mean unobserved, not a failed behavior; let the person say when they did not see enough.
Agree the observation before the practice
Ask whether the person has time and is willing to help. Name the work sample or practice situation, the duration, the focus and when you would like to debrief. Supply only the context needed to understand the task. Avoid attaching a large confidential thread when a synthetic prompt would work.
For an interpersonal skill, agree whether this is a rehearsal or real work. A rehearsal lets you pause and try again. A live meeting includes other people's time and responsibilities; do not turn it into an undisclosed assessment or introduce recording without the appropriate agreement and policy checks.
UCSF's Ask-Tell-Ask resource emphasizes setting feedback expectations, observing behavior, inviting learner reflection and discussing next steps. It comes from medical education. Applying those general coaching principles to the fictional workplace rehearsals here is an editorial adaptation, not evidence of clinical or workplace effectiveness. UCSF feedback guidance.
Use a small observation note rather than a personality scale. Ask the observer to capture a phrase or action, its immediate effect on their understanding, and a possible alternative. An interpretation such as “you seemed impatient” needs to be distinguished from an observation such as “you proposed a tool before the speaker finished describing the constraint.”
Worked asset one: replace a rating request with an observation request
In this fictional example, developer Quentin is practicing how to clarify a colleague's request before suggesting a technical solution. Mabli will play the requester. Ari, an experienced colleague, agrees to observe two short rehearsals. No real customer information, recordings or production decisions are involved.
Quentin originally writes: “Can you tell me whether I am good at gathering requirements? Please rate my communication out of ten.” Ari could answer that question without showing Quentin a single behavior to repeat or change. A high score might reassure him while leaving the next conversation unchanged.
Quentin replaces it with this complete request:
Ari, could you observe a five-minute rehearsal with Mabli, then spend five minutes debriefing with me? I am practicing summarizing the requested outcome and constraint before suggesting a solution. Please note my first proposed solution, whether I checked my summary with Mabli, and one question that helped or narrowed the discussion too early. Use a phrase you heard rather than a score. It is fine to mark something unobserved. I will try one adjustment in a second rehearsal with a different prompt if you have another ten minutes.
| General request | What it leaves unclear | Completed focused alternative |
|---|---|---|
| “How was my communication?” | Which behavior, situation or evidence matters | “In the rehearsal opening, did I check my understanding before suggesting a tool? Note the phrase.” |
| “Was I confident enough?” | Confidence may be inferred from style or personality | “When I did not know the constraint, did I name that gap and ask a question rather than assert an answer?” |
| “Would you give me a higher rating now?” | A changed score need not explain a changed action | “Compare the two openings against the same agreed behavior. What changed, and what is still missing?” |
Ari accepts two ten-minute blocks, each containing five minutes of rehearsal and five minutes of debrief: 20 minutes total. The dialogue excerpts below illustrate selected moments within those planned blocks; they are not timed recordings. Quentin supplies two short fictional prompts and the observation focus beforehand. These are voluntary arrangements within the example, not a required workplace feedback format or a request actually sent to a colleague.
The request is narrow without dictating praise. Quentin does not ask Ari to confirm that he is a good listener. He asks for evidence that could show a missed behavior and explicitly allows an incomplete observation. He also keeps the next attempt small enough for Ari's available time, so the colleague can give a concrete example without preparing a broad performance assessment.
Worked asset two: a completed two-rehearsal feedback record
Practice focus: reflect the requested outcome and known constraint, check the summary, then ask a question before proposing a solution. Observation scope: the first five minutes of each fictional conversation. No overall score: the notes describe specific behavior, not general communication competence.
Rehearsal one: finding training material
Mabli's first prompt is: “New colleagues cannot easily find the training recordings they need. They usually ask someone for a link. We have limited time to maintain another system.”
Quentin replies: “We should put a search assistant over the recordings.” He later asks which recordings new colleagues need, but does not first check the maintenance constraint or who has access to the materials.
In the debrief, Quentin says, “I think I went straight to the tool because I recognized the search problem.” Ari replies, “Your first response proposed a search assistant. I did not hear a summary of the maintenance constraint or a check with Mabli before that. Your later question about which recordings was useful, but it came after you had framed the answer.”
Quentin checks his understanding: “So the change is to summarize the need and constraint, confirm them, and ask what is missing before choosing a tool.” Ari agrees that this matches the intended practice focus. He does not conclude that a search assistant is technically wrong; the rehearsal did not establish that either way.
Selected adjustment: Quentin will use a brief summary followed by an open question about the remaining constraint. He will keep the useful habit of asking which material is involved. He will not try to fix presentation style, speaking speed and all requirements techniques at the same time.
Rehearsal two: instructions away from the network
Mabli's different prompt is: “Field colleagues need the current maintenance instructions when they are away from the network. Some instructions change frequently, and outdated copies would be a problem.”
Quentin replies: “You need current instructions away from the network, and frequent changes make stale copies risky. Have I understood that correctly?” Mabli confirms. Quentin then asks, “So would a cached copy solve this?”
Ari's debrief is mixed: “This time you summarized both the need and the stale-copy concern, and Mabli confirmed it before you proposed an approach. The next question introduced caching as the answer. We still do not know how people learn that an instruction has changed or which instructions must remain available.”
Quentin responds, “I changed the opening, but my follow-up still jumped to a solution. Next time I will ask how they recognize the current version and what they need to do if they cannot confirm it.” No offline feature was built or tested; this remains a rehearsal about questioning.
| Observation field | Rehearsal one | Rehearsal two | Next practice decision |
|---|---|---|---|
| Outcome and constraint summarized | No summary before the first solution | Both repeated in the opening | Retain the concise summary |
| Requester asked to confirm understanding | Not heard before the solution | Explicit question; Mabli confirmed | Repeat this check with a new prompt |
| Follow-up question opens the problem | Later question about which recordings was useful | Cached-copy question narrowed toward a proposed answer | Ask about current-version recognition before suggesting an approach |
| Technical correctness | Not evaluated | Not evaluated | Seek domain review separately if this becomes real work |
| General skill judgment | Not assessed | Not assessed | No overall rating or claim of mastery |
The completed record contains a specific change and a remaining gap. These are authored examples, not observed improvements in a real person. Even in a real practice session, different prompts, familiarity and coaching would limit what two attempts could establish about durable skill or causality. A better second opening would not isolate which part of the coaching caused the change.

Make the debrief a conversation about the evidence
Give your own brief account first, then listen for what the observer actually noticed. Do not spend the entire debrief defending your intention. If the evidence is surprising, ask what phrase, action or point in the conversation produced that impression. If the observer missed part of the exercise, record that limit.
You can disagree with a suggested solution while accepting a useful observation. Quentin can accept that he proposed a tool early without accepting that he must never suggest tools. The narrower question is whether his timing helped clarify this particular request. A preferred communication style does not establish a personality trait. If an impression matters, ask what behavior produced it and what alternative would serve this particular task.
Ask what to retain as well as what to change. Otherwise, each practice attempt can become an effort to remove everything distinctive about your approach. In the example, Quentin retains his concise summary and question about relevant material while working on the leading follow-up.
If the feedback stays broad, narrow the next request rather than soliciting more ratings from more people. “What did you hear before my first solution?” is easier to answer than “Do other people think I am collaborative?” Broadening the audience also creates more demands on colleagues and may introduce context they did not observe.
Use the next attempt to test usefulness, not prove yourself
MIT's communication guidance recommends finding explicit practice opportunities and asking a trusted colleague for feedback. Our two-prompt record makes that idea concrete while keeping its limits visible. The sources do not establish an ideal rehearsal length or a universal number of attempts. MIT communication guidance.
Choose one next action, a suitable opportunity and the evidence you will request. Keep the relevant prompt, observer note and your chosen adjustment where they can be reviewed appropriately. Do not turn a colleague's practice comments into an endorsement, a promotion assessment or a quotation for wider circulation without discussing that use.
In the fictional plan, Quentin and Ari end after the agreed 20 minutes. A third rehearsal is not booked automatically. Quentin will ask separately about availability and bring a new prompt focused on the follow-up question. Until Ari agrees, there is no third observation commitment. The useful result of this cycle is a clearer next practice target, not a declaration that the skill is finished.
For your next request, replace the general rating with one observable behavior, an example you want captured and a realistic debrief. Decide what you will try afterward, including what would remain uncertain. More practical skill-development guides are available from LandOffer.ai.
Sources and Further Reading
- UCSF Medical Education: Ask-Tell-Ask Feedback Tips, content credited to Sandrijn van Schaik for UCSF CFE, 2024; checked October 27, 2026. General principles paraphrased, not the clinical table or sample phrases; original workplace cases are not clinical instruction.
- MIT Human Resources: Ongoing Coaching and Feedback, no exact publication date displayed; checked October 27, 2026. Focused requests, specific observations and next steps.
- MIT Human Resources: The Basics of Communicating with Others, no exact publication date displayed; checked October 27, 2026. Explicit practice opportunities and feedback from a trusted colleague.


