Career Catalogue
Switch tool

Team practice

Team experiment

Turn one retro or health observation into a small change. Agree what you will observe, then return to decide whether to keep, change or stop it.

What you leave with One agreed plan, a review date and a record of what you learned.

Review your plan and take a copy ↓

Agree on one experiment

Start with a shared observation, not a score about a person. Every field is required. Drafts save on this device as you type.

Someone who helps the experiment happen and brings the observation back. An initial or role is enough.

Defaults to a fortnight from today. Put the review in your team's calendar; this page shows when it is due when you return.

Your draft

A copy you can take into the conversation. Saving the agreed plan starts the review cycle.

Observation
Still to discuss
Change to try
Still to discuss
Volunteer owner
Still to discuss
Success signal
Still to discuss
Review date
Not scheduled
View Markdown 

        

      

    

  


  

    

      A completed example: reviews piling up
      
Observation: Small changes wait until the last days of a sprint for review, leaving the team rushing to finish.

      
Change: For one fortnight, volunteer reviewers check the queue after the daily scrum and take the oldest ready change first.

      
Owner: A volunteer from the team rotates the reviewer reminder.

      
Success signal: Compare how long changes wait for review. Ask at the next retro whether people felt less rushed. Do not measure individual reviewer output.

      
Review after one fortnight: Waiting time improved, but the daily reminder interrupted people during deep work.

      
Decision — Change: Keep checking the queue, use an asynchronous reminder, and review again in a fortnight.

    

    

      
      
    

  


  

    
Recent learning

    
The last 10 reviews and closures stay on this device. Download anything you want to keep longer.

    
No reviews yet. Your first review will keep its plan and what you learned here.

    

  


  

    
The writing behind the practice

    
Closing the Feedback Loop · The Importance of Iterative Development · Retro · Team health

  

  
Runs in your browser. Plans and learning stay in local storage on this device. No reminders are sent. Keep shared observations here; leave private feedback and personal health votes out.