Great Lakes Continuous Improvement

Systems that work · Cultures that thrive · Excellence that lasts

Which comes first, the processes or the culture they create?

Great Lakes Continuous Improvement helps businesses build both.

A sitting Director of Quality and Continuous Improvement, with nineteen years inside manufacturing plants.

I started Great Lakes Continuous Improvement to solve a problem that I have seen repeatedly across multiple industries: organizations build solid systems and processes, then watch them degrade as ownership blurs, accountability slips, and the people who showed up everyday got burnt out.

“A bad system will beat a good person every time.”

W. Edwards Deming

Alternatively, organizations actively push for a good culture while their systems lag behind, which wears down the people who were asked to care, until caring stops feeling worth it.

Either way, the results end up the same: operational performance suffers, talented people leave, and the financials wither. The bottom line is, quality systems and quality culture must be built at the same time, with sustainment designed into the process so that the structure holds for years.

Tim Morin, Founder and Principal Consultant

The idea behind the practice
What organizations are

Continuous Improvement runs on two things, system and culture, and they are always linked.

Every organization has two dimensions: the systems that power it, and the culture that decides what is possible. Neither one holds on its own.

A manufacturing plant floor
The system

Locks in performance

Done right, it gives customers a reason to trust you.

Left unchecked, it becomes bureaucracy serving itself.

The culture

Decides what is possible

At its best, it pushes people to do remarkable things.

At its worst, it blinds the organization and throttles improvement.

You cannot install a system into a culture that will not use it, or grow a culture with no system to channel it.

PERFORMANCE TIME → system only culture only both nobody runs it the heroes burn out
the same starting point, three different endings
Why organizations break

Four operating modes, and only one of them pays dividends.

Every organization can be mapped to one of four operating modes. Only one of them brings long-term, sustainable value to its customers and its shareholders.

scroll to walk the four modes
Weak systems
Strong systems
Culture
Strong culture · weak systems

Heroic but Fragile

Strong culture · strong systems

Dialed In

Weak culture · weak systems

Crisis as Operating Mode

Weak culture · strong systems

Compliance Theater

Systems →
State one · weak systems, weak culture

Crisis as Operating Mode

Nothing is written down that anyone follows, and nobody expects it to be. The organization runs on recovery: the same problems return, the same people put them out, and the day is measured by what did not catch fire. It is the most common state, and the most stable in the worst possible way, because everyone has adapted to it.

State two · weak systems, strong culture

Heroic but Fragile

The people are the reason it works. They care, they cover for each other, and they carry the operation on their backs. The catch is that heroics do not scale: the moment volume rises or the person who held it together moves on, the performance goes with them. This state never stays put; it either builds the system underneath it, or it slides.

State three · strong systems, weak culture

Compliance Theater

The machinery is good and the paperwork is clean. The audit passes, the corrective actions close, and the metrics are met, while the behavior underneath tells a different story. Signals get suppressed because raising them costs more than hiding them, and the documents slowly stop describing how the place actually runs.

State four · strong systems, strong culture

Dialed In

The system sets the standard, and the culture is what runs it. Problems surface early because the people closest to the work are expected to say so, and improvements hold because sustainment was designed in rather than bolted on. This is the only one of the four that pays dividends year after year, and it is the state this practice is built to reach.

Two root causes, two different approaches.

Follow any failure far enough and it ends in one of two places. A launch failure and a management failure feel similar on the floor, but require different approaches to address.

Root cause one

Launch Failure

The problem was designed in before the first part ran, because the planning work was skipped or rushed. The remedy is structural: the work to prevent the problem happens before the first part runs.

Root cause two

Management Failure

The condition is known and has been accepted. The remedy is a matter of leadership: expectations have to be set clearly, owned, and backed with the resources to meet them.

WHAT YOU SEE WHERE IT ACTUALLY STARTED tooling was not ready the process was never validated material variation nobody studied concerns were raised and ignored the same finding repeats every audit no one actually owns the fix Launch Failure PLANNING SKIPPED OR RUSHED Management Failure KNOWN, AND ACCEPTED
technical symptoms and cultural symptoms lead to different places

Accurately accounting for the problems is not about assigning blame. It is about making sure the solution is implemented where the failure actually happened, so it does not come back wearing a different mask.

Read more about the framework in Dialed In →
Designing organizations that work

None of this is perfected simply by trial and error. Organizations that reach the fourth state design their way there deliberately, and that design work is what my field guide, Dialed In, maps out.

SYSTEM → CULTURE → CRISIS HEROIC THEATER DIALED IN no shortcut
you climb one side first; nobody jumps straight to the corner

This is the idea the whole practice is built on. If it resonates, the field guide is where it goes deep: the four operating modes in full, why organizations break, and what it takes to reach the one state that lasts.

Explore the thinking in Dialed In