Skip to main content

Team Performance Model - by Drexler and Sibbet

Many of you have all heard of the Tuckman model of team dynamics (Forming, Storming, Norming, Performing).  It was created in 1966 and has become the most popular model for describing team behavior.  Is it time to level up in your mental model of team dynamics?  Are you ready for a richer more functional model?



Introducing the Team Performance Model by Drexler and Sibbet



Orientation - Why am I here?
"Orientation is about understanding the purpose of a team and assessing what it will mean to be a member.  you need to understand the reason the team exist, what will be expected of you and how you will benefit from membership.  In a new team, these are individual concerns, because the group is only potentially a team.  that is why these concerns are illustrated as occurring in your imagination at an intuitive level.  As a team leader it is important to provide time and space for people to answer these internal questions themselves."

Keys to when Orientation challenges are resolved:
 - Team Purpose
 - Team Identity
 - Membership

Blocked teams at stage 1 Orientation may show...
 - Uncertainty
 - disorientation
 - Fear




Trust Building - Who are you?
"Trust is a measure of your willingness to work together with others for something important.  Because team members have to depend on each other to be successful, trust is essential in direct relation to how much cooperation is needed to get the job done.  In the beginning of a new team's live, trust involves some risk and uncertainty about dealing with strangers.  This is why the key question is "Who are you?"  An unstated aspect of this question is wondering, "What will you expect from me?"  For a team to work well, you need to accept that you can depend on team members to work together to accomplish the team's purpose."

Keys to when trust challenges are resolved:
 - Mutual regard
 - forthrightness
 - Reliability

When a team is Blocked at stage 2, members may show...
 - Caution
 - Facade
 - Mustrust

Goal Clarification - What are we doing?
Sometimes teams have precise charters that specify what they are responsible for accomplishing.  More often, they are given a broad mandate and nee to make choices about how they will pursue that mandate and translate it into goals.  "What are we doing?"  is a more specific question than the larger question of purpose asked during Orientation.  During this stage of a new team's life, it will need to do research and develop clear understanding of the job that is required, as well as generate agreements about goals and specific deliverables."

Keys to when goal clarification challenges are resolved:
- Explicit Assumptions
- Clear integrated goals
- Shared vision

Blocked at stage 3, members may show....
- Apathy and skepticism
- Irrelevant competition

Commitment - How will we do it?
"When goals are clear and options are identified, your team is probably eager to act.  Attention moves to the question, "How will we do it?"  this stage occurs at the bottom of the "V" in the TPM, the point of the greatest constraint.  This means committing to a specific course of action, making decisions about resources, and being clear about roles.  These are also the indicators of having addressed the "turn".  Remember that the initial stages of team performance involve a good bit of trial-and-error.  Embracing these questions might require backtracking to goals, investing more in trust development, and revisiting initial purpose before you can fully resolve commitment issues."

Keys to when commitment challenges are resolved
- assigned roles
"As your team turns toward implementation everyone will want to be clear about roles and responsibilities. You may have considered these during stage three planning, but now need to commit to what your function, authority, and responsibilities will be in practice.  Role definitions have to be complete enough to cover all the tasks that must be done to accomplish your team goals while minimizing overlaps and role conflicts.  A big part of your job if you are the team leader is to help match goals to competencies, and help people step into roles that will develop their abilities and improve results for the team."

- allocated resources
"In addition to role clarity, your team must deal with another constraint - how to provide for and deploy its limited resources, including time, money, and so forth.  These hard choices usually involve setting aside some useful tasks because the resources are not available to support them.  Indecision in this area breeds confusion and stalls work.  For virtual teams, decisions about tools and communication platforms are essential at this stage.  Teams may have to negotiate with the larger organization to get the kind of tools and support they need.  This is why the TPM intersects the organization "platform" at this stage."

- decision made
"Finally, a team needs to get clear about how members will handle decision making.  Will authority be shared?  How will you stay in touch with one another?  Who can spend what funds?  In a dynamic work environment where plans can change frequently, decision about course corrections are common.  Thinking through in advance how these will be handled moves the team's focus more productively toward implementation and high performance."

Challenges at stage 4, members may show...
- dependence
- resistance

Implementation - Who does what, when, where?
"Implementation involves scheduling and sequencing work over time.  The key question is "Who does what, when, and where?"  A visible schedule, strategy, and / or process liberates the team to move into action confidently.  Conflicts and confusion arise when there is commitment but no clear way forward."

Keys to when Implementation challenges are resolved:
 - clear processes
 - alignment
 - disciplined execution

Team's blocked at stage 5, member may show...
- Conflict
- Nonalignment
- missed deadlines

High Performance - WOW!
"High performance is a WOW state, as a team masters its processes and begins to experience the ability to change goals as well as achieve them.  You can feel when it happens and observe its effects, buy not necessarily control it.  Teams achieve a flow state when trust is high and people have mastered their roles.  In a state of high performance, boundaries and individual limits soften, everything moves together, and everyone responds as if they are part of the whole.  The indicators of that having happened are spontaneous interaction, synergy, and a team that is surpassing their expectation on results.  WOW symbolizes how high performance teams transcend rational processes by working with all the human faculties - spirt, soul, mind, and body."

keys to when High Performance challenges are resolved:
- spontaneous Interaction
- synergy
- surpassing results

When a team is blocked at stage 6, members may show...
- Overload
- Disharmony

Renewal - Why continue?
"Over time the conditions that initially set your team in motion will change.  High Performances is demanding.  Don't be surprised if people ask, "Why continue?"  this key question reminds us that team performance is an ongoing process, and must be renewed by returning to Stage 1 and reassessing if the work is still needed, worthwhile, and has some personal value and meaning.  Spending time on renewal puts your team back in touch with meaning and purpose and refreshes everyone's commitment to keep going.  It also includes learning from what you have accomplished, and building a repertoire of best practices for the next journey on this or other teams.  If your team's work is completed, Renewal is the time to wrap things up, freeing members to move on to new challenges."

Keys to when renewal challenges are resolved:
- recognition and celebration
- managing change
- staying power

When team's are blocked at stage 7, members may show...
- boredom
- burnout

---

This is just a taste of the awesomeness of Sibbet's book on visualizations and exercises to build great teams.  Want to know more - read the book.  You will learn lots about how team move forward and backward toward performance.  And the exercises to work with teams to help them share their understand of where they are, where they are going and what might set them back are very well explained.

    Reference:  Visual Teams - Graphic tools for commitment, innovation, & high performance by David Sibbet.

So what next:
Now that you've got your team categorized into one of those basic circles of development - let's decide what your team's future is going to be.  There are really only 7 possible stories that can be told about your team.  Which one will you tell?

The Seven Basic Plots (in Literature)

This reminds me of a song - Hair Styles and Attitudes.


See Also:

Tuckman was Wrong - Doc on Dev - CTO2 there is little science backing Tuckman and many experiments that do not confirm the theory.

The Tenth Man Principle how the Israeli PM combats institutional group think to save the nation. - by Patrick Anderson

Jay W. Vogt of Peoplesworth explains the Drexler Sibbet Model of team building and how it can result in a positive outcome. YouTube

Management 3.0 Workbook
7 levels of Delegation exercise


Sibbet discusses the origins of the TPM - SketchTalk

Dunning-Kruger Effect - TED-Ed 
The psychology behind why incompetent people think they're amazing:
Post a Comment

Most Popular on Agile Complexification Inverter

Exercise:: Definition of Ready & Done

Assuming you are on a Scrum/Agile software development team, then one of the first 'working agreements' you have created with your team is a 'Definition of Done' - right?



Oh - you don't have a definition of what aspects a user story that is done will exhibit. Well then, you need to create a list of attributes of a done story. One way to do this would be to Google 'definition of done' ... here let me do that for you: http://tinyurl.com/3br9o6n. Then you could just use someone else's definition - there DONE!

But that would be cheating -- right? It is not the artifact - the list of done criteria, that is important for your team - it is the act of doing it for themselves, it is that shared understanding of having a debate over some of the gray areas that create a true working agreement. If some of the team believes that a story being done means that there can be no bugs found in the code - but some believe that there can be some minor issues - well, …

Elements of an Effective Scrum Task Board

What are the individual elements that make a Scrum task board effective for the team and the leadership of the team?  There are a few basic elements that are quite obvious when you have seen a few good Scrum boards... but there are some other elements that appear to elude even the most servant of leaders of Scrum teams.









In general I'm referring to a physical Scrum board.  Although software applications will replicated may of the elements of a good Scrum board there will be affordances that are not easily replicated.  And software applications offer features not easily implemented in the physical domain also.





Scrum Info Radiator Checklist (PDF) Basic Elements
Board Framework - columns and rows laid out in bold colors (blue tape works well)
Attributes:  space for the total number of stickies that will need to belong in each cell of the matrix;  lines that are not easy eroded, but are also easy to replace;  see Orientation.

Columns (or Rows) - labeled
    Stories
    To Do
    Work In P…

Webinar: Collaboration at Scale: Defining Done, Ready, and NO.

I was invited to participate in a Scrum Alliance Webinar.  Maybe you would like to listen to us in a discussion of techniques to collaborate at scale (remotely and with many people).  The topic is one that I've got some experience in discussions - yet I never seem to get to done...
Collaboration at Scale: Defining Done and Ready and NO for Distributed Teams
With Joel Bancroft-Connors, Agile Organizational Coach; David A. Koontz, Agile Transition Guide; and Luke Hohmann, CEO and Founder of Conteneo, Inc.


14 February 2018 11 a.m. ET (USA).




The Scrum Guide is pretty clear on the criticality of the definition of Done: "When a Product Backlog item or an Increment is described as "Done," everyone must understand what "Done" means. However, the Scrum Guide ALSO says that the definition of Done can "vary significantly per Scrum Team." This leads us to examine when and how the definition of Done should vary, how distributed teams should cr…

A T-Shaped 21st Century Knowledge Worker

Knowledge workers in the 21st Century must have many areas of deep knowledge, while also be capable of collaboration across multiple other domains with dissimilar T-shaped individuals.  This description of a person is a metaphor.  Compare it to the shape of the "I" in the classic saying there is no "I" in Team.


I first read about Scott Ambler's term "Generalizing Specialist" - but it's so hard to remember the proper order of the words... get it backwards and it has an inverted meaning... T-Shaped is easier to remember. 
A generalizing specialist is someone who:
Has one or more technical specialties (e.g. Java programming, Project Management, Database Administration, ...). Has at least a general knowledge of software development. Has at least a general knowledge of the business domain in which they work. Actively seeks to gain new skills in both their existing specialties as well as in other areas, including both technical and domain areas.  General…

A FAILURE to Communicate

I was working with a failing team some time ago.  I use "failing" to describe the outcome of the team - not the people on the team.  Are you OK with that description?



An issue arrose in the stand up - a team member that was to verify the quality of a procedure did so and reported that there were a few records that didn't match expectation in the data set.  Upon inquire the number of records not matching was over 2000.  Most people acknowledged immediately the exaggeration - I could tell by the laughter.  After about 10 minutes of discussing the details of the problem - it appeared the team had a handle on the specific situation.

I stopped the discussion and inquired if they could name the impediment.  One team member did a great job of describing the impediment as a _communication gap_.  Wonderful - I could work with that - the problem had a name and it didn't include anyones Proper Name.

"If the problem has a first name; we are going to have a problem."

I&#…