It Is Not the Technology

Inside the Process Episode 2: "It's Not the Technology"

Some names and identifying details in this series have been changed to protect client confidentiality. The consulting process, conversations, and outcomes are real.

Most business problems don't start with technology. They start with friction. Work takes longer than it should. Decisions get delayed. Priorities drift. People work harder but somehow make less progress. Over the next several months we're documenting a real consulting engagement to explore what causes that friction — and what happens when you start removing it.

There's something that happens when you actually track your time. Not estimate it. Not guess at it. Actually track it — every hour, every task, every interruption written down and accounted for.

What most people find isn't what they expected. They already knew they were busy. What they didn't know was the shape of it. Where the time was really going. Which things were eating more than they should. And underneath all of it, the pattern they'd been too close to see.

Marcus came into the second session with his homework done.

He'd broken his week into categories — Meridian Financial, Hargrove & Associates, Apex Systems, content and podcast work, house, family, contractors. Hours logged, tasks noted, interruptions counted. He'd even run it through AI to build a structured document from Rob's questions, then gone back and filled it in himself.

It was good work. Thorough. Honest. And what it showed was about to reframe everything.

Rob opened the way he usually does — not with an answer, but with a question. "What surprised you the most from doing that exercise?" Marcus thought for a second. The biggest time sink wasn't the client work. It wasn't the day job. It was the developer work — the content pipeline, the podcast, the social media scheduling, the blogs. The thing he was building to free up his time was still the thing consuming the most of it.

But he wasn't surprised by that. He knew it was coming. What he couldn't shake was something simpler and harder to fix. "The worst part is I know where I need to be putting my time, but the problem is other responsibilities with clients and work." He said it almost matter-of-factly. But it sat in the room for a moment.

Because that's not a scheduling problem. That's not something a better calendar fixes. That's a person who can see exactly where they need to go and keeps getting pulled away before they can get there. Week after week. The path is clear. The distance never closes.

Rob heard it. He didn't jump to solutions. He kept going.

They worked through the data piece by piece. The content pipeline — an hour and a half a week Marcus was trying to compress to fifteen minutes with an automation tool he was still building. Social media scheduling eating time not because the work was hard but because the platforms were poorly designed. Blogs taking thirty minutes each even with AI assistance, because checking the work still takes time whether a person or a machine wrote it first.

Then Hargrove & Associates. Training sessions that were supposed to take two hours had stretched to five. A go-live date approaching fast. A full staff training session being set up in a break room. Marcus could see the finish line. He was getting there. But the client relationship had worn thin.

"It's about pissed me off to the point where I want to walk away."

He didn't walk away. He was too far in and too professional for that. But the feeling was real, and it mattered — because a client who has pushed a capable person to that edge isn't just a difficult client. They're a drain that goes beyond hours on a timesheet.

Then Meridian Financial. And the conversation changed. "Meridian got interesting," Marcus said, almost casually. "We fired a contractor Friday. The other guy gave notice. And the new one we brought on three weeks ago is starting to go MIA." He kept going. His normal workload was manageable. This week they'd been handed more than double. Two people were walking out the door mid-project. A full working system was due by Wednesday. And the one person who held all the critical knowledge — the architecture, the decisions, the context that lived nowhere except inside his head — couldn't be pinned down.

"We are the piece everything else depends on. There are eight teams waiting on us by next Wednesday. If they don't have it, they're blocked." Rob asked the question quietly. "So if Peter leaves tomorrow — you're dead in the water." Marcus didn't hesitate. "We're not gonna make our deadlines. We'll figure it out. But we'll essentially be starting over." Then, almost as an aside — "I don't know, I've lost track of days at this point." It wasn't dramatic. It wasn't a cry for help. It was just a man so deep in it that the calendar had stopped making sense. And somehow that made it land harder than anything else he'd said.

Rob sat with that for a moment.

Then he asked the question that shifted the whole session. "How many of the issues you've been dealing with — across all of it — are actually technology problems?" Marcus thought about it. Really thought about it. Almost none of them.

The content pipeline was a technology problem he was actively solving. But the Hargrove delays? People. The Meridian chaos? People. The waiting, the rebuilding, the work that shouldn't have been necessary — all of it traced back not to broken systems but to broken handoffs. Knowledge that lived in one person's head. Decisions made at a high level with no one responsible for writing them down.

"Yeah," Rob said. "That's what I'm hearing too."

He pushed a little deeper. How much of the time Marcus spent waiting that week was dead time — waiting on someone to respond, waiting on a review, waiting on a sign-off that never came? Marcus ran the numbers. Three days at Hargrove for someone to flag a problem they'd known about immediately. At Meridian Financial — at least twenty hours lost to waiting. Twenty hours. In a single week. "And how much of that," Rob asked, "involved information that only exists in one person's head?" Marcus didn't pause. "All of it."

That's when Rob shifted gears.

He'd been listening not just to the work story but to everything around it. Something Marcus had mentioned early in the session had stayed with him — almost thrown away in the middle of a longer thought. Rachel had fallen. She couldn't walk for three days. And Marcus had spent the week pulling himself away from whatever he was working on to check on her, over and over, unable to stay in one place mentally or physically.

Rob asked about it directly. How much of that checking in, he wanted to know, was actually necessary — and how much of it came from the belief that everything depended on him? It landed like a stone dropped into still water. Marcus was quiet for a moment. Then honest. Rachel wouldn't ask for help. Even when she couldn't walk, she'd gotten up to let the dogs out herself rather than call for him, then sat in pain for hours because of it. So yes — he checked on her. Because if he didn't, she'd push through something she shouldn't.

Rob didn't argue with that. He understood it. But he held the question open anyway and let Marcus sit with it. Because what he was really asking was something bigger than Rachel's fall. He was asking Marcus to look at a pattern — the way he'd become the necessary person in every situation. At work. At home. In his business. The one everything ran through. The one who couldn't step away because if he did, something would break.

Was that always true? Or was some of it a story he'd been telling himself for so long he'd stopped questioning it? Marcus had mentioned something else quietly, almost in passing, that stuck. He hadn't been to his coworking space in almost a year.

"It really pisses me off," he said, "because that place really helped."

It was a small thing on the surface. A desk in a shared office. But what it represented was the last place Marcus had that was just his — no contractors, no Rachel needing help, no construction noise, no context switching. A place where he could close the door on everything else and just think. And somewhere in the chaos of the last year, he'd lost it. That's not a productivity problem. That's a person who has slowly given up every piece of space that was his own.

The homework Rob gave Marcus was a simple framework to apply to every major area of work in the week ahead. For each one, track five things: What work happened. Who could have done it. Who actually did it. What would stop if that person disappeared for two weeks. And what information exists only because that person remembers it. Then one final question for every person who showed up as a bottleneck. Is the dependency on them required, convenient, or assumed?

Required meant there was no other way. It was what it was. Convenient meant someone had become the go-to not because they had to be, but because it was easier than spreading the knowledge around. And assumed — assumed was the most interesting one. Assumed meant everyone believed this person was irreplaceable, but if you looked closely, they didn't have to be. The reliance on them was a habit, not a necessity.

Marcus turned it over out loud. He could already see it applying everywhere. At Meridian Financial, where Peter was genuinely required right now — but where some of what flowed through Peter did so by convenience, maybe even by design. At Hargrove, where a single contact had become a bottleneck not because the work required it but because that's how things had been allowed to develop. Even at home, where the question of required versus assumed was harder to sit with but no less worth asking.

"I almost think," Marcus said slowly, "that what I put together is something I'd want to share with the Meridian team. But I'm worried that if I do, they'll look at it and think — he should be in a management role." Rob didn't dismiss it. He told Marcus to include that tension in his answers next week. Because that discomfort — the fear of being seen as the person who should be driving when he didn't want to drive — that was worth looking at too.

The session closed the way good ones do. Not with resolution, but with clarity. A week ago Marcus had a general sense that things were heavy. Now he had something more specific. The chaos hadn't changed. The workload was still double what it should be. Peter was still the only person who knew how the whole thing worked. The content pipeline was still unfinished. But

Marcus could see it differently now. Not as a pile of problems to push through. As a set of people and dependencies to examine. Some required. Some convenient. Some assumed. And assumed, it turned out, was where the real work was waiting.