Coaching practices for Getting Results the Agile Way Ags After a Loss
Describe almost anything you are working through and IX Coach finds the practices whose real-world fit is closest. For Getting Results the Agile Way Ags After a Loss, these are the strongest matches in the current practice library.
Does this sound like the set of challenges you might be facing?
- Every week I hit the same walls and learn nothing
- When something goes badly I’ll pick it apart for hours, but when something actually goes great I just enjoy it and move on without a second thought
- I get to the end of a packed day having ticked off a hundred little things and still can’t point to one that actually mattered
- I beat myself up over a call that went badly even though it was reasonable with what I knew, and I pat myself on the back for a reckless one that happened to work
- I lost, so I’ve written the whole thing off as a failure
Practices that may help
- Getting Results the Agile Way (AGS), Made Practical
J.D. Meier’s Agile Results (also called Agile Getting Started or AGS) is a time-management framework built on a simple rule: name three outcomes at the day, week, month, and year level, and focus your effort on completing them. The Monday Vision / Daily Outcomes / Friday Reflection rhythm is a practitioner structure grounded in goal-specificity and reflection research, not a formally studied protocol. - Run a Friday Reflection
Each Friday, review what you accomplished, what you learned, and what you would do differently.
Getting Results the Agile Way (AGS), Made Practical - Apply the AAR to successes, not only setbacks
Reviewing what actually caused a win produces replicable insight; reviewing only failures produces only loss-avoidance.
After-Action Review: The US Army’s Tool for Continuous Learning - Name three outcomes each day
Before the day begins, write three concrete things you will accomplish — not tasks, but results.
Getting Results the Agile Way (AGS), Made Practical - Score decision quality separately from outcome quality
Judge the process you used — not whether it worked — when you review a past decision.
Decision Journaling: Learning to Decide Better Over Time - Review process goal execution separately from outcomes after each performance
Evaluate how well you executed your process goals independently of whether you won or lost.
Process Goals, Made Practical - Separate judgment from analysis in the debrief
The AAR only produces learning when the analysis phase is free of performance judgments.
After-Action Review: The US Army’s Tool for Continuous Learning - Run brief after-action reviews without blame
After any significant outcome — success or failure — ask four questions together as a team.
Psychological Safety in Teams - Debrief against process goals, not just the outcome
After performance, evaluate whether you executed your process goals before evaluating the result.
Process vs. Outcome Goals in Sport and Performance - Shift goal emphasis under adversity
When an outcome goal becomes unachievable mid-competition, shift focus explicitly to process goals.
Process vs. Outcome Goals in Sport and Performance
Related concerns
- Getting Results The Agile Way Ags After A Setback
J.D. Meier’s Agile Results (also called Agile Getting Started or AGS) is a time-management framework built on a simple rule: name three outcomes at the day, week, month, and year level, and focus your effort on completing them. The Monday Vision / Daily Outcomes / Friday Reflection rhythm is a practitioner structure grounded in goal-specificity and reflection research, not a formally studied protocol.
- Process Goals After A Loss
Evaluate how well you executed your process goals independently of whether you won or lost.
Review process goal execution separately from outcomes after each performance
- Review Action Not Outcome
Reviewing what actually caused a win produces replicable insight; reviewing only failures produces only loss-avoidance.
Apply the AAR to successes, not only setbacks
- After Action Review The Us Army S Tool For Continuous Learning At Work
An after-action review (AAR) is a structured debriefing developed by the US Army that asks four questions after any event: What was supposed to happen? What actually happened? What caused the difference? What do we do differently next time? Applied consistently, AARs build a culture of learning from experience rather than simply moving on. The evidence base is primarily observational and practice-based; experimental studies are limited but supportive.
- After Action Review The Us Army S Tool For Continuous Learning During A Big Change
An after-action review (AAR) is a structured debriefing developed by the US Army that asks four questions after any event: What was supposed to happen? What actually happened? What caused the difference? What do we do differently next time? Applied consistently, AARs build a culture of learning from experience rather than simply moving on. The evidence base is primarily observational and practice-based; experimental studies are limited but supportive.
- How To Review Performance Correctly
After performance, evaluate whether you executed your process goals before evaluating the result.
Debrief against process goals, not just the outcome
Describe your situation in your own words to search the complete practice library.