Dornell.izella

29
2011 Program Management Challenge Developing High Performance Teams Presenters: Bobby Watkins NASA Marshall Spaceflight Center Izella M. Dornell U.S. Department of Commerce 1

Transcript of Dornell.izella

Page 1: Dornell.izella

2011 Program Management Challenge

Developing High Performance Teams

Presenters:

Bobby Watkins NASA Marshall Spaceflight Center

Izella M. Dornell U.S. Department of Commerce

1

Page 2: Dornell.izella

Agenda

Overview

Program/Project Problem Resolution

Anatomy of a High Performance Team– The Importance of Teams– Team Building Components– Team Leadership– Team Membership– Obtaining Balance

10 Reasons to Use Teams2

Page 3: Dornell.izella

High Performance TeamsOverview

• Developing strong teams and relationships within the team are major components that enable mission success

• Optimizing team performance should be a high priority for an organization’s leadership

• A team’s functionality can mean the difference between having the appropriate resources made available or landing on a “high risk” cancellation list 3

Page 4: Dornell.izella

1. Identify/SelectProblem

2. Analyzethe Problem

3. GeneratePotentialSolutions

4. Select &Plan Solution

5. Implement the Solution

6. Evaluatethe Solution

Plan

DoCheck

Act

Six Step Problem Solving Process

4

Page 5: Dornell.izella

5

Blue Print Tools

• Team Building–Fostering collaboration through “team

building” is the key component for effective execution of the organization’s mission, programs and projects

–Must realize that people are the foundation for building and nurturing high performing teams

Page 6: Dornell.izella

6

Team Building Components

• Purpose• Structure• Motivation• Dynamics• Communication• Respect for members• Feedback• Closure

Page 7: Dornell.izella

7

High Performance TeamsLeadership

• Effective leaders first gain an understanding of the context of their organization

• Mission• Stakeholders• Constraints• Political environment• Culture

Page 8: Dornell.izella

8

High Performance TeamsLeadership

• Characteristics– Use different leadership styles– Define and focus on goals and objectives– Articulate a strategy for moving forward– Engage employees/team members– Put customers first– Involve key stakeholders– Seize the moment– Communicate, communicate and communicate– Create alignment– Expect the unexpected– Stick with it

Page 9: Dornell.izella
Page 10: Dornell.izella

Who Touches the Process?

• Process Owner• Professional staff who do the work• Technical staff who do the work• IT representative• HR representative• Finance representative• Customers & other stakeholders• Suppliers• Benchmarking partner• Somebody with facilitation skills• Somebody who has done a process improvement

10

Page 11: Dornell.izella

For Team Effectiveness…….

Page 12: Dornell.izella

A Team Facilitator Who:– Consults (Knows when to shut up)– Focuses the Team– Encourages Initiative– Shares Tasks & Leadership– Trains & Develops– Cultivates Honesty– Cultivates Respect– Coordinates Activities– Motivates the Team– Measures, Measures, Measures– Cultivates Creativity– Runs Interference

12

Page 13: Dornell.izella

Team Members Who:• Care• Take Responsibility• Freely Offer Ideas & Talents• Encourage the Ideas & Talents of Others• Focus• Think (till it hurts)• Are Positive• Appreciate & Utilize Diversity• Helps the Leader

13

Page 14: Dornell.izella

Meeting Ground Rules• 1. Respect Each Other• 2. Share Responsibility• 3. Criticize Ideas Not People• 4. Keep An Open Mind• 5. Question & Participate• 6. Attend All Meetings• 7. Listen Constructively & Carefully• 8. Be On Time• 9. Make All Points At Meetings

– (Not In Parking Lot)• 10. Be Candid & Diplomatic

14

Page 15: Dornell.izella

15

High Performance Teams Balanced Results

Processes implemented to maximize program and project

efficiency with the “active cooperation” and “buy-in” from the

TEAM

Page 16: Dornell.izella

16

Obtaining Team Balance

• What do you need to be able to do?

– Create a Blue Print– Know the Environment– Determine the Leadership– Establish organizational goals/mission focus– Build a functional team

• Build relationships• Establish alliances and coalitions• Beware of organizational “land mines” i.e. politics/culture

Page 17: Dornell.izella

Ten Reasons to Use Teams

(Besides getting the boss off the hook on tough

decisions)

Page 18: Dornell.izella

1. Reduces Stress and Politics

• Boss does not have to be all knowing• Vastly increases the data used for decision

making• Process less personal (in good ways)• Personal status and “histories” not part of

the process• More objective

18

Page 19: Dornell.izella

2. Reduces Bureaucracy

• Communication among units immediate• Assignments made and completed outside

of “chain of command”• No need for sequential “clearance” for

permission to take next steps

19

Page 20: Dornell.izella

3. Creates Fun and Energy

• Group commitment to each other pushes things forward

• People bond when on a well defined mission

• Brainstorming, creativity and innovation are invigorating

• Learning is invigorating• A good facilitator will make sure there is

fun

20

Page 21: Dornell.izella

4. Consensus Can Happen

• Solutions moves forward without sabotage – Majority rule causes sabotage– Unilateral decisions cause insurrection– Consensus causes the group to “dig deeper”

21

Page 22: Dornell.izella

5. Makes Your Diversity A Resource

• Produces tangible experience of the advantage of differences

• Infects the organizations culture

22

Page 23: Dornell.izella

6. Creates Continuously Improving Systems

• Systematic approaches used by teams produced systems – Systems have monitoring devises – Systems have means of calibrating to

changing customer requirements– Systems have input, in-process and output

measures– Systems are deployed to standards– Systems can be compared and benchmarked

23

Page 24: Dornell.izella

7. Not Constrained by the Organization Chart

• Include Suppliers• Include Partners• Include Customers• Include the Customer you want

24

Page 25: Dornell.izella

8. Learning Happens

• Transfer of skills, knowledge and point of view

• Innovation results when concepts from unrelated fields meet

• There are development opportunities even in a “flat” organization

• Hidden talents emerge• Personal growth inevitable

25

Page 26: Dornell.izella

9. Puts the “We” in Your Organization

• Builds relationships across silos• Communication channels outlive project• Credit and pride goes far and wide• Supports empowerment• Encourages matrix management

26

Page 27: Dornell.izella

10. Produces Better Solutions That Actually Get Implemented

• All the right egos invested• Every “gift” can be in the room• All bases have been touched• Everyone pulling for success• Everyone adapting for success• Lots of folks get credit for success• No put downs

27

Page 28: Dornell.izella
Page 29: Dornell.izella

Discussion