YWT reflection
Reflect on what you did, what you learned, and what you will do next, using a specific experience.
YWT is a reflection approach developed by JMAC: Y means what you did, W what you learned or realized, and T what you will do next. Use it after a concrete experience to develop your own learning and a practical next action. YWT is a registered trademark of JMAC.
A completed activity, what actually happened, relevant feedback, your interpretation, and the next opportunity to act on the learning.
An editable three-step reflection connecting actual action, a learning point with its basis, and a proposed next action and check.
On this page
How to use it
- Choose one completed experience. In Y, describe your actual actions and what happened, including useful timing or feedback.
- In W, explain what you learned from those actions. Link the insight to observations and identify what still needs confirmation.
- In T, choose a concrete next action that uses the learning. Say when you could try it and what you will observe.
- After the next experience, compare what happened with your expectation. Update the learning rather than declaring the change successful in advance.
Keep its limits in mind
YWT supports reflection and self-directed learning. It is not a performance rating or a way to blame someone. A personal insight is an interpretation, not proof of another person's priorities or the cause of an outcome. Test a proposed next action before claiming an effect.
Learn from a customer demonstration
Fictional example: a new Yunqiao colleague gave a 30-minute studio-product demonstration. The first 15 minutes covered internal task management; the customer asked three times about external review. The original reflection was only “be more familiar next time.”
On a small screen, scroll across the diagram to read it.
Observation and interpretation: Thirty minutes, the first 15 minutes, and three questions describe the completed demo. Repeated questions support a learning hypothesis; they do not prove the customer's priority or that the presentation order caused confusion.
Learning becomes action: “Be more familiar” does not identify a change. Asking about the current review process before a project-based demo gives the colleague a concrete next behavior. No later demo or improved result is supplied.
Next step: Try the new opening at the next demonstration, ask the customer to confirm the workflow and priorities, and reflect on the actual response.
Three reasons to pause before writing a lesson
Choose one experience you can describe concretely. Separate what you did from what you now understand and what you intend to try next. A useful reflection can be modest: a question noticed during a demonstration may be enough to change the next opening without claiming that the whole approach was wrong.
Pause when Y contains only praise or blame instead of actions. Pause when W describes another person’s priorities as if you could read their mind. Pause when T is only “do better” or depends on someone else agreeing to a change. Return to the record, label your interpretation and identify a next behavior within your influence.
YWT is for learning, not a compulsory confession or a performance grade. If a reflection is shared with a supervisor, agree the purpose and what detail is appropriate to share. A colleague’s different interpretation can remain alongside yours; agreement is not required to make every personal insight identical.
Choose reflection, team review or a coaching conversation
Keep JMAC’s YWT name and attribution distinct from this worksheet’s presentation. Select the structure that fits who is reflecting and what evidence is available, rather than turning every review into a three-box form.
| Method | Material | Output |
|---|---|---|
| YWT | A concrete personal experience | Action, learning and a proposed next behavior |
| KPT | A bounded team period with attributed observations | Keep, Problem and Try items |
| PDCA | An agreed trial and comparable observations | A check and proposed adaptation |
| GROW | A person’s goal, reality, options and own choice | A conversation and a commitment to confirm |
Worked case: change the reflection without inventing a customer priority
This continues the fictional Yunqiao demonstration. A new colleague presented for thirty minutes, spending the first fifteen on internal task management before showing review. The customer asked about external review three times. These are the complete quantitative details supplied; there is no transcript, timing of each question, comprehension test or later purchase result.
The original reflection, “be more familiar next time,” does not identify what to change. The first fifteen minutes were half of the demonstration, but that arithmetic does not establish an ideal speaking allocation. Three questions could reflect importance, confusion or a different context. The speaker’s learning should remain a hypothesis about this customer until the customer clarifies it.
The table rewrites the same material into a usable reflection. Y preserves observable behavior; W owns the interpretation; T proposes asking about the existing review process before showing one project. It does not assert that a later demonstration has occurred or that fewer questions would automatically mean better understanding.
| Part | Record or draft | What remains unresolved |
|---|---|---|
| Y: did | 30-minute menu-led demo; first15 minutes internal tasks; three review questions | Exact question wording and customer context |
| W: learned | External review may matter more than my menu order suggested | Customer’s actual priority and reason for asking |
| T: next | Ask about current review work, then show one customer project | Customer agreement, next-demo response and effect |
Review a new experience without rewriting the old one
The conclusion is a specific change to the opening, not a diagnosis of the customer or the speaker. At the next demonstration, ask how review currently works, what the participant wants to decide and whether a project example fits. Let the answer alter the plan instead of using the question as a scripted route back to your preferred feature.
Afterwards, record what you actually asked, what the customer said, which workflow was demonstrated and where questions arose. Ask the customer to explain the core workflow in their own terms. Questions can reveal productive engagement, so their number alone is an inadequate success criterion. A quiet room could also mean uncertainty or lack of opportunity to speak.
Append a new YWT entry with its own context, keeping the original thirty-minute record intact. Compare your intended behavior with what you did, then revise the learning if the response contradicts it. If external review was not the main need, retain that correction rather than forcing the original insight to be right. No second demonstration or improvement is supplied in this case; T remains a proposed action until performed.
Check your work
- Is Y about something actually done rather than a future plan?
- Does W explain a specific learning point and the observations behind it?
- Are facts, personal interpretations, and remaining questions distinguishable?
- Does T change an observable behavior and include a check?
- Is the reflection useful to the person learning, without becoming a score or a blame exercise?
Framework references
References explain the framework and its scope; they do not validate the fictional example's results.
Put the framework to work
Copy the outline and add your question, evidence, and open questions.
Read a practical guide →Practice with an example
Choose a preparation route for progress, a resource or decision request, or a period review. Use one service case to inspect openings, review checks and focused guides, and keep a preparation note.
Prepare a work update: start with the purpose →