Friction Focused Management

Why winning three battles beats losing ten

“What are your top 3 frictions right now?”

“I don’t have any.”

“You’re lying.”

That is how most of my 1-on-1s begin.

Not because I’m trying to be provocative.
Because zero frictions is a fantasy.

No team, no process, no company runs without friction.
The only variable is whether you’re naming it.

And most people don’t name it.
Not because they can’t see it, but because they’ve been trained not to.

In most engineering cultures, competence is armor.
Admitting friction feels like admitting failure.

Engineers internalize systemic drag as personal weakness.
A broken deployment pipeline becomes a personal puzzle to power through,
a muddy product requirement becomes a test of intelligence rather than a flag of organizational dysfunction.

When someone tells you they have no frictions, they aren’t deceiving you.
They are protecting themselves.
They believe naming friction makes them look weak.

The reality is the opposite:
Naming friction is the first act of leadership.

The Reality: Engineering Management Is a Friction Factory

If you are an engineering manager — or you manage managers — your calendar tells one story and your Slack tells another.

The calendar says:
Weekly syncs, 1-on-1s, roadmap reviews, retrospectives.
Structured. Predictable. Manageable.

Slack says:
Urgent escalations, unblocking requests, HR threads, cross-team misalignments, last-minute scope changes, performance concerns, somebody’s deployment broke something, and three people asking the same question in different channels.

Retros produce action items.
Leadership reviews produce more action items.
1-on-1s surface yet more friction.

By the time you stack it all up, you’re looking at 15 to 20 open items at any given moment — each one with a name attached, each one theoretically your responsibility to move forward.

Most managers respond to this volume in one of two ways.
They either try to hold everything and become the bottleneck,
or they let it all blur into background noise and the most squeaky wheel gets the grease that week.

Neither is a strategy.

Because the real problem is not the number of open items.
It is that they are not equal.

Some are minor annoyances.
Some are systemic blockers.
Some are early signals of something much larger starting to break.

When everything is treated as just another task to manage, the signal disappears into the noise.

And when the signal disappears,
leadership stops managing reality and starts managing symptoms.

Why Friction Is the Real Leadership Signal

Friction is not just work that feels annoying. It is information.

It tells you where your system is slowing down — where decisions are unclear, ownership is ambiguous, processes are outdated, or constraints are misaligned with reality.

Delivery metrics show you the output of the system.
Friction shows you the forces acting inside it.

The problem is that friction is unevenly distributed and often invisible.

Some of it is minor noise that resolves itself.
Some of it is load-bearing — the kind that quietly accumulates until a person, a team, or an entire organization starts drifting off course.

Without a way to distinguish between the two, everything feels equally urgent and nothing gets resolved at the right level.

Most leadership tools focus on what is visible:
Velocity, deadlines, roadmaps, performance indicators.

Those matter.
But they are lagging signals.
By the time they move, the underlying friction has already been there for weeks or months.

Leadership, in practice, is not just about managing work.
It is about managing the invisible forces that shape that work
before they become visible failures.

The question is not whether friction exists. It always does.
The question is whether you have a reliable way to surface the most important friction early enough to act on it.

The Method: Friction Focused Management

FFM — Friction Focused Management — started as a simple shift in how I opened 1-on-1s.

Instead of asking “how’s it going” or running through a project status checklist, I ask one question:

“What are your top three frictions affecting your personal productivity this week?”

The wording is deliberate.

The word “personal” matters because I’m not asking for team metrics or delivery updates. I’m asking what is slowing this specific person down right now.

The friction can be internal — a process their team owns — or external, like a company policy or a cross-team dependency they cannot change.

It doesn’t matter whether it is solvable.
What matters is that it is named.

The constraint of three is equally intentional.

One friction is too easy to dismiss and often not the real blocker. Five or ten turns the conversation into a complaint session with no resolution.

Three forces prioritization. It is the minimum number that reveals a pattern and the maximum most people can articulate clearly under pressure.

Once the three are on the table, we work through them systematically — not all in one conversation, but batch by batch.

Resolve the top three.
Surface the next three.
Repeat.

This creates a working rhythm. Instead of trying to hold fifteen open loops simultaneously, the conversation stays anchored to a manageable set of load-bearing issues.

Over time,
the accumulation of resolved frictions
matters far more than the illusion of tracking everything at once.

What Actually Happens When You Name Friction

The impact of FFM is not just better prioritization.
It is clarity.

One of my reports was a Senior Data Platform Engineer — smart, capable, respected by his peers. Over several weeks, I noticed something shifting. He was becoming anxious — visibly stressed in meetings, second-guessing decisions he would normally have made confidently, slower to ship.

In our 1-on-1s, he described his situation in fragments.

There were team-level frictions.
Company-level constraints.
A few interpersonal dynamics that weren’t clean.

He was holding all of it simultaneously, and none of it clearly.

I introduced FFM explicitly and asked him to name just his top three frictions.
Not everything. Just three.

What happened next was more interesting than I expected.
The act of naming the top three helped him understand his own situation better.

He had been conflating different types of friction — treating a process problem like a people problem, treating an external constraint like something he should fix personally.

Sorting them into three, forced a level of clarity he didn’t have before.

We worked through them one by one over the following weeks.
His confidence returned.
His output improved — not just in my observation, but in his 360 peer feedback.

And eventually he stopped waiting for me to ask the question.
He would come to our 1-on-1s with his three frictions already prepared.

FFM had become his habit,
not just mine.

That is the signal that a framework is working:
When the person you’re coaching internalizes it and starts running it themselves.

The Interview Flip: Friction as a Diagnostic Tool

FFM works because friction is not just a personal experience.
It is a system signal.

The same question that surfaces clarity in a 1-on-1 can reveal just as much when asked at the organizational level.

I’ve been in a lot of interviews over the past year — senior engineering leadership roles across different industries and growth stages.

At some point, I stopped waiting until the end to ask,
“Do you have any questions for me?”
I started opening with one of my own:

“What are the top three frictions you’d like this role to help you solve?”

The responses are more diagnostic than almost any question I’ve been asked in return.

Some companies answer immediately and specifically.
The frictions are concrete — a team scaling from twelve to thirty with no engineering culture to hold it together, a platform migration that keeps stalling because nobody owns the decision, a persistent gap between engineering and product that has already cost two quarters of alignment.

When a company can name three real frictions, it tells you the hiring manager understands their own system.
That is a strong signal.

Some companies hesitate.
They offer generic answers — “we want to scale,” “we need to improve processes.” These are not frictions; they are aspirations.

That usually means the role was created reactively,
in response to something that hurt,
without a clear diagnosis of what actually needs to change.

And some companies perform frictions.
They provide answers that sound thoughtful but feel rehearsed — friction-shaped talking points designed to make the role sound important without revealing anything real.

That is a yellow flag at best.

There is one more category — and it is the most revealing of all.

In one interview, when I asked this question, the response was immediate:

“There are no frictions. I’ve actually fixed everything.”

That answer told me more than anything else could have.

Friction is not something you eliminate permanently.
It is something you manage continuously.

A system with no named friction is not frictionless.
It is opaque. And opacity is where problems accumulate silently.

That was the moment I knew this was not the manager, and not the organization, I wanted to work with.

The question also shifts the dynamic of the conversation.

You are no longer just a candidate pitching yourself against a job description.
You are a practitioner assessing a problem space.

Good companies recognize that immediately — and respond differently.

Candidates rarely use this.
They should.

The Underlying Principle

FFM is not a complicated system. It is an application of a simple idea:
you cannot resolve what you cannot name,
and you cannot name what you have not prioritized.

At its core, friction is not just work that feels inconvenient.
It is information about how a system is actually functioning beneath the surface.

Delivery metrics show you what happened.
Friction shows you the upstream forces that determine downstream outcomes.

Most leadership effort is spent managing what is visible:
deadlines, deliverables, performance indicators, roadmap commitments.

Those matter. But they are outputs.
By the time they shift, the forces influencing them have already been in motion for weeks or months.

The real work of leadership happens earlier, in the invisible layer — where ambiguity, misalignment, unclear ownership, and structural constraints quietly accumulate.

Left unnamed, they do not disappear.
They compound.

The same instinct is behind Bezos’s no-slides rule. When you cannot rely on a polished presentation, you are forced to reason directly about the problem in the room.

Constraints force clarity.
Limiting friction to three works the same way.
It forces you to distinguish between noise and the issues that truly matter.

Engineering management is full of people who are genuinely busy and genuinely stuck — not because they lack effort, but because their attention is distributed across too many invisible forces simultaneously.

FFM does not add another layer of process.
It makes those forces visible, so they can finally be addressed.

A Working Rhythm, Not a One-Time Trick

FFM works not because of the question itself, but because of the rhythm it creates.

Asking once provides a snapshot.
Asking consistently creates visibility over time.

Patterns begin to emerge — recurring dependencies, persistent process gaps, structural constraints that affect multiple people in different ways. What initially appears as isolated friction often reveals itself as part of a larger system dynamic.

This is why FFM should not be treated as a one-off intervention or a clever conversation technique.

It is a continuous loop:
surface the most important frictions,
resolve what you can,
observe what repeats,
and return to the question again.

Over time, the value compounds.

The system becomes easier to understand because the forces shaping it are no longer hidden.
People develop the muscle to diagnose their own friction before you ask.
The organization builds a shared language for naming constraints clearly.

The Question That Starts Everything

If you manage people, try this in your next 1-on-1.
Skip the status check and ask instead:

“What are your top three frictions affecting your productivity right now?”

If they say they don’t have any, tell them — gently — that they’re lying.

Then wait.
Give them the space to think.
Most people have never been asked to name their friction precisely.
When they do, something shifts.

And if you’re interviewing — for any role, at any level — try asking the hiring manager the same question before they ask it of you.
You’ll learn more from that exchange than from most of the rest of the conversation combined.

It starts as a question.
It becomes a practice.
And over time, it becomes the way you lead.
Not by pushing harder, but by seeing more clearly.

Friction is not the enemy.
Unnamed friction is.

---

THE FRICTION STACK SERIES

Part 1 — Friction Focused Management ← you are here

Part 2 — The Attrition Killer · coming soon

Part 3 — Managing What You Cannot See · coming soon

---

---

---

If you found this useful, subscribe to The Socratic Leadership for weekly insights on leadership, AI strategy, and systems thinking.

---

Petros Bountis is a Director of Engineering with 15+ years of experience building and scaling systems and teams in high-stakes, regulated environments. He writes about engineering leadership, AI strategy, and designing resilient systems.