Pivotal team moment goat2015

Pivotal Team Moments

How to recognize them to influence your team’s journey


Identifying and reframing to influence team's journey

Jesus Mendez

Nieces & Nephews

7 Marriage

13Sports

6

Nationalities

2

18

Years being part of teams

32Teams



Robert Pragai



Why do we love Team Dynamics?





Work in teams





What motivates you to work within a

team?



1. Define a Pivotal Moment

2. Examples of Pivotal Moment

3. Share Similarities

4. Framework

What we want to achieve today!



Pivotal Moment:

“A single or a quick series of unexpected event(s)

that has a major effect that can make or break a

team”

Definition



The team’s journey

Bruce Tuckman Group development theory model

Collaboration level

Low

High

Maturity levelLow High

Robert Pragai

What about these options?

Jesus Mendez

I really like the second one



1. Being the Solo Hero

BackgroundTeam Stage: PerformingTeam Size: 5 Tenure Together: 18 months5 successful customer deliveries




Pivotal Moment: Within 2 hours, 3 major failures, 48 hours before a major customer release.

Immediate Impact:• Team Actions:

“I will fix” instead of “We will fix this together”• Team Sentiments:

Mistrust, Blame, Anxiety, and Fear• Team Stage:

Fell back to Storming




Immediate Outcome:Product was released however sentiments remained.Focus remained on the last 48 hours as opposed to the overall

amazing work to deliver.

Team Visibility Resolution Reflection Outcome

LIMITED “I will fix it” Individually No reflection Team learned blame




NEXT STEPS:Priority: Rebuild Trust and Confidence within Team



2. Demonstrating Humility

Background:• Team Stage: Norming • Team Size: 3 • Tenure Together: 10 months

key player left the team the week before

Fear




Pivotal Moment: Database drop, 8 hours we couldn’t offer services to our clients, little knowledge about the broken system among team members, lost money and reputation

Impact on the team:• Team Stage: – The team took step towards Performing

• Team Sentiments: – Support each other, Collaboration, Accomplishment




Immediate Outcome: System went back to normal, team learned how the complex system

works, stakeholders reassured, we can do it together!

Visibility Resolution Reflection Outcome

FULL“We will fix this

together” Team

- Reflect to learn- Actions taken

- Team learned- non organizational

learning




NEXT STEPS:Priority:

• Ask for external help • Share learning with the organization



Tone

Common Team Sentiments

Fear

Anxiety

Jesus Mendez

anxiety + teams tone + interactions



Pivotal Moment Reference TableLevel Team Visibility Resolution Reflection Outcome

1 LIMITED “I will fix it” Individually

No reflection Team learned blame

2 LIMITED “I will fix it” Individually

Reflect to LearnActions taken Individual learning

3 FULL “We will fix this together” Team

No Reflection Team learned blame

4 FULL “We will fix this together” Team

Reflect to LearnActions Taken

- Team learned + non organizational learning

5 FULL + ORG “We will fix this together” Team

Reflect to Learn + Action taken + Share learnings with the organization

-Team learned + Organization learned



Group DiscussionInstructions:

1. Identify a team’s pivotal moment in the past 6 months.

2. Please answer these two(2) questions:

a. Which stage the team was, based on Tuckman’s model?

b. Which level of Pivotal team’s moment reference table the team was?

3. Share your findings with your neighbor

a. What we have learned?

Let’s spend the next 5 minutes on it

Framework

IndividualConfirmation

Team Confirmation

Team Reflection



Several conversations

People acting weirdHurry up attitude

1. Individual Confirmation

Potential Triggers

Something is Off



1. Individual Confirmation

Observe

Sense It

Be Curious

Trust but Verify

Investigate



2. Team Confirmation

Ask for H

elp

AcceptYes

No Drop it

Let’sAddress

itAccept



2. Team Confirmation

Address

Share and explain



3. Team Reflection

Celebrate learning



3. Team Reflection

1. Let’s share our appreciation to the team2. What went good?3. What have we learned? Focus on Behaviors/Feelings4. What could be improved?5. How do we incorporate learning into our development process?6. What do we do to celebrate learning?



What we have concluded?



“No matter the product, the reason, or purpose of your team, there comes a point in each teams journey which will either bring them together, or tear them apart”.

Agile Urban Proverb

Conclusion

Guess What?

https://www.youtube.com/watch?v=nK1jtVhimPA



Questions?Comments?Suggestions?



Join the Movement

Twitter: @chuzzeteEmail: [email protected]

Techniques for transforming teams into high-performing sustainable Agile teams.www.jesusmendez.ca

Twitter: @RobertPragaiEmail: [email protected]

http://www.jesusmendez.ca/



Technology

Pivotal team moment goat2015