Your team is a system. It is complex with multiple and interlocking parts. We like to borrow the term Operating System (OS) from the software industry, to denote a complex system that supports people to work (programmes to run) and is improved over time through constant, small iterations.

This workshop is an essential starting point for any team that wants to update its OS and evolve the way it works. Most teams work and grow organically, with little deliberate attention given to designing the working process, exploring interpersonal relations, and challenging traditional notions of hierarchy.

By taking the time to do a self-assessment a team can surface things that are implicit, and make them explicit. Only once they are explicit can a team talk about them and change them.

This workshop uses 6 dimensions to frame the reflection and discussion. Write these on a whiteboard, flipchart paper, or show them on a screen for the team to copy.

• Team Relations & Environment
• Information & Decision-Making
• Responsibility & Accountability
• Learning & Individual Purpose
• Collective Purpose
• Profit & Productivity

Give each team member a sheet of flipchart paper, portrait orientation. Instruct them to draw 5 horizontal lines, splitting it into 6 equal sections and label each section with a dimension.

Now give them 30 minutes to reflect on these dimensions in silence. Individually, they should write down statements that apply to each dimension. These should all complete the sentence:

As a team, we...

Some will likely be positive or celebratory, others will likely be critical or development oriented. Ask members to arrange their statements on the paper, with the most development-oriented on the left and the most celebratory on the right.

On a whiteboard or flipchart draw a large version of the 6 sections that they have been working on. The aim of this step is to bring everyone's statements together to see where the team agrees and disagrees on the 6 dimensions.

One-by-one, invite the team members to share 2-3 post-its from each dimension. They should just read out what they have written. No additional explanation or justification is necessary at this point.

Again, they should put the more development-oriented statements to the left, and the more celebratory statements to the right.

The aim of this step is to narrow down the statements and remove any clear duplications.

Invite someone from the team to cluster the statements in silence. When they feel they are finished, ask the group if anyone feels strongly about changing the clusters. If they do, invite them up to make the changes.

Repeat this until nobody objects to the clustering. It may take a few rounds, but eventually you will arrive at a selection of statements that nobody strongly disagrees with. This is a consent-based group decision.

The aim of this step is to see what statements the group feels strongly about. You're going to do that through dot voting.

Give each team member a sheet of small coloured sticky dots. They should all be the same colour, so you can't tell who voted for which statement.

Ask the team members to look at the clustered statements. They should stick a dot on the statements that they think are important to this team. The things they think should be addressed, changed, or celebrated. There is no limit to the amount of dots they can use.

When everyone is finished voting, step back and look at the board / flipchart. The spread, density, and frequency of the dots will give you an immediate sense of what the team thinks is important.

The aim of this final step is to digitise the insights from the workshop and figure out the next steps!

Ask the group for a volunteer to turn what is on the board / flipchart into a digital image. They should take a picture(s) on their phone, and transfer the information onto a collaborative, editable document. Something like a Google Document.

Now is the time for a group discussion. The team should decide what to do with this information. Here are a few suggestions:

• Formally celebrate the positive statements in some way.
• Schedule 6 discussion sessions over the next few weeks, each one focused on one development-oriented statement from one of the dimensions.
• Present the digital document to another team, or to the whole company at an All Hands meeting or Brown Bag session.
• Run the Engineering Your Team OS workshop next week, to redesign your team's operating system in a highly deliberate manner.