Engineering Your Team OS
Engineering Your Team OS is a team-development workshop from the Hyper Island toolbox that treats the way a team works together as an operating system to be upgraded in small iterations. The team writes positive, aspirational statements about how it wants to work across six areas, agrees them by consent and then practises one statement per week. It is designed as the follow-up to Hyper Island's Team Self-Assessment.
Facilitation script
- 1
Frame the operating-system idea and review the self-assessment results, or run individual reflection on the six areas.
15 min - 2
Explain the round format and consent: build on a proposal, or object and offer an alternative.
10 min - 3
Work through the areas one at a time, collecting and agreeing statements. Post each agreed statement.
45 min - 4
Read the full list of agreed statements back to the team.
5 min - 5
Choose one statement for the coming week, collect spoken commitments and schedule the review.
15 min - 6
Follow-up at the next team meeting, outside the workshop itself: review the week, refine the statement and pick the next one.
10 min
Tips
Push for statements that describe observable behaviour, such as who posts decisions where and by when; a statement like 'we communicate openly' cannot be practised for a week.
Resist the wish to adopt the whole list at once, because the method depends on one change at a time.
Put the weekly review in the calendar before people leave, since without it the wall of statements is forgotten within a fortnight.
Common pitfalls
Statements stay at the level of values ('we trust each other'), so nobody can tell after a week whether the team did it
Trying to adopt all agreed statements at once, which means none is practised deliberately and the team concludes the workshop changed nothing
Treating consent as consensus and debating wording until everyone loves it, which uses the session up on two statements
No scheduled review, so the first statement is never examined and the iteration the method is built on never starts
The manager proposes most statements and the team consents out of politeness, producing rules nobody owns
Variations
Large groups can split into sub-groups by area, draft statements in parallel and bring them to plenary for the consent round. Online, use a shared document with one section per area and run the rounds by calling on people in a fixed order. A team short on time can cover two or three areas in a first session and return to the others later. The six areas are also the structure of the Team Self-Assessment, so the two workshops can be run back to back as a half day.
Where it fits
When to use it
A team has completed a self-assessment and needs to turn the findings into changed behaviour
A team is taking on more self-management and has to decide for itself how decisions, information and accountability work
Earlier team agreements were written once and never looked at again, and you want a format with a built-in practice loop
A team has regular meetings in which a weekly review of one statement can live
Collaboration problems are spread across several areas and nobody knows where to start
When not to use it
The group meets only once or has no regular meeting rhythm; a one-off Working Agreements session is more honest about what will stick
There is an open conflict between individuals, which should be addressed directly before the team writes aspirational statements over it
The team has no real say over how it works because process is dictated from above; clarify the mandate first
A brand-new team that has not worked together yet; start with a Team Canvas to agree purpose and roles
Related methods
Frequently asked questions
What is Engineering Your Team OS?▾
Engineering Your Team OS is a Hyper Island workshop in which a team deliberately redesigns how it works together. The team formulates aspirational statements across six areas of teamwork, agrees them by consent and then tries out one statement per week. The image of an operating system stands for the habits and rules a team runs on, which can be updated step by step.
What are the six areas of the team operating system?▾
They are team relations and environment, information and decision-making, responsibility and accountability, learning and individual purpose, collective purpose, and profit and productivity. The same six areas structure Hyper Island's Team Self-Assessment.
Do we need to run a Team Self-Assessment first?▾
It helps, because the assessment gives the team a shared view of where it stands in each area. If you have not run one, the workshop replaces it with about 15 minutes of individual reflection on the six areas at the start.
How is this different from Working Agreements?▾
Working Agreements usually produce a short list of ground rules in one sitting. Engineering Your Team OS covers a wider range of topics, from decision-making to purpose, and adds a weekly cycle in which the team practises one statement, reviews it and moves to the next.
What does consent mean in this workshop?▾
Consent means a statement is adopted when nobody has a strong objection, even if not everyone finds it ideal. A person who objects is expected to propose an alternative. This keeps the session moving and suits statements that will be tested for a week and can be changed afterwards.
Plan your next workshop with AI
Workshop Weaver helps you combine methods like Engineering Your Team OS into a complete, timed agenda in minutes.
Try it freeMethod descriptions on Workshop Weaver are original content written by our team, based on established facilitation practices. This method was inspired by work from Hyper Island.