Friction Focused Management - by Petros Bountis

Zero frictions is a fantasy. Every team, every process, every company runs with friction. The only question is whether you're naming it. Most people don't - not because they can't see it, but because they've been trained to internalize systemic drag as personal weakness. When an engineer tells you they have no frictions, they aren't lying to you. They're protecting themselves. They believe naming friction makes them look weak. The reality is the opposite: naming friction is the first act of leadership.

The problem with most management approaches is that they treat all friction equally. Retros produce action items. Leadership reviews produce more action items. 1-on-1s surface yet more friction. Stack it all up and you're looking at 15 to 20 open items - each one theoretically your responsibility. Most managers either try to hold everything and become the bottleneck, or they let it blur into background noise and the squeakiest wheel gets the grease. Neither is a strategy. Some friction is minor noise. Some is load-bearing - the kind that quietly accumulates until a person, team, or organization starts drifting off course.

Friction Focused Management starts with one deliberate question: What are your top three frictions affecting your personal productivity this week? The wording matters. Personal means you're not asking for team metrics - you're asking what is slowing this specific person down right now. Three forces prioritization. One friction is too easy to dismiss. Five turns it into a complaint session. Three reveals patterns without overwhelming the conversation. Once the three are on the table, you work through them systematically. Resolve the top three. Surface the next three. Repeat.

The framework works because it creates clarity. One senior engineer was visibly anxious, second-guessing decisions he'd normally make confidently. In fragments, he described team frictions, company constraints, interpersonal dynamics - holding all of it simultaneously with none of it clear. Asking him to name just three forced him to stop conflating different types of friction. He'd been treating a process problem like a people problem, treating an external constraint like something he should fix personally. His confidence returned. His output improved. Eventually he stopped waiting to be asked - he'd come to 1-on-1s with his three frictions already prepared.

The same question works in interviews. Ask the hiring manager: What are the top three frictions you'd like this role to help you solve? Their response is more diagnostic than almost anything else. Some companies answer immediately and specifically - that tells you they understand their own system. Some hesitate and offer generic aspirations like "we want to scale." That means the role was created reactively without clear diagnosis. And some say they have no frictions because they've fixed everything. That's the biggest red flag of all. A system with no named friction isn't frictionless - it's opaque. Opacity is where problems accumulate silently.