Create a self-formed team with Post-Its

Back in the days of Microsoft, a crazy idea was used to create self-formed teams, allowing every team member to choose what they wanted to work on. Read Self-forming Teams at Scale, by Brian Harry 2015, for the complete story.

LighthouseAllowing teams to “self-form” empowers stakeholders to choose their purpose and strengthens the core pillars of an effective team: trust, commitment, and accountability.


Before you start this exercise, ensure that you have the following prepared:

  • Compelling direction – VISION
  • The WHAT and WHY/team
  • Business domain expert (Product Owners)/team
  • Expert coaches (Scrum Masters)/team
  • Supportive engineering process


  • Set the scene by presenting the compelling direction.
  • Introduce the enabling structure, engineering process, known constraints, and proposed teams.
  • Allow the product owners and scrum masters to present their team and convince everyone why their team is the best thing since sliced cheese with holes.

It is a sales job!

  • Optionally give everyone a cool off period to think and have discussions with peers and leadership.


  • Agree on a common standard to depict first, second, and third choice. For example, colours, dots, or numbers.
  • Give everyone three sticky notes.
  • Ensure that all teams are collocated, so that everyone can interact and assess who they may be working with.
  • Allow everyone time to place their three sticky notes next to the teams they want to join.


  • After the sticky note session, the leadership, product owners, and scrum masters discuss forming their teams.
  • Everyone’s personal preference is important!
  • Ensure there is transparency on the reasoning behind the final team formations.


  • Leadership can do a bit of marketing and selling ahead of time to nudge key resources in the right direction.
  • Not everyone can get their first choice, which is why we ask users to pick a second and third.

Allow everyone to “make it fun”.

Teams need to be inspired!

Share this post

Download our free white paper on Technical Debt and Business Agility.

Fill out the form below, and we will send you a white paper along with a drawing for a free drawing for our DevOps book!

Ready to level up your career?

Recent Posts

Add to Waitlist

If a course has an ‘add to waitlist’ button then it is likely booked up. Spots often become available so please fill out the form below. We will be in touch within 24hrs


Born 1965, San Antonio, Texas and lives in Dallas, Tx.
Mr. James, Ronald, Maverick holds a Bachelor of Science in Psychology at The University of Texas, San Antonio.

Mr. Maverick or JR as many call him is a “slick” but warm and friendly character in our upcoming book on the DevOps Mindset. Mr. Maverick cares about his IT team very much and could charm the socks off a Texas Longhorn. JR is liked by many in his organization; however, he is not as well trusted by the Overlords as he used to be. Mr. Maverick has a group of loyal staff, including Mr. Barker a bit of an opposite to JR. Of course, Mr. Barker would never call him JR; he would only call him Mr. Maverick because well, Mr. Maverick is his boss. Mr. Maverick has held many IT positions in the past, including starting as a Sales Professional for HP and IBM mini and mainframe computers. Over the years he has risen through the ranks to hold this senior position by delivering using high-paid consultants and Big name firms. He also received his promotion from outsourcing to a foreign country where he was able to reduce his IT spend significantly. Recently he has discovered (actually this was made painfully aware to him by the Overlords) that both the Offshore roadmap and use of external consultants was not giving him the value and velocity for his IT department, and he was probably paying more than he bargained for

So, after hearing a talk at a DevOps event by the Agents of Chaos, JR decided to enlist them to help with their digital transformation roadmap and help improve the value, focus and velocity of his department. However, MR. Maverick has a few ideas about agile and DevOps, something he has heard about for a while and read in various CIO magazines; he thinks of these as Marketing terms and something that can be bought. While Mr. Maverick has held on for many years to traditional IT ways of working he has come to the end of his tenure if he doesn’t do something fast and get DevOps working quickly as he has promised to the Overlords providing him with a little more rope to get the transformation completed more quickly as they view his IT department ageing, procrastinators who are not able to keep up with business demands. JR says in his mind, “I will get it done, they don’t call me Maverick for nothing!“