What We Fix

BUSINESSES RARELY GET HARDER
FOR JUST ONE REASON.

The symptoms show up everywhere: slow decisions, overloaded people, more meetings, more tools, more handoffs.

But the problem underneath is often simpler.

Choose the situation that feels closest.

01 / WHAT YOU SEE

GROWTH ADDED CAPABILITY. IT ALSO ADDED CONNECTIONS.

→ More people need coordination.
→ More teams create handoffs.
→ More systems create dependencies.
→ More customers create exceptions.
→ More managers create decisions between decisions.
→ More growth creates more internal work.

02 / WHAT MAY ACTUALLY BE HAPPENING

THE BUSINESS IS ADDING COMPLEXITY FASTER THAN CAPABILITY.

Growth does not automatically create leverage.

Every new team, process, system and management layer can create new interfaces.

The cost often hides in the connections: handoffs, waiting, coordination, exceptions, approvals, meetings.

THE NUMBER OF PARTS ISN'T THE PROBLEM. THE NUMBER OF INTERACTIONS BETWEEN THEM CAN BE.

03 / WHY THE USUAL RESPONSE OFTEN MAKES IT WORSE

WHEN GROWTH GETS HARD, COMPANIES OFTEN ADD MORE.

Sometimes that works.

Sometimes it adds another layer to the problem.

WHAT IF WE REMOVE BEFORE WE ADD?

04 / WHAT TO CHALLENGE

QUESTION THE CONNECTIONS.

05 / A BETTER OPERATING LOGIC

BERNIER PRINCIPLES

FRICTION DOESN'T RESPECT DEPARTMENTS.

Customer→Sales→Operations→Approval→Delivery

What looks like a sales, operations, people or technology problem may actually be caused somewhere else in the system. Bernier works on the constraint, not the department label.

06 / TRY SOMETHING

TRY THIS ON ONE WORKFLOW.

TODAY

Choose one recurring workflow with multiple team transitions.

CHALLENGE

Does the work actually require another team, or does the organization chart require it?

TEST

Remove or combine one transition.

PROVE

Compare elapsed time and rework before and after.

07 / WHAT BETTER LOOKS LIKE

GROWTH SHOULD CREATE MORE CAPABILITY THAN COMPLEXITY.

BEFORE

More growth

→more people

→more coordination

→more management

→more complexity

BETTER

More growth

→simpler interfaces

→clearer ownership

→faster flow

→greater capacity

REVEAL THE PATTERN

BERNIER CALLS THIS:

GROWTH COMPLEXITY

The company is accumulating coordination, process and operating complexity faster than it is creating capability.

YOU'VE SEEN THE PATTERN.
NOW FIND WHERE IT MATTERS MOST.

Every company has different constraints. Find the Friction helps identify which pressure deserves attention first.

FIND THE FRICTION

01 / WHAT YOU SEE

THE COMPANY GREW. THE DECISION SYSTEM DIDN'T.

→ Decisions wait.
→ Issues escalate.
→ Knowledge concentrates.
→ Customers ask for specific people.
→ Teams wait for approval.
→ The owner remains involved everywhere.

02 / WHAT MAY ACTUALLY BE HAPPENING

THE BUSINESS HAS MORE PEOPLE, BUT NOT ENOUGH DISTRIBUTED CAPABILITY.

Key-person dependency is not only a people problem.

It can be caused by: unclear authority, missing decision rules, concentrated knowledge, weak escalation boundaries, customer dependency, low trust, poorly designed workflows.

THE PROBLEM ISN'T THAT KEY PEOPLE ARE TOO GOOD. THE PROBLEM IS THAT THE SYSTEM NEEDS THEM TOO OFTEN.

03 / WHY THE USUAL RESPONSE OFTEN MAKES IT WORSE

WHEN GROWTH GETS HARD, COMPANIES OFTEN ADD MORE.

These may reduce symptoms without removing dependency.

WHAT IF WE SHIFTED DECISIONS INSTEAD OF SHIFTING WORK?

04 / WHAT TO CHALLENGE

QUESTION THE CONNECTIONS.

05 / A BETTER OPERATING LOGIC

BERNIER PRINCIPLES

FRICTION DOESN'T RESPECT DEPARTMENTS.

Customer→Team→Manager→Owner→Manager→Team→Customer

What looks like a sales, operations, people or technology problem may actually be caused somewhere else in the system. Bernier works on the constraint, not the department label.

06 / TRY SOMETHING

TRY THIS ON ONE WORKFLOW.

TODAY

Find one decision that reaches the same senior person every week.

CHALLENGE

What information is required? What can be decided without escalation?

TEST

Define a threshold. Escalate only when the threshold is crossed.

PROVE

Measure how often the senior person still needs to intervene.

07 / WHAT BETTER LOOKS LIKE

IMPORTANT PEOPLE SHOULD CREATE LEVERAGE. THEY SHOULDN'T BECOME THE ROUTING SYSTEM.

BEFORE

More growth

→more decisions

→more escalation

→more key-person load

BETTER

More growth

→clearer authority

→distributed decisions

→exceptions escalate

→leadership capacity increases

REVEAL THE PATTERN

BERNIER CALLS THIS:

KEY-PERSON DEPENDENCY

Important decisions, knowledge, approvals and coordination are concentrated around too few people.

YOU'VE SEEN THE PATTERN.
NOW FIND WHERE IT MATTERS MOST.

Every company has different constraints. Find the Friction helps identify which pressure deserves attention first.

FIND THE FRICTION

01 / WHAT YOU SEE

MORE INPUT. NOT ENOUGH ADDITIONAL CAPACITY.

→ More people.
→ More software.
→ More AI.
→ More automation.
→ More vendors.
→ More process.
→ But: People are still overloaded. Work is still slow. Customers still wait. Manual coordination remains.

02 / WHAT MAY ACTUALLY BE HAPPENING

THE COMPANY IS ADDING RESOURCES WITHOUT REMOVING ENOUGH WORK.

Technology can accelerate a workflow. It can also accelerate unnecessary work.

Hiring can increase capacity. It can also create coordination.

Automation can reduce manual effort. It can also introduce maintenance and exceptions.

AI can increase individual output. It can also leave the operating model unchanged.

LEVERAGE ISN'T WHAT YOU ADD. IT'S WHAT THE BUSINESS CAN DO WITHOUT PROPORTIONALLY ADDING MORE.

03 / WHY THE USUAL RESPONSE OFTEN MAKES IT WORSE

THE USUAL RESPONSE

These additions often treat the symptom without addressing the underlying design of the work.

WHAT IF THE WORK SHOULDN'T EXIST?

04 / WHAT TO CHALLENGE

QUESTION THE CONNECTIONS.

05 / A BETTER OPERATING LOGIC

BERNIER PRINCIPLES

FRICTION DOESN'T RESPECT DEPARTMENTS.

System A→person→spreadsheet→System B→person→approval→System C

What looks like a sales, operations, people or technology problem may actually be caused somewhere else in the system. Bernier works on the constraint, not the department label.

06 / TRY SOMETHING

TRY THIS ON ONE WORKFLOW.

TODAY

Choose a recurring workflow where the company has already added people or technology.

CHALLENGE

Where is most of the time actually going? Does the constraint require another resource?

TEST

Measure human effort, elapsed time, waiting, and handoffs.

PROVE

Test one change before adding anything else.

07 / WHAT BETTER LOOKS LIKE

THE GOAL ISN'T TO DO MORE WORK. IT'S TO NEED LESS WORK TO CREATE MORE VALUE.

BEFORE

More work

→more people/tools

→more coordination

→more operating burden

BETTER

More work

→remove unnecessary work

→compress flow

→shift responsibility

→amplify with technology

→greater capacity

REVEAL THE PATTERN

BERNIER CALLS THIS:

LOW LEVERAGE

Additional people, technology, systems or effort are not producing proportional increases in speed, reliability or capacity.

YOU'VE SEEN THE PATTERN.
NOW FIND WHERE IT MATTERS MOST.

Every company has different constraints. Find the Friction helps identify which pressure deserves attention first.

FIND THE FRICTION

What We Fix

BUSINESSES RARELY GET HARDER FOR JUST ONE REASON.

WE GREW. COMPLEXITY GREW FASTER.

TOO MUCH STILL DEPENDS ON A FEW PEOPLE.

WE KEEP ADDING. THE WORK ISN'T GETTING EASIER.

GROWTH ADDED CAPABILITY. IT ALSO ADDED CONNECTIONS.

THE BUSINESS IS ADDING COMPLEXITY FASTER THAN CAPABILITY.

WHEN GROWTH GETS HARD, COMPANIES OFTEN ADD MORE.

QUESTION THE CONNECTIONS.

BERNIER PRINCIPLES

REMOVE BEFORE ADDING.

REDUCE INTERFACES.

DESIGN AROUND OUTCOMES, NOT THE ORG CHART.

MEASURE FLOW, NOT JUST ACTIVITY.

FRICTION DOESN'T RESPECT DEPARTMENTS.

TRY THIS ON ONE WORKFLOW.

GROWTH SHOULD CREATE MORE CAPABILITY THAN COMPLEXITY.

BERNIER CALLS THIS:

GROWTH COMPLEXITY

YOU'VE SEEN THE PATTERN.NOW FIND WHERE IT MATTERS MOST.

THE COMPANY GREW. THE DECISION SYSTEM DIDN'T.

THE BUSINESS HAS MORE PEOPLE, BUT NOT ENOUGH DISTRIBUTED CAPABILITY.

WHEN GROWTH GETS HARD, COMPANIES OFTEN ADD MORE.

QUESTION THE CONNECTIONS.

BERNIER PRINCIPLES

MAKE AUTHORITY EXPLICIT.

TURN JUDGMENT INTO REUSABLE RULES WHERE POSSIBLE.

MOVE DECISIONS TO THE LOWEST RESPONSIBLE LEVEL.

USE ESCALATION FOR EXCEPTIONS, NOT ROUTINE WORK.

MAKE CRITICAL KNOWLEDGE ACCESSIBLE.

FRICTION DOESN'T RESPECT DEPARTMENTS.

TRY THIS ON ONE WORKFLOW.

IMPORTANT PEOPLE SHOULD CREATE LEVERAGE. THEY SHOULDN'T BECOME THE ROUTING SYSTEM.

BERNIER CALLS THIS:

KEY-PERSON DEPENDENCY

YOU'VE SEEN THE PATTERN.NOW FIND WHERE IT MATTERS MOST.

MORE INPUT. NOT ENOUGH ADDITIONAL CAPACITY.

THE COMPANY IS ADDING RESOURCES WITHOUT REMOVING ENOUGH WORK.

THE USUAL RESPONSE

QUESTION THE CONNECTIONS.

BERNIER PRINCIPLES

REMOVE BEFORE AUTOMATING.

MEASURE BEFORE ADDING.

COMPRESS BEFORE SCALING.

SHIFT WORK TO THE RIGHT LEVEL.

USE TECHNOLOGY AS LEVERAGE, NOT AS PROOF OF PROGRESS.

FRICTION DOESN'T RESPECT DEPARTMENTS.

TRY THIS ON ONE WORKFLOW.

THE GOAL ISN'T TO DO MORE WORK. IT'S TO NEED LESS WORK TO CREATE MORE VALUE.

BERNIER CALLS THIS:

LOW LEVERAGE

YOU'VE SEEN THE PATTERN.NOW FIND WHERE IT MATTERS MOST.

BUSINESSES RARELY GET HARDER
FOR JUST ONE REASON.

YOU'VE SEEN THE PATTERN.
NOW FIND WHERE IT MATTERS MOST.

YOU'VE SEEN THE PATTERN.
NOW FIND WHERE IT MATTERS MOST.

YOU'VE SEEN THE PATTERN.
NOW FIND WHERE IT MATTERS MOST.