Tag Archives: Teams

Super7 teams benefit from Lean Operational Management

Super7 teams benefit from having the standard processing times and performance dashboards in place. These elements from Operational Management help a Super7 team in steering itself. When these basic elements from Operational Management are missing, implementation projects tend to take more time. It takes longer before the Super7 teams become autonomous.

Super7 Operations claims to be the next step for Lean in financial services. But how much does it owe to the previous Lean wave in financial Services? Which elements from Lean Operational Management are essential for the success of Super7 Operations?

The Next Step for Lean builds on the previous step

The way I see it, Super7 Operations is the logical next step for Lean in financial services. The first lean waves in financial services were often aimed at introducing standardized work,  standard processing times, and making performance visible in performance dashboards.

Standard processing times make the work plannable. In Lean Operational Management, managers use them to plan the work for their teams. And afterwards, actual production is compared with planned production to calculate performance*. The manager then retains control through performance dashboards.

As I explain in my book, Super7 teams are steered on output. And, in Super7 Operations, the teams get the freedom and responsibility to plan their own work. However, both output steering and planning your own work becomes much easier when standard working times and dashboards are in place.

In Super7 Operations, the customer determines what needs to be done: the workload is based on the actual demand from that day. The manager sets the boundary conditions: that all requests are processed the same day (Today In, Today Out, or TITO). Work is often planned on forecast. But, to make planning decisions, the team needs to be able to match the forecasted workload to their planned capacity. And this can only be done when the forecasted number of customer requests can be translated into hours of work with the help of standard processing times.

Dashboards are equally important in Super7 Operations, but primarily for the teams themselves. They need to be able to see if all their Continuous Improvement efforts are paying off. And dashboards can be used to constantly raise the bar, both by the team itself and by the manager. Too many green lights become a red light, as the saying goes. This means that when the daily targets are met every day, this should lead to a more challenging target. More service in the same time for instance, or doing the same work with less capacity.

When standard processing times and performance dashboards, two basic elements from Lean Operational Management, are missing, implementation projects tend to take more time. It takes longer before the Super7 teams can make the decisions that make them truly autonomous.

Menno R. van Dijk

*Performance in Financial Services is often expressed in Total Team Effectiveness, a derivative of Overall Equipment Effectiveness (OEE) which is the standard within manufacturing.

 

Creating the right culture for Super7 Operations

How to create the right culture for Super7 teams?

Creativity and autonomy florishes within a culture of trust, support, stretch and discipline. Traditional companies often rely on constraints, compliance, control and binding through contracts. This is explained excellenty by Prof. Sumantra Ghosha.

Recently, I was given a tip to watch a short clip form Prof. Sumantra Ghoshal, called “the smell of the place”. To my opinion, this clip is very relevant for autonomous teams, scrum, agile and Super7 Opertions. Below, you’ll find his brilliant speech from the World Economic Forum about corporate environments and the faults of management in creating a positive work place.

The smell in which creativity and autonomy – and therefore Super7 Operations – will florish

  • Stretch (environment in which everybody wants to take that extra step)
  • Discipline (self-discipline, be on time, agree to disagree and committ to decisions)
  • Support (managers change from exercisers of control to coaching, guidance, support)
  • Trust (act on the presumption that people act in the best intrest of their company)

 In contrast, the smell traditional companies often create:

  • Constraints in stead of stretch,
  • Compliance in stead of dicipline,
  • Control in stead of support,
  • Contracts in stead of trust.

Important lesson from this video is that the smell can be changed. You can convert the smell of the place from “downtown Calcutta in the summer” to “a forest in spring”. It has been done before. And, you can use the smell metaphor in explaining and visualizing this change.

One department I recently visited had a brown paper on their Scrum-wall, on which all teammembers rate the smell they are smelling on a scale from 1 (Calcutta) to 10 (Forest). This way, they can monitor the culture, and address issues that cause ‘bad smells’.

Menno R. van Dijk.

Making Agile Squads work

To make Agile Squads work, you can make specialists multi-skilled to enable the Squad to prioritize across all disciplines within their squad – an important lesson from our Super7 experience.

Many companies are trying to emulate the success that Spotify has had with their Agile engineering culture (see YouTube: part1, part2). Traditional companies are now considering reorganizing into Squads, Tribes and Chapters. Let’s recap first:

A Squad is a small, multi-disciplinary team, much like a Super7 team, but more focused on developing and managing a product or product feature rather than processing customer requests.

A Tribe is more-or-less what we used to call a department, but again, focused on a related group of products or services.

A chapter is the ‘matrix-layer’, a group of similar specialism from different tribes.

As Spotify explains in their second video, strong growth has made the Squad & Tribe organization more complex. So how do you get this type of organization to work?

My observation is that the matrix of Chapters running crisscross through Tribes creates 2 potential problems.

1. Less autonomous problem solving power for the Squads because different specialists can’t help each other.

– Squad members are all specialists in their own field
– Each specialist will have their own list of priorities
– When one specialist’s highest priority is really critical, the risk is that his/her squad members can’t help this specialist, simply because they don’t know enough of the subject.
– Instead, they can only focus on their own priorities, sub optimizing the squad results

2. Requirement of more management because of complexity

– In the situation as described above, the specialist in need of help will turn to his/her chapter-members.
– This requires cross-squad or even cross-tribe prioritizing
– And this will require a lot of talk, compromising, decision making.
– In short, this will increase the need of management.

For these 2 problems, our experience with Super7 could hold the solution:

Use multi-skilled specialists, and enable the Squad to prioritize across all disciplines within their squad. A graduation study has shown that Super7’s that can rely on help from within their own Super7 are more effective and have better team-spirit than teams that need to lend a hand to other Super7’s on a regular basis. This emphasizes the importance of multi-skilled specialists.

How would this work for Squads?

  • Super7 shows us that specialists need to be able to help at least 2 other members of their Super7.
  • Translated to Squads: every squad-member needs to be a specialist in at least 2, but preferably 3 specialisms that are needed within the squad.

This will demand a lot of the people involved. They need to be trained. But as Toyota puts it: “we build people before we build cars”.

Menno R. van Dijk.

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

Managing autonomous teams, or Super7 teams, requires a different management style than managing regular teams. Here’s the last part the key do’s and don’ts from my practice as a Lean Super7 consultant. And, in my opinion, this one is the most important.

Perhaps most importantly, Do: Use your own strengths and talents.
Don’t: Put all your efforts on improving your weaknesses.

The best advice I can give any manager is: be the best person that you can be. Use your talents as much as you can. If you only focus on improving your weaknesses, you won’t be able to perform at your best. You will be most effective when you do the things you like to do and use your own unique talents while doing them. When faced with a transition from a more traditional organization towards autonomous teams or Super7’s, you might at first only see those elements that are difficult for you, that you don’t like and where you can’t use your talents. But if you give it a chance, if you start experimenting, you might find that there is a way to use your strengths in the new way of working. In my experience, most managers will find a way that fits them. Of course, managing autonomous teams or Super7’s will not be the perfect job for everybody. It is important for your happiness and for your chances to success that you keep searching for an environment where you can do the things you like and use your talents at the same time. And in some cases, this may mean a change of career. But, there isn’t just one way or one perfect style of managing autonomous teams. Take a chance, experiment, and you might just find the style that works for you and for your teams.

Menno R. van Dijk.

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

Managing autonomous teams, or Super7 teams, requires a different management style than managing regular teams. Here’s part four of the key do’s and don’ts from my practice as a Lean Super7 consultant. This week, we’ll look into the competences that an output-manager needs. 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.
Do: Adapt to the new situation and experiment with the required competences
Don’t: Expect this change to be easy
Other skills and behaviors are asked from a manager when an organization makes the transition from a classical, input steered organization towards autonomous teams or Super7’s.
Typical skills are:
• Facilitating style, focused on output
• Creativity in developing improvement experiments together with the team
• Drive to improve continuously
• Group focus instead of focus on the individuals
• Flexibility, managers should be able to manage each other’s teams
• Working fact-based, using facts and figures for planning and forecasting
• Analytical; being able to interpret data to challenge the teams and to identify improvement opportunities
Typical behaviors are:
• Proactive in finding improvement opportunities and in implementing improvements
• Focused on customers and customer processes
• Inspiring the team to be customer focused and innovative
• Helping teams and team members in their journey towards autonomy

Keep an eye out for the last post in this series: the most important tip will follow shortly

 

Menno R. van Dijk

 

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

Managing autonomous teams, or Super7 teams, requires a different management style than managing regular teams. Here’s part three of the key do’s and don’ts from my practice as a Lean Super7 consultant. This week, we’ll discuss the do’s and don’ts of management metrics and dashboards for autonomous teams. 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.

Do: Use quantitative metrics on output performance

Don’t: regard output as a Boolean function (i.e. true or false, the output has been delivered or the output has not been delivered)

Many managers in Financial Services Operations are used to manage by spreadsheet. When switching to output steering, they might tend to overcompensate. Instead of managing productivity, Fisrt-Time-Right and throughput time, they just evaluate whether the output has been delivered or not. The outcome is black or white, good or bad: either the team made it, or they didn’t. Managers should use quantitative metrics to measure the output. When the target output hasn’t been met, the team should be able to see by exactly how much the target was missed. This allows learning and evaluation of improvement experiments.

Do: Use the well-known Lean steering metrics to evaluate performance and to give the team insight in where they can improve. (.e.g. Efficiency (productivity, availability), First-Time-Right percentage, throughput time)

Don’t: Use these Lean steering metrics to manage the team on a daily basis.

As said, many managers in Financial Services Operations are used to manage by spreadsheet. These spreadsheets may still be of value for autonomous teams or Super7’s. However, the teams should only be managed on their performance against the daily output target. All other metrics should be used to aid in the team’s continuous improvement efforts. Dashboards and spreadsheets give valuable insight in where the autonomous team or Super7 can improve.

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.

Super7 Operations - making it work

Soft Skills for cooperation in Super7 teams

What soft skills are needed for cooperation in Super7 teams – what soft skills are essential for a team to reach cooperational excellence? The implementation Super7 Operations (link) within the operations departments of one of the leading Dutch retail banks is in full swing. Many things need to be taken care of in the preparation phase: small, autonomous production teams (Super7’s) arent’ formed overnight. But one thing in particular is essential for a smooth introduction of Super7 Operations: attention to the soft skills that are needed for working together in a small, autonomous team.
In our experience, the most important soft skills for cooperation in Super7 teams that required training in preparation of Super7 Operations are:
1. Giving and receiving feedback
2. Understanding the development of autonomous teams
3. Effective meetings and making decisions as a team

Let’s look at these subjects in a bit more detail:
1. Basics of giving feedback
• Describe what behavior you have observed
• Explain what effect this behavior has on you
• Check if the person you give feedback understands you
• Indicate what behavior you would like to see

2. Basic development steps of autonomous teams
• Phase 1: group of individuals
• Phase 2: a developing team
• Phase3: a cooperating team
• Phase 4: an autonomous team, striving towards cooperational excellence

4. Basic elements of effective meetings and making decisions as a team
• Use team roles in meetings: chairperson, time keeper, voice-of-the-customer
• Make sure all items on the agenda are well prepared
• Assign a fixed amount of time to each item on the agenda
• Start with giving all participants the chance to say something about the subject – finish the initial round before starting the discussion
• Use a white board or flipchart to write down the most important points
• Keep the focus on solutions and improvement ideas
• Make sure everybody gets their say
• Keep the discussion focused
• Don’t take minutes, write down actions (what, who, when)

For the team managers, the change from traditional Operational Management to Super7 Operations can be even more dramatic than for the team members themselves. More on this change and the required skills for managing Super7 Operations can be found in my book: Super7 Operations – The Next Step for Lean in Financial Services. More information about this book can be found on www.super7ops.com

Maturity Model for Autonomous Super7 Operations Teams

At this moment, Super7 Operations (link) is applied within several operations departments of one of the leading Dutch retail banks. A lot has been learned since. The change from strict daily steering to small autonomous teams –and at the same time keeping all the good things from LEAN and Operational Management – has asked a lot from both the shop-floor employees and their managers. What we noticed is that teams go through several phases, or maturity levels, in their journey towards autonomy. And, team managers need to grow towards supportive leadership and output steering – this too doesn’t happen overnight. 

When we recognised this, it became clear that a maturity model would be very helpful. With this, the transition can be broken up into smaller, more manageable steps. And, for each maturity level, specific training and coaching can be developed to support both managers and Super7 teams.

The maturity model is still a work in progress, and at the moment only available in Dutch. If you’re interested nonetheless, you can request a copy by replying to this post. And, I expect to be able to post an English version of the Maturity Model for Autonomous Super7 Opertions Teams on this site shortly.

I would like to hear your experiences with the development of autonomous teams. You are invited to join the discussion on Super7 Operations on http://www.super7ops.com/