What It Actually Takes to Build a Consulting Business While Job Searching

Status: Drafting

Pillar: ⚙️ Operations & Systems

Target Audience: Managers frustrated with their teams, HR and ops professionals, founders building their first team

Hook: Accountability requires infrastructure. Most leaders are solving the wrong problem.

CTA: Discovery call — soft invite to work with GRIC

Publish Date: July 16, 2026

Let me tell you about a manager I've seen a hundred times over.

They're good at their job. They care about their team. And they are exhausted — because no matter how many conversations they have, no matter how many performance reviews they sit through, the same problems keep showing up.

Deadlines missed. Handoffs dropped. Tasks falling into the void between departments, with everyone assuming someone else picked it up.

So the manager does what most managers do: they start questioning the people.

Maybe this person isn't detail-oriented enough. Maybe that person needs more coaching. Maybe we hired wrong.

And sometimes — sometimes — that's true. But more often than not? The people are fine. The process is the problem.

A people problem looks like this: someone consistently underperforms even when they have clear expectations, the right tools, and genuine support. You've invested in them. You've had the conversations. It's still not working.

A process problem looks like this: multiple people, across different roles and different personalities, are struggling with the same thing. Missed handoffs. Confusion about who owns what. Work duplicated in one area and completely skipped in another.

If it's happening to one person, look at the person.

If it's happening to everyone, look at the system.

It's not just the missed deadline or the dropped ball. It's the time your team spends trying to compensate for the lack of structure — the DMs asking "wait, who's handling this?", the meetings that exist because nobody documented the process, the manager who becomes the human routing system because there's no workflow that does it instead.

That's not a performance issue. That's a design issue.

And here's the part that stings a little: when there's no clear process, the most conscientious people on your team will overextend themselves trying to fill the gaps. They'll carry more than they should, communicate more than they should, check and double-check because the system doesn't make it obvious. And eventually, they burn out — not because they aren't capable, but because the infrastructure was never built to support them.

That's a retention problem in slow motion.

Before your next performance conversation, ask yourself a few honest questions:

Does this person know exactly what's expected of them — not just in their job description, but for this task, this week, this handoff?

Is there a documented process they're supposed to follow, or are they improvising based on what they think you want?

When something goes wrong, do multiple people point to the same gap? Or is it consistently one person?

If the answer to those first two questions is "not really" — start there. Before the coaching conversation. Before the PIP (Performance Improvement Plan — a formal document outlining specific goals and timelines to help an employee meet expectations). Before you decide it's a people problem.

You don't need a sophisticated system to start. You need documented expectations, clear ownership, and a way for people to know when something's on them versus when it's been handed off.

That's it. A RACI (a chart that clarifies who's Responsible, Accountable, Consulted, and Informed for each task). A simple SOP (Standard Operating Procedure — a documented step-by-step guide for how a task gets done). A checklist that lives somewhere everyone can find it.

When the infrastructure exists, accountability becomes possible. Because you can't hold someone accountable to a process that was never written down.

Your team wants to do good work. Most people do. And when they're not delivering, the most generous — and often most accurate — assumption is that something in the environment isn't set up to help them succeed.

Start there. Build the process first. Then see what's left.