Continuous Improvement via Operational Awareness

Joe Ward on Medium
Thoughts & Opinions
4 min readApr 15, 2022

Modern businesses want to be as nimble as possible; quick to adapt and ideally able to drive change. This requires in-depth knowledge of what you do, and what you don’t do.

This paper details one way of knowing what we need to know about our businesses.

Basic Operational Awareness

Create detailed Value Stream Maps (VSM) for every team and every process. VSMs capture the full scope of a process: what’s produced, by who, using what tools and tasks, taking how long, how often…

They are common tools in Lean/Six-Sigma operational teams, and they help enable several other key operational products:

— Illustrating workflows in VSMs identify KPIs and process bottlenecks or team pain-points that may need to be re-designed or otherwise prioritized.

— Process-Task Matrixes are lists of all tools and tasks that teams action on to see where we have overlap.

A basic Process-Task matrix showing skills used by different roles in an org. This could highlight internal growth paths, or opportunities for teams to skill up and take advantage of resources other similar roles are using.

This tool enables comparisons across similar processes, roles, and teams to see where we have our biggest opportunities, but also to see where we’re already doing things better and facilitate knowledge sharing to bring another team up to level.

Current State reporting: After KPIs are identified, they can be measured. So once we map our processes and see the key sub-tasks (Leading + Lagging indicators) we want to monitor, we can build meaningful reporting.

Institutional knowledge. Track which employees work on core functions, innovations, tool deployments, skills used, and any other company-specific knowledge you want to keep track of (more on this below).

That’s basically it. Value Stream Maps are an extremely under-leveraged tool that can even help in interviews. You can use them to talk candidates through the existing role, what they’re familiar with, what they’d change…

But operations are nebulous, it’s hard data to capture and even harder to maintain and make use of. For this, let’s see how we could structure information on team processes using a VSM to illustrate.

Figure 1

Figure 1: A simple order confirmation VSM. At each step, much more than Takt time and widget counts can be measured. Object models (ie: Figure 2 below) help capture flexible, potentially text-based data in a way that be used for analysis or easily presented via front-end dashboard or webpage (ie: for HR partners leveraging the data).

Figure 2

Using Data to Foster a Culture that’s Comfortable with Change

Object notation can be quickly referenced and looped through by internal webapps, but you can structure your data however you want and should just focus on capturing it for all steps in the process in a usable format.

We can create time variables to compare similar tasks and processes, and qualitative objects that track the skills involved with the tasks, past owners and more. This data, once designed and collected, can be analyzed as-is or visualized in cleaner front-end dashboards for teams to monitor their own KPIs and team profiles.

Process-Task Matrixes map out synergies and gaps for tools and skills. Human Resources can use this data to find more candidates and leaders internally. Procurement and Strategy teams can help find external partners based on real-time strengths and gaps.

Most importantly, sitting down with teams and mapping things out WITH them gives employees the chance to point out bottlenecks and pain points and how they view things. The biggest impediment to change is fear and comfort. Combat that with clarity, even excitement.

Let them own their own Process Maps and make it a part of quarterly goal setting to review the process with managers (or even broader groups). Commit to improvements when possible.

If you listen to their problems and keep them informed about high-level directions the company could take, then they can automate or adapt their roles without fear. They can do it with a mind towards what will make them most valuable to the future state of the company.

Doing quarterly VSM reviews is good practice for enabling a culture of change. Asking employees what they like and don’t like about their jobs is valuable information, and giving them the power to influence that change makes it worth everyone’s time.

By pairing automation with generous skill development budgets and well-communicated dream-scenarios, you empower interested employees to drive their roles towards your dream. And by replacing old work with new, future-focused work, the trade is equitable for everyone.

Summary of Approach

Instead of a central team of Lean consultants descending on teams, make VSM reviews a part of normal quarterly manager-employee discussions. Being consistent with these reviews and having them come from their own teams will make them more meaningful to employees.

This also keeps changes and strategies more at the product/team level, letting people make decisions for themselves with broader corporate strategy in mind, and possibly with input from a central team that reviews well-structured organization data for opportunities.

--

--