Episode 3

full
Published on:

7th May 2026

Episode 3: Name That Friction!

Okay, Actually is a podcast for people who are working hard, still falling behind, and are starting to wonder if the problem is them. It's not.

Each episode — always under 25 minutes — we dig into what's truly broken and figure out how to build a solution that can actually work.

In this episode, I walk through what friction actually is, why you've probably stopped feeling it, and how to locate exactly where it lives — because a people problem solved with a process solution doesn't get fixed. Location matters.

00:00 Never Check Your Bags

04:11 When Friction Gets Normal

06:18 Acceptance vs Surrender

09:45 Five Ps Framework

18:21 Friction vs Ground Truth

21:42 Wrap Up and Connect

The Five Ps

  1. People: is the friction coming from a person, a dynamic, or someone in the wrong role?
  2. Process: is the friction built into how things are or have always been done?
  3. Product: is the friction in the tool or system everyone's working around instead of through?
  4. Place: is the friction in the environment itself?
  5. Priorities: is the friction coming from direction that's unclear, contested, or unresolved?

Find me here:

OkayDoak.com

karen@okaydoak.com

Get clear. Get sorted. Get going. Stay sane.

Transcript
Karen:

I think we've all had that unfortunate experience when

2

:

traveling where the bag that

you didn't want to check in the

3

:

first place ends up not arriving.

4

:

I don't want to pick on any particular

airline, so let's just come up

5

:

with a generic name like American.

6

:

Picture this.

7

:

I'm standing at baggage claim.

8

:

I'm waiting.

9

:

I'm looking for my bag.

10

:

It's not there.

11

:

I go to the American Airlines counter.

12

:

The staff says, "Oh, it probably went

to terminal F," which seems super

13

:

weird when you're in terminal D.

14

:

But I walk to terminal F from D, and the

team at that counter basically laughs

15

:

in my face, and they're like, "Why

would a bag from a terminal D flight be

16

:

in a terminal F, you complete idiot?"

17

:

Which they didn't necessarily

say, but I felt that because we're

18

:

talking about the Philadelphia

Airport, that was definitely implied.

19

:

I walk all the way back.

20

:

The person who was originally

there is now on break.

21

:

I fill out a form.

22

:

They give me, like, a 47-digit

code and a login to a portal.

23

:

And when I log in there later, there's

no updates, and so time passes.

24

:

And finally, one day my phone rings.

25

:

I answer it, and I hear, "Hello, Mrs.

26

:

Dork.

27

:

We found your bag."

28

:

In the rankings of how I'd like this

to have gone, ideal state would've

29

:

been never losing my bag at all,

followed by finding it quickly.

30

:

But waiting several days and then

being name-called was definitely

31

:

close to the bottom of the list.

32

:

And it's not because they were bad people.

33

:

It's not because they didn't

care, although I don't

34

:

think they cared that much.

35

:

But it's because there was just so much

friction built into the system, and nobody

36

:

on the inside was experiencing it the way

that I did on the outside as a customer.

37

:

To them, they get told about

a missing bag, and when they

38

:

find it, they just call Mrs.

39

:

Dork.

40

:

But to me, it was a case of every

single step in the process being

41

:

harder than it needed to be.

42

:

That's what we're going

to talk about today.

43

:

I'm Karen Doak.

44

:

This is OK Actually, where we get clear,

get sorted, get going, and stay sane.

45

:

So that's obviously the experience on

the customer side of things, but I've

46

:

seen and noted the same experience

internally at companies where I've worked.

47

:

A customer has a question.

48

:

It's the kind of question that another

customer has definitely asked before.

49

:

It's not a trick.

50

:

It's not a gotcha.

51

:

It's the kind of question that if your

organization is doing what it says it

52

:

does, it should be answerable in, let's

say, 20 minutes or so of light searching.

53

:

But it isn't, and that's not because

anyone is incompetent or slacking.

54

:

If you watch all of the internal activity

that goes on to try to get an answer

55

:

to the question, the emails, Slack

messages, "Hey, do you have this?"

56

:

pings, the pinging again, the casual,

"Hey, I don't mean to pester, but still

57

:

trying to get an answer for so-and-so."

58

:

It looks like effort because it is effort

because there's no actual result Effort

59

:

and answers are not the same thing.

60

:

The answer ultimately lives nowhere,

or alternatively, it lives in 12

61

:

places that don't talk to each other.

62

:

There's poor documentation, lack of

ownership, institutional knowledge

63

:

locked in the head of someone who

may not even be there anymore.

64

:

Twenty minutes becomes a month,

and the team works hard the whole

65

:

time to try to get an answer.

66

:

Internally, it felt like effort, but

externally, it looked like incompetence.

67

:

The friction might end up feeling

invisible to you when you're the

68

:

one chasing it inside, and you get

completely used to it, but it's totally

69

:

visible to the customer as well.

70

:

So that's what we're

talking about today, right?

71

:

Friction, the organizational,

personal, structural kind, the drag

72

:

that slows everything down and costs

more than you know, and that you've

73

:

probably stopped noticing a lot of

because you totally get used to it.

74

:

It just becomes an expectation.

75

:

We're gonna talk about what happens

when you stop noticing, how to

76

:

find it when you look for it,

and what to do when you find it.

77

:

Because the answer is not always

fix it, and it's definitely

78

:

not always just accept it.

79

:

There's a thing that happens in

organizations, and frankly, in families

80

:

too, and, and personal work groups,

where friction just gets absorbed into

81

:

the standard operating assumption.

82

:

You stop flinching.

83

:

You start saying, "Oh, yeah, it's gonna

take us a few weeks to get you that

84

:

answer," without your eye twitching.

85

:

And when you say it, it's the

kind of sentence that has stopped

86

:

feeling like an apology and

started sounding like a policy.

87

:

And here's the problem.

88

:

Your customer doesn't stop

feeling it, and you know that

89

:

because you've been that customer.

90

:

The person on the receiving

end of the broken process is

91

:

still living it in real time.

92

:

They're living exactly what

you've learned to accept, and

93

:

they don't have your context.

94

:

They don't know about the CRM

migration or the staffing gap or

95

:

the fact that Q4 was just a lot,

and everyone's still recovering.

96

:

They just know it's been two weeks.

97

:

They still don't have an answer to

a question they thought was pretty

98

:

simple, and they asked in good faith.

99

:

What you've stopped feeling,

they never stopped experiencing.

100

:

This is actually the most expensive

thing for an organization or a group

101

:

or even an individual that's not

being tracked because it's not just

102

:

the month of bad experience, but it's

the compounding erosion of trust.

103

:

The customer who stops asking, not

because they don't need help anymore,

104

:

but because they already know that

the answer's gonna piss them off.

105

:

The employee who stops flagging

problems, not because the problems

106

:

went away, but because they've run out

of faith that flagging does anything

107

:

when they hear their boss is just

saying, "Look, I've raised that issue.

108

:

I've tried to solve it, and it's

not going anywhere, so please

109

:

just stop bringing it to me."

110

:

The relationship, whether it's

professional, personal, or institutional,

111

:

it develops a workaround instead of a

resolution, and the workaround is that

112

:

it becomes standard in the relationship.

113

:

Friction doesn't disappear

when you normalize it.

114

:

It just stops being visible to

the people who could fix it, and

115

:

that's not a neutral outcome.

116

:

That is a slow leak in a building

that you thought was solid.

117

:

That moment that you start to say, "Yep,

it's just gonna take a couple weeks,"

118

:

without flinching, you've made a decision.

119

:

You've decided that this is

just how it is, and maybe it is.

120

:

Maybe three weeks is genuinely the

best the system can do right now,

121

:

given real constraints and real humans.

122

:

Maybe.

123

:

But there's, there's a critical

difference between two things that can

124

:

look identical from the outside, and

that's an important distinction to draw.

125

:

The difference between informed

acceptance and passive absorption.

126

:

Informed acceptance is, "I know

exactly why this takes three weeks.

127

:

I've looked at it.

128

:

I've decided consciously that it's

not mine to fix right now, or that

129

:

the cost of changing it outweighs

the cost of absorbing it, or that

130

:

I'm not even someone who can solve

it without buy-in from others, and

131

:

that's not coming anytime soon, and

ultimately, I'm budgeting for it.

132

:

I, I made a choice."

133

:

Whereas passive absorption is

more, "It just takes three weeks.

134

:

It's always taken three weeks.

135

:

I've stopped asking."

136

:

Those two sound almost identical

out loud, but they're not the

137

:

same thing because that second one

is actually a type of surrender.

138

:

Last week, I talked about Pepper,

my aging soulmate of a toy poodle.

139

:

On the other end of the dog spectrum

from Pepper is my other poodle, Sam.

140

:

Sam is not a smart dog.

141

:

Sam has a whole host of issues.

142

:

We had a, a dog whisperer named Big

Chuck who said that he had level two

143

:

anxiety but wouldn't tell me what that

meant or even how many levels there are.

144

:

But one of the areas that Sam has major

issues with is any slippery surface, or

145

:

I guess you could say lack of friction.

146

:

When we built the house we're in right

now, we chose wood floors and even a

147

:

wood staircase without a runner on it

because, as I said to Jeff, "I'm not

148

:

gonna make a decision about my home

based on the anxiety of a ten-pound dog."

149

:

Sam did not get a vote.

150

:

But since then, Sam has scratched up the

stairs doing these panic leaps at the

151

:

top and bottom of landings, and now I

have to have rugs that I don't like in

152

:

places I did not even want rugs because

otherwise Sam can't even get from one

153

:

room to the next, and he just sits and

cries until someone comes to get him.

154

:

So I chose the floors.

155

:

I guess I chose Sam.

156

:

I live with the rugs.

157

:

I've totally normalized this.

158

:

I walk over a rug that I hate

every single day, and we just

159

:

tell guests, "Oh, that's Sam."

160

:

Actually, his dog tag just says, "Oh,

Sam" because- Guys, this dog needs help.

161

:

Anyway, that's Sam, and that's just

the calm of someone who has made peace

162

:

with that decision three years ago.

163

:

I have informed acceptance.

164

:

I know the ground truth.

165

:

I chose specific floors.

166

:

My dog is afraid of those floors.

167

:

In fact, the rugs are the only

place in this entire story where

168

:

I want more friction, not less

169

:

I didn't just absorb rugs as

an inexplicable feature of

170

:

the house that I didn't want.

171

:

You can't fix what you won't name.

172

:

"It's hard to work here" is not a

diagnosis, it's a weather report, so you

173

:

can either complain about the rain, or you

can try to figure out how to fix the roof.

174

:

Friction isn't ambient.

175

:

It isn't floating in the air, like,

just as a general vibe of difficulty.

176

:

It comes from somewhere, and once you

locate it, once you give it an address,

177

:

you have something to work with.

178

:

It's pretty standard business

nomenclature that there are three

179

:

Ps, or sometimes four Ps or five Ps.

180

:

I'm gonna have five Ps in this example.

181

:

People, process, product,

place, priorities.

182

:

I'm gonna walk through each one with

you and what it has to do with friction.

183

:

And the reason that I'm putting

together a taxonomy here, and the

184

:

reason taxonomy matters, is that each

of these requires different fixes.

185

:

A people problem solved with a process

solution isn't really getting fixed.

186

:

A priorities problem solved with better

software definitely isn't getting fixed,

187

:

and all of those details really matter if

you're trying to solve what's going on.

188

:

So people friction.

189

:

People friction is not always

about a bad person or a difficult

190

:

employee or a challenging boss.

191

:

Sometimes it's a capable

person in the wrong role.

192

:

Sometimes it's a good relationship with,

an unresolved conflict underneath it.

193

:

Sometimes it's someone who was

exactly right for a company of 20 and

194

:

is now a structural problem at 80.

195

:

I was on the receiving end of people

friction when I was trying to get a prior

196

:

authorization from my insurance company,

which seems simple enough in theory,

197

:

except that this particular insurance

company only sends them via snail mail

198

:

and fax and probably carrier pigeon.

199

:

And when it still hadn't arrived in a

timely manner by mail, I then was trying

200

:

to figure out how to get it faxed,

only to learn that there's one person

201

:

in this entire company who handles

the fax machine-- I'm sorry, the fax

202

:

department, and they work part-time

And I know that I'm talking about

203

:

a fax machine in twenty twenty-six.

204

:

I get it.

205

:

But it didn't occur to me that a company's

only ability to send information that

206

:

is quick and timely would be restricted

to a single part-time employee.

207

:

The request ultimately just sits.

208

:

The fix isn't firing someone.

209

:

The fix is making sure a critical

workflow doesn't run through

210

:

a single human with no backup.

211

:

That's a staffing decision,

not a process memo.

212

:

But you can't get there if you just

say, "Oh, this is an issue with my

213

:

insurance company being stuck in 1995."

214

:

." Process friction is a bit of a

different story, and it's often

215

:

invisible because it's built into

how things have been done forever.

216

:

You're not seeing the friction.

217

:

You're just seeing what's normal

for various groups or organizations.

218

:

You can usually tell that it's a process

friction issue when people say things

219

:

like, "Oh, it's always been this way.

220

:

That's just the way it is."

221

:

I think very fondly, in finger quotes,

about when my son was on the swim and

222

:

dive team with 80 other boys, and as

a result, over 100 parents were all

223

:

on the hook to volunteer for things.

224

:

It was just part of the requirements.

225

:

And we needed to sign up

for various snack slots.

226

:

So I signed up for every single

possible snack slot on one single

227

:

day because I'm being efficient.

228

:

Get it done, handle it once, move on.

229

:

One trip to the store,

one time to drop it off.

230

:

You know what?

231

:

I should be honest here, too.

232

:

I was obviously not

gonna drop it off either.

233

:

So one time to put it in the

trunk of my kid's car and

234

:

make him drop it off one time.

235

:

But a mom on the team reached out

and gently Passive aggressively, but

236

:

gently, let me know that the way it is

supposed to work is that everyone signs

237

:

up for one slot, but on different days,

spread out across the season so that

238

:

multiple people had the opportunity to

participate at different points in time.

239

:

This mom is not the problem.

240

:

She's just doing exactly what the swim

moms before her did and the swim moms

241

:

before them, faithfully guarding a

process that's been handed down like

242

:

scripture and never once questioned.

243

:

But here's the actual issue.

244

:

One person handling all the snacks

in one trip is more efficient,

245

:

objectively more efficient.

246

:

Fewer store runs, fewer drop-offs, fewer

scheduling variables, better for both

247

:

the environment and my own mental health

248

:

. The process she's defending makes

everyone's life harder for no

249

:

discernible reason except that

it distributes the participation.

250

:

I don't care about the

participation being distributed.

251

:

This isn't even my team.

252

:

It's my kid's team.

253

:

And all of that apparently matters more

than whether the process makes sense.

254

:

Documenting a bad process is just a more

efficient way to do the wrong thing.

255

:

The fix isn't telling the

new person how it works.

256

:

The fix is asking whether it

should work that way at all.

257

:

Product friction.

258

:

Product friction is different.

259

:

It's often expensive because it touches

everyone who uses it every single day.

260

:

It's also one of the most underestimated

sources of drag because people adapt

261

:

to it thinking that that's just

what the product is there for and

262

:

the workaround then becomes normal.

263

:

Normal becomes invisible and at

some point you're running a business

264

:

on top of a stack of workarounds

that nobody has ever fully mapped.

265

:

This is not meant to be a dig at

Salesforce, but I have had this

266

:

experience with Salesforce so many times.

267

:

Salesforce exists and it's supposed to

be the core CRM and system of record.

268

:

But nobody is using it consistently.

269

:

Nobody is updating it.

270

:

And for that reason, nobody trusts

Salesforce because the data is

271

:

incomplete, because nobody updates

it, because nobody trusts it,

272

:

and such goes the cycle of hell.

273

:

Someone needs a list of

specific customer subset.

274

:

They can't pull it

reliably from Salesforce.

275

:

So then they have to build a Google

sheet and ask everyone to update it.

276

:

Ten days later, they need a

slightly different subset and

277

:

maybe two different fields added.

278

:

So now there's another sheet.

279

:

Another question comes in.

280

:

We need another Google sheet to answer it.

281

:

Nobody had time to update Salesforce

because everyone knew that unless every

282

:

single person in the company updated it,

it still wouldn't be the source of truth.

283

:

They just have to make

the spreadsheet anyway.

284

:

So the tool exists, but almost

as a monument to the problem

285

:

rather than a solution.

286

:

Place friction.

287

:

Place friction is the one that nobody can,

like, put in a customer service ticket.

288

:

The environment shapes behavior

constantly and invisibly.

289

:

Who can focus?

290

:

Who can collaborate?

291

:

Who ends up just staying home?

292

:

And because it's not a person or a

process you can point to, it tends to

293

:

get absorbed as just the way things are.

294

:

I think a lot about post-COVID, when

we'd gotten used to, remote meetings,

295

:

and every meeting has a Zoom link

attached, and most offices, even if

296

:

they've returned to work, still had

a decent number of remote workers.

297

:

The office is an open floor plan

with not enough enclosed rooms or

298

:

meeting rooms, and so on heavy meeting

days, you really have two options.

299

:

You book a room three weeks out and

hope no one stole it by the time

300

:

you get there, or you stay home.

301

:

And so people stay home, and the

office fills up with the people who

302

:

don't need to meet with each other

and is empty of the people who do.

303

:

And then the company's just paying rent on

an office while navigating everything that

304

:

still comes with having a remote team.

305

:

Leadership starts worrying about

engagement and connection and

306

:

culture, and the root cause of

all of that is the floor plan.

307

:

But nobody puts that in

the engagement survey.

308

:

Priorities.

309

:

This is an under-named one when it

comes to friction, but I think it's

310

:

a real culprit a lot more often than

people might give it credit for.

311

:

Priorities friction is often

misdiagnosed as more of a

312

:

communication issue or a process issue.

313

:

You can improve communication

all you want, but if the

314

:

underlying direction is unclear or

contested, you will still be slow.

315

:

You will not be able to pick up the pace.

316

:

You'll just have better documented

slowness, like that sloth who

317

:

works at the DMV in Zootopia.

318

:

I, I think a little bit about this

when I worked in one organization

319

:

where we were ultimately trying to

evolve from a focus on services to a

320

:

focus on software, but without a real

plan or timeline to make that happen.

321

:

The software wasn't built

yet, so it wasn't there.

322

:

Customers still needed services.

323

:

The services team is still doing

the work and still generating

324

:

the revenue, but every staffing

conversation becomes impossible.

325

:

You can't hire for services when

you're gonna move away from that.

326

:

You're trying to hire for tech,

but you don't have the revenue

327

:

to support the headcount.

328

:

And the criteria is constantly shifting

depending on who presented in the meeting

329

:

last and who had the best case for what

needed to happen in the next few weeks.

330

:

Nobody in the room can really

acknowledge that both things were

331

:

true and that the real problem was

that direction hadn't been resolved.

332

:

It was a declared intention,

but not with formal commitments.

333

:

And that's a totally different thing.

334

:

You'll know you're in a priorities

problem when simple decision takes

335

:

forever because nobody can agree

on the criteria for making it.

336

:

The meeting keeps happening.

337

:

The decision keeps not getting made.

338

:

That's not a people problem.

339

:

It's not a process problem.

340

:

The direction itself is what's unresolved

and every decision pays tax on that.

341

:

So with these five P's, people,

process, product, place,

342

:

priorities, which one is yours?

343

:

Just take a moment to see if you can

identify what's the source, what's

344

:

the real source of friction that's

causing you the most pain at the moment.

345

:

You see, that's the distinction I really

want to make sure I'm clear about.

346

:

Friction is what you feel.

347

:

Whereas last week we talked

about ground truth and ground

348

:

truth is why friction exists.

349

:

Friction is the symptom.

350

:

It's the month that it takes

for an answer, the three-step

351

:

approval for a $200 expense.

352

:

It's 100 parents each bringing one bag

of Doritos to 12 different swim meets.

353

:

Whereas ground truth is the

structural reality underneath.

354

:

Nobody owns knowledge management.

355

:

Not because people are lazy,

but because when the company was

356

:

small, it wasn't really needed.

357

:

And no one built the

infrastructure as the company grew.

358

:

Decisions require VP sign-off

because trust was never built at

359

:

the team level and nobody ever

figured out how to delegate.

360

:

So getting to ground truth is

ultimately the full diagnostic.

361

:

It's what you need when you

have the standing and the

362

:

leverage to fix the source.

363

:

But you don't always have

access to the source.

364

:

You might be a customer, a middle

manager with no budget authority

365

:

or a parent dealing with the PTA.

366

:

You can see the friction.

367

:

You can guess at the ground truth, but

you can't fix the underlying architecture

368

:

because you're not in that meeting.

369

:

It's not your call.

370

:

And that's not a failure.

371

:

It's just a totally different problem.

372

:

So when you can't fix the

source, the question shifts.

373

:

How do I reduce the drag that

this creates in my life given

374

:

that I can't change the structure?

375

:

You find the one person inside the

broken system who actually knows

376

:

things and go directly to them.

377

:

You stop sending tickets into the

void and you make a phone call.

378

:

You budget three weeks

instead of two days.

379

:

So you stop being surprised

every time it takes that long.

380

:

You build a workaround that

actually fits your life like rugs

381

:

in places you didn't plan for rugs.

382

:

Sometimes I think a lot about my

therapist when I lived in New York.

383

:

I went to him one time with, I wanna

be clear, not like a real problem,

384

:

and I said, "You know, ugh, I go into

every weekend with so much negativity

385

:

because every Friday afternoon at

work, Morgan comes by my desk and

386

:

is a total downer and just puts

me in a bad mood for the weekend."

387

:

And my therapist was like, "Well, how

do you, how do you think you fix this?"

388

:

And I said, "Oh, I, I don't know.

389

:

I guess I have to have a conversation

with Morgan and let her know how I feel."

390

:

And my therapist was like, "You

could do that, or you could just

391

:

stop talking to Morgan on Fridays."

392

:

The goal isn't zero friction,

because that's not a real place.

393

:

Friction is inherent to complexity.

394

:

Friction is inherent to

other humans existing.

395

:

Some friction is just the natural result

of doing things that actually matter.

396

:

So the goal becomes no

unexamined friction.

397

:

You wanna know what you're

living with and where it comes

398

:

from, and make a real deliberate

choice about what to do with it.

399

:

Fix it, reduce it, organize

against it, accept it consciously

400

:

with your eyes wide open.

401

:

"Yep, it's gonna take three weeks," can

be the end of the sentence, but it doesn't

402

:

need to be the end of the conversation.

403

:

Sometimes you wanna really get

to the bottom of an issue, and

404

:

sometimes you wanna just stop

talking to Morgan on Fridays.

405

:

I'm Karen Doak.

406

:

This is Okay, Actually.

407

:

If something in this episode

landed for you, if you identified

408

:

a friction source in your own work

or life, I'd love to hear about it.

409

:

You can find me on LinkedIn or by email.

410

:

Everything's in the show notes,

and I'll see you next week

Listen for free

Show artwork for Okay, Actually

About the Podcast

Okay, Actually
Okay, Actually is a show for people who are competent, well-resourced, and still somehow building the plane while flying it. Each episode is a direct conversation about the problems, decisions, structures, and resets that get you from chaos to clarity — without the fluff or the hustle gospel. Get clear, get sorted, get going, stay sane in under 30 minutes.

About your host

Profile picture for Karen Doak

Karen Doak