What Feels Heavy?

For years we’ve helped organizations improve systems, and streamline processes. What we’ve learned is that most business problems don’t begin with technology. They begin with questions. Questions about time. Questions about priorities. Questions about communication. Questions about why work feels harder than it should. This month RB Consulting is beginning a new project with a client who has agreed to let us document the journey. Names and identifying details will be changed, but the conversations, challenges, discoveries, and lessons will be real. Over the coming months we’ll share observations from the consulting process as we work together to uncover bottlenecks, improve workflows, evaluate opportunities for automation, and identify where AI may—or may not—provide value. Our goal isn’t simply to showcase solutions. Our goal is to show the process behind finding them.

A new ongoing series from RB Consulting

Inside the Process: Following the journey from frustration to productivity - Chapter 1

Chapter 1: "What Feels Heavy?"

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

You know the feeling.

It's Sunday night, and you're mentally running through the week ahead. There's a client who needs attention. A process that's been broken for months that you keep meaning to fix. An idea for the business you haven't had time to develop. A list of things that are almost done but not quite, and another list of things you haven't even started.

You're not failing. Nobody looking at your business from the outside would say you're failing. You have clients. You're delivering. You're keeping the plates spinning.

But something is oQ. The business feels like it's moving through water. You work hard, long hours, and somehow the needle barely moves. You're always reacting, never quite building. And if you're being honest with yourself — really honest — you have a nagging sense that the problem isn't eQort. You've got plenty of that. The problem is something structural, something underneath the surface, and you can't quite see it clearly enough to fix it.

Most business owners live here. Not in crisis — in friction. Chronic, low-grade friction that compounds quietly over months and years until one day you realize you've been running hard in a direction you didn't entirely choose.

The frustrating truth is that the answers are usually already there. Not in a new tool, not in a better app, not in a consultant's slide deck. They're in the business owner's own head — buried under the noise, the urgency, the daily fires. The map exists. It just needs to be drawn out.

That's the conversation this series is about.

Before the Meeting

Rob Broadhead has a rule he doesn't advertise.

When he sits down with a new client for the first time, he doesn't lead with a framework. He doesn't open a deck. He doesn't hand over a questionnaire or walk through a list of deliverables. Instead, he asks one question — a question so open-ended it almost sounds lazy — and then he gets out of the way.

"What feels heavier or slower than it should right now?"

That's it. That's the whole opening.

To understand why that question works, you have to understand what Rob is actually doing in that first session. He isn't there to diagnose yet. He's there to listen for what the client already knows but hasn't had the space to say out loud. In his experience, most business owners are sitting on a detailed map of their own problems. They just haven't been handed a quiet room and someone willing to actually hear it.

This is the story of what happened when he gave that room to Marcus, the founder of Apex Systems.

The Setup

Marcus runs a boutique quality assurance and systems consulting firm. On paper, Apex Systems should be thriving. Marcus is technically sharp, deeply experienced, and genuinely good at what he does. He has active clients. He has prospects. He has a clear vision for where he wants the business to go.

What he doesn't have is time.

Or rather — he has time, but it keeps disappearing. He'll plan a week with clear priorities, and by Friday he'll look up and realize he spent most of it managing things that weren't on the list. A client's internal drama. A construction crew at the house. A crisis at his day job.

His wife Rachel's health, which has been fragile and unpredictable for months. The list of things that happened to him in any given week is long. The list of things he chose is short.

Rob and Marcus had known each other for a while before this meeting. They'd talked — about AI, about tools, about business strategy, about life. Good conversations. Useful ones. But those were peer conversations between two people thinking out loud together.

This was diQerent. This was the first formal session — structured, intentional, aimed at something specific. The kind of conversation where one person is there to help the other find what's actually going on beneath the noise.

What neither of them knew yet was exactly what they'd find.

The First Question

Rob asked it just past the ten-minute mark, after the pleasantries settled and the ground rules were set: stay high-level today, stay open-ended, resist the urge to jump to solutions.

"What feels heavier or slower than it should right now?"

Marcus didn't hesitate. And what came out wasn't a neat, organized answer. It was a dam breaking.

There was Hargrove & Associates — a client implementation project that had been grinding for months, perpetually close to the finish line but never quite crossing it. The software was ready. The data was cleaned. The go-live date was set for July 1st. But the client's internal gatekeeper kept making herself unavailable, delaying sign-oQs, sitting on problems instead of surfacing them. Marcus was burning hours just trying to get people in the same room. The project that should have wrapped months ago had become the lodestone everything else orbited around.

Then there was Meridian Financial — his day job as a contractor, which was supposed to be contained at thirty hours a week but had a way of expanding. The infrastructure work there had been a labyrinth: systems handed oQ without documentation, processes nobody fully understood, a knowledge expert who'd been pulled to other teams for months while Marcus's team was left to reverse-engineer the architecture from scratch. He'd defined coding standards where none existed. He'd refactored the same infrastructure four times because nobody upstream had done their homework. He was doing good work — but he was also doing work that shouldn't have been necessary.

And then, underneath all of that, there was Apex Systems itself — the business he was actually trying to build. The one he'd started because he saw a clear need: small and mid- sized businesses that are technically underpowered, organizationally chaotic, and don't know yet that help exists. He'd begun building an automation pipeline to streamline his own content and social media work — an hour and a half each week he was trying to compress down to fifteen minutes. He had a promising new prospect right in front of him — literally his own home contractor, running a growing business oQ scraps of paper and sheer memory — but hadn't had the bandwidth to pursue it. He could see the path. He just couldn't get to it.

Rob listened. He asked a few probing follow-up questions — "Why is the house situation killing your time specifically? What is the actual drain?" — but mostly he let Marcus keep going. The picture that assembled itself was not the picture of a failing business. It was the picture of a capable person whose bandwidth had been systematically consumed by things that didn't scale: manual coordination, undocumented systems, clients who weren't holding up their end of the contract, and a season of personal life that would have derailed anyone.

The Turn

Somewhere around the thirty-minute mark, Rob did something that a lot of consultants wouldn't do. He stopped drilling into the loudest problem on the list — the months of house construction, the disruption, the sheer accumulated weight of it — and reframed it entirely.

"The good news I heard in that," he said, "is that it sounds like that's actually sort of in the past. So it's something that hopefully will not be plaguing you moving forward. Which means if we want to make things better, we can actually look at other places instead of trying to fix that."

It was a subtle move, but an important one. The instinct in these conversations is to focus on whatever is screaming loudest. But Rob was listening for something more specific: what was within Marcus's control, and what was repeating. The construction wasn't repeating — it was winding down. But some of the other patterns were structural. The time lost to manual tasks that could be automated. The repeated explanations that should have been documentation. The clients consuming more than they were contractually entitled to. Those were the things worth digging into, because those were the things that would still be there in six months if nobody addressed them.

This is the diagnostic instinct that separates useful consulting from expensive noise. Not every problem deserves equal attention. Not every fire needs to be fought. The skill is in learning to tell the diQerence between a problem that is loud and a problem that is load- bearing — and focusing your energy on the latter.

For Marcus, the construction chaos was loud. The structural patterns underneath it were load-bearing.

And so the homework Rob gave Marcus for the week ahead was precise and deliberately narrow:

"Come back next week and tell me one thing you're doing more than you should."

Not a full audit. Not a to-do list. Not a strategic plan with color-coded priorities. Just: pay attention for one week, and find the thing that keeps happening that shouldn't have to keep happening. That was the thread they'd pull.

What This Is Really About

After the formal portion of the session ended, the call shifted — easier, unhurried, the way conversations go when the work is done and two people actually like each other. They talked about Rachel's recovery. About how the house was finally starting to come together after months of chaos. Marcus spoke frankly about his own mental health, the kind of honesty that doesn't come easily but clearly needed an outlet. Life had been a lot lately. He said so plainly.

That part of the conversation won't show up in most consulting engagements. It doesn't fit in a deliverable or a scope of work. But it's not incidental to what Rob does — it's central to it.

Because the reason most business consulting fails isn't a bad methodology or the wrong software. It's that the consultant never truly understands the human carrying the business. They map the org chart and miss the person. They audit the workflow and ignore what's draining the person running it. They arrive with answers before they've genuinely heard the questions.

The business and the person running it are not separate things. You cannot fix one without understanding the other.

Rob's first session with Marcus produced no report. No roadmap. No action plan. Just a question asked well, an honest answer given, and one specific thing to look for in the week ahead.

Next Week

Marcus heads into the week with one assignment: find the thing he's doing more than he should.

Rob suspects he already knows what it is. But that's not the point. The point is that Marcus needs to see it himself — to name it, to own it, to bring it back into the room as something that can be examined and changed rather than just absorbed and endured.

That's where the real work begins.

[Subscribe to follow this series] • [LinkedIn] • [Learn more about RB Consulting]