Published in


Run team retrospectives to set a continuous improvement workflow

1. Explain to your team the rules for a safe space

  • Every opinion is valid
  • It’s not personal. Focus on facts, not blaming someone.
  • Open-minded listening to detect opportunities

2. Choose the questions template for a better perspective

  • Quick retrospectives define the team’s key focuses of attention
  • Mad, Sad, Glad format to understand your team’s emotional health and consider changes
  • Start, Stop, Continue template to focus the team on new habits by defining what to do or don’t
  • Sailboat framework helps to define the vision for the team and anticipate problems ahead
  • The 4 L’s look at the current situation from a factual perspective

3. Schedule action items with owners and follow-up dates

They will help as calendar remainders and keep track on people and tasks progress.

 by the author.




Short-form stories about productivity, strategy and communication skills.

Recommended from Medium

Make Your CV Reader Get Excited

When The Work Isn’t Enough

What Getting Laid Off Taught Me About My Own Jobs to be Done

Top questions for your job interview. Part II

10 Examples of Fresher Profile Summaries

Calendar software companies: for all our sakes, please make this one change

Become Inspired- Increasing Volunteer Engagement in your Nonprofit

The Resume Snowball Effect

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
J. Antonio Avalos

J. Antonio Avalos

Product Manager & Certified UX Architect. I write about productivity, strategy and communication skills for creatives | jantonioavalos.com

More from Medium

The PMwheel in Action: Dynamic Updates from Lisa Mo Wagner and Jason Knight

Learning Log

A notebook with a pen laying over the page

How Product and Sprint Backlogs Drive Working Functionality Early On

agile vs waterfall | Active Bridge

From Architecture To Product — A short story