User guide
Understanding your results
Make sense of your team's working habits and turn your results into practical next steps.
Your Team Profile
Your TeamDynamics describe the working habits shared by your team. Everyone on the team shares the same team type.
No team type is better or worse. Your team can use both approaches in each dimension; the result shows which it tends to rely on more naturally.
Explore a sample Team ProfileSample Team Profile
OLAS
The Fast Movers

- Communicating
- Ordered
- Processing
- Logical
- Deciding
- Authoritative
- Executing
- Spontaneous
1. Your team’s type
Each letter represents the team’s behavior in one of the four dimensions shown below. Together they describe this team’s usual pattern, rather than a score or grade.
The four dimensions
Read each pair as two ways of working. Your team can use both approaches.
Communicating
How does your team share information?
Ordered (O)Information is shared through defined processes and forums.
- For important discussions, you prefer written communication and pre-existing meetings to ad hoc calls and Slack pings.
- Meetings are structured and have agendas. Decisions and action items are written down.
- Critical team knowledge is kept in documentation that is organized and kept up-to-date.
Informal (I)Information is shared organically among team members.
- You tend to ping each other or chat live when needed instead of waiting for a meeting or sending an email or written doc.
- Meeting preparation and follow-up work are lightweight. You don't always write down agendas, decisions, or action items.
- Institutional knowledge and team expertise live in people's heads rather than in written documentation.
Processing
How does your team interpret shared information?
Relational (R)The source of information matters when evaluating it.
- Your team has a habit of socializing its analysis ahead of key meetings and decision points, running it by key people for their input and buy-in. Emotional intelligence is an important ingredient in succeeding.
- Certain individuals on the team (not necessarily the team's leaders!) have a lot of sway over what the team does. You're often told to "check with so-and-so" before making a decision.
- There's a lot of emphasis on the value of expertise, organizational context, and relationship capital. It's better to have the team's respect than it is to always be "right."
Logical (L)Information is evaluated on its own merits, regardless of source.
- The argument that carries the day tends to be the one that is most rigorously researched and supported by the facts.
- Everyone has a chance to inform the group’s thinking, so long as they back it up with the type of analysis the team likes to see.
- There's an emphasis on objectivity and a general skepticism of intuition or "gut feel." Maybe you've even heard your teammates say something to the effect of, "In God we trust. All others must bring data."
Deciding
How does your team arrive at a course of action?
Concordant (C)Decisions are driven by consensus among team members.
- Everyone’s opinion is sought and valued, ensuring a collective agreement is reached before moving forward. You prioritize involving all team members in the decision-making process and having every team member on board with the final decision.
- Deliberation is the norm, and transparency about a decision-making process is key to getting things done.
- You frequently hear about team members "socializing" their decisions, soliciting "input" from others, and looking for "alignment" before proceeding with a decision.
Authoritative (A)Decisions are driven by direction from team leadership.
- Decisions are predominantly made by team leaders or a small group of team members, with relatively little input from the broader group.
- Team leaders provide clear direction and explicit instructions for tasks and projects, with communication generally flowing "from the top."
- Decisions are typically made quickly (sometimes unexpectedly so), without much visibility into the decision-making process.
Executing
How does your team work toward its objectives?
Deliberate (D)Plans are thorough, closely followed, and regularly updated.
- Every project starts with a detailed implementation plan. That plan needs to be approved before action can start.
- You regularly review progress against your implementation plans, diligently pursuing milestones and updating the plan as circumstances evolve.
- When something unexpected happens, your team's first instinct is to go back to the original plan and figure out why it wasn't anticipated.
Spontaneous (S)Lightweight plans favor agility and adaptability.
- You move (nearly!) immediately from the point at which a decision is made to taking action.
- Many projects don't have a detailed plan defined, with the team opting to "figure it out at as we go."
- For those times when a plan does get defined, it's lightweight (and perhaps rarely referenced again).
16 team types
One preference from each of four dimensions combines into a four-letter type. Together, the possible combinations form 16 team types.
Reading a team type · sample OLAS
- Communicating
- OOrdered
- Processing
- LLogical
- Deciding
- AAuthoritative
- Executing
- SSpontaneous
Your CoDynamics
Your CoDynamics compare your own working preferences with your team's habits.
Natural fit
Natural fit means your preferences align with the team's approach. These situations may feel more comfortable.
Potential tension
Potential tension means you prefer a different approach. Recognizing these situations helps you prepare and ask for support.
Reflect on a real situation
Think of a recent situation: what felt comfortable or difficult, and what would help next time?
Use your CoDynamics to decide which working differences you want to discuss with your manager or teammates.
Explore sample CoDynamicsYour CoDynamics
Communicating
Potential tension- Your preference
- Informal
- Your team’s behavior
- Ordered
If you took TeamDynamics Solo
TeamDynamics Solo reflects one person's view of how a team works. It is an estimate from your answers, rather than a combined view from team members.
Explore a sample Solo resultPut your results to work
Set aside 45–90 minutes to discuss your results and agree on practical working norms.

Get oriented
Introduce the four dimensions and how you will use them together.
Explore your results
Compare the results with real team experiences. Invite personal reflections without requiring anyone to discuss their CoDynamics.
Plan next steps
Before the session ends, agree on one change to test in real work. Record the situation it addresses, the behavior you will try, the owner, and the first opportunity to use it. Agree when you will review whether it helped.
If you manage or support a team
Use these patterns to ask what support helps each person do their best work. Discuss specific situations and agree on practical adjustments, rather than assigning people a label.
Explore a sample Manager ReportWhen to revisit your results
Team assessments work best once you have worked together for at least four weeks, with shared experiences to reflect on. Revisit your results about twice a year, or when the team or its context changes.
Open your account