What is a Self-Improving System?

 

What is a people network? Connectedness, shared information and reciprocity.  What does it look like? Short, focused, connected huddles around visual boards. Why does it matter?  A strong network is like a nervous system. Think quick response, adjustment and learning. If you pull it off, it’s a gold mine. So how do you build one?

Building a Self-Improving System.

Here are some key elements.

·       Clarity & alignment around Aspiration & Winning Logic. Each level and team translate the these into a tactics & metrics they track on their huddle boards.

·       A Big Room called an ‘Obeya’ (aka Control Tower, Cockpit) that serves as ‘mission control’. The Obeya answers the big strategy questions at a glance. What should be happening? What’s actually happening? What are the biggest blockers & what are we doing about them?

·       Information flows up, and support flows down. “Here's how we're doing, and here are the blockers. Can you please help with this one & that one, boss?”

·       World class problem solving – more to come on this topic in future posts

·       Clear roles: It’s understood that the team owns the problem. Senior leaders help remove the blockers that are beyond the team’s control

What are the enablers?

·       Simple visual standards for all important work

·       Repeatable operating rhythms at each level.

·       Visual management - at a glance understanding of what’s happening

·       Strong connections between teams in the form of Ok/Not Ok tests.

·       Clear rules of engagement such as:

o   Make problems visible – they’re gold

o   Warm heart principle. Hard on the problem but easy on the people. Remember the problem is usually in the process.

o   Respectful inquiry. Leave your rank at the door. Listen more than you speak.

o   Evidence-based management – no Zebras or Hippos![i]

 

Common Blockers

Common failures modes include poor (i.e. invisible, low quality, incomplete) information flow, lack of shared Purpose, and an overly rigid strategy deployment system.

Team Hassles: The ideal team size is typically between 5 & 9 people (e.g. Amazon’s famous ‘two pizza teams’). This sweet spot balances the need for diverse skills & perspectives against the communication & coordination challenges that plague larger groups. There are many other team-related hassles well described by Patrick Lencioni and others.

Information Hassles: E.g. Information that is incomplete, low quality or invisible. Team boards can be both analogue & Digital, but a messy analogue board is more compelling.

Lack of Shared Purpose: Have we articulated our purpose in clear simple language?  Can team members explain in their own words? Leadership is oratory, leadership is storytelling.

Dysfunctional Cultural Norms: Reciprocity means ‘you scratch my back, and I’ll scratch yours’.  Incentive structures obviously help but are not enough. Cultural norms around Safety, Respect for People, Teamwork and other core principles drive reciprocity.  Great companies provide continual nudges in this direction. Leaders at every level have a shared set of values that they reinforce through shared ‘ceremonies’.  Culture is what you do when nobody is watching.  Over time these shared routines and norms permeate you way of thinking and behaving.

Here’s an example from early in my career. The scene: my first day at Toyota, in the manager onboarding program.  Our instructor began by drawing three ovals, one at a time, and labelling each:

·       Oval 1: something for the customer & community

·       Oval 2: something for the team member

·       Oval 3: something for the company

My fellow trainees and I stared at the Toyota logo.  It’s a nudge I’ve never forgotten.

That said, please do not copy Toyota or any other company. Make a system that fits your company, culture and industry.  Weave in the fundamentals, run experiments and keep getting better.

Best regards,

Pascal Dennis

E: pascal.dennis@leansystems.org

---

[i] Highest paid person’s opinion; Zero expertise but really arrogant.