Monthly Archives: June 2014

Do’s and don’ts of managing autonomous teams (or Super7’s) – part II

Managing autonomous teams, or Super7 teams, requires a different management style than managing regular teams. Here’s part two of the key do’s and don’ts from my practice as a Lean Super7 consultant. When your department introduces Super7 Operations, or other forms of autonomous teams, this may help you to adapt to the new situation you’ll face as a manager.

This week: protecting the boundaries of the team – with more than one different meaning of the word boundaries.

Do: actively manage the boundary conditions, keep optimizing

A manager can improve on performance by setting and adjusting the boundaries. As a manager, you are responsible for how much resources can be used to finish the task. You set the boundaries, for instance on how much flex-hours can be used this month. But don’t get complacent if everything keeps running smooth: too much green lights is also bad. Green lights tell you that everything is perfect, while there is always room for improvement.

Don’t: overload the system, prevent overburden (or in Japanese Lean-speak: Muri)

In many classical operations departments, managers used rigid controls, like hourly standardized work packages. These confine creativity and hinder team work, but they protect the employees also from over-burden. A Super7, or any autonomous team, won’t have this protective cage. Keeping the workload manageable is your responsibility as a manager. A team with performance that is up to par (i.e. 100% productivity in productive time and less than 20% unavailability) should be able to get the work done within the time they have. If they can’t finish on time day after day, you may have under-capacity. You as a manager should protect your team from overburden.

Do: Offer help by adding flex capacity from within the boundaries of Super7, rather than by adding extracting people from other Super7’s.

A recent study into Super7-effectiveness show that help by asking a team member to come back from home is better that help by asking a team member of another team to step in. Help from within their own team is appreciated more, and increases the team bond. With flexible (min/max) contracts, it is possible to increase available capacity without adding people to the group. An unexpected study result it may be, but it appears that a strong independent Super7 team is better than two Super7’s that work closely together.

 

Hope you enjoyed this part II – part III will follow shorty.
Menno R. van Dijk.

Do’s and don’ts of managing autonomous teams (or Super7’s)

Managing autonomous teams, or Super7 teams, requires a different management style than managing regular teams. From my practice as a Lean Super7 consultant, I deducted several key do’s and don’ts. When your department introduces Super7 Operations, or other forms of autonomous teams, this may help you to adapt to the new situation you’ll face as a manager.

In the following weeks, I’ll share them with you on this site (www.cooperationalexcellence.nl). This week, I give you the first two sets.

Do: Let go, let the team make their own mistakes

Sometimes, the team manager sees problems that the team hasn’t recognized yet. A pro-active team manager might want to go and fix it directly. Fix it for the team, to help them along. However, studies show that teams that are allowed to make their own mistakes are more effective and more successful. You as a manager can warn the team, but the team must be left free to fix it or respond to it.

Don’t: Leave the team alone.

A team manager can let go too much. An autonomous team needs management support. They may not need detailed steering, but they do need coaching, facilitating and help in solving problems beyond their own circle of influence.

Do: Offer help when the team asks for it – ask questions later.

An autonomous team is capable to deliver results. Even more than the sum of what each individual could deliver. But there is a limit. When the team says they can’t do it, the team manager should help. What he can do to help depends on the specifics, but could include: add capacity, move resources from one team to another or approve lower output for that day.

Don’t: Always offer help when the team asks for it, without evaluating afterwards.

For example: a team indicates that they can’t meet today’s target, and the team manager accepts that some of the work is shoved foreword to the next day. The manager is right to offer help, but he should evaluate the average productivity of that day. Should it be less than normal, he/she should evaluate this with the team. And, the next time he can demand that the team steps to at least normal pace when they ask for help.

I will share more do’s and don’t in the next couple of weeks. In the mean time: keep experimenting!

Menno R. van Dijk.