Operations Consulting
Operating Premise
Growth shouldn't require the founder to become the routing system for the entire company.
Growth has a funny way of exposing every process nobody documented, every handoff nobody owns, every exception nobody planned for, and every decision that somehow still needs the founder. We figure out why the business keeps fighting itself — then fix the operating structure underneath it.
Operational Traffic · Current State
When everything keeps rolling uphill
Incoming Work
Team
“Can you approve this?”
Client
“Who actually owns this?”
Process
“What do we do when this happens?”
Systems
“The CRM doesn't match reality.”
Exception
“This one's weird. Ask the founder.”
Default Routing Point
The Founder
Approval engine. Exception handler. Human search bar. Final answer.
What That Creates
Slow Decisions
Work waits for somebody at the top.
Fragile Execution
The business works differently depending on who's online.
Founder Exhaustion
Growth creates more decisions instead of more leverage.
The Real Problem
The founder became the operating system because the actual operating system never got built.
What Better Starts to Look Like
Work gets routed by structure, not telepathy
01
Clear Ownership
02
Defined Decisions
03
Usable Process
04
Supporting Systems
Ownership · Workflow · Decisions · Systems · Execution
A business that makes sense without founder telepathy.
What Operational Problems Look Like
Usually it shows up as missed work, frustrated employees, annoyed clients, constant interruptions, or another meeting about why something still didn't happen. The symptoms look different. The operating conditions underneath them are usually much more connected than they seem.
Above the Surface · What You Notice
Symptoms are evidence — not diagnoses
01
Founder Dependency
You hired people so you could stop being involved in everything. Instead, you're still approving exceptions, answering questions, solving weird edge cases, and becoming the default answer whenever nobody knows what happens next.
We Start Tracing
Decision rights · ownership · escalation
02
Ownership
Plenty of people are working. That's not the same as clear ownership. Responsibilities overlap, work bounces between people, and something sits untouched because everyone reasonably thought somebody else had it.
We Start Tracing
Roles · handoffs · accountability
03
Process
The process works because one experienced employee knows the exceptions, shortcuts, context, and unofficial rules. When they're unavailable, everyone suddenly discovers the documentation was mostly wishful thinking.
We Start Tracing
Knowledge · workflow · exceptions
04
Handoffs
Sales thinks delivery has it. Delivery thinks onboarding owns it. Customer Success assumes somebody already followed up. The client doesn't care whose fault it was — they just know nobody called them.
We Start Tracing
Transition · context · next action
05
Systems
The CRM says one thing, Slack says another, somebody has a spreadsheet, and the actual truth lives in a conversation from last Thursday. Technology was supposed to create visibility — not an archaeological dig.
We Start Tracing
Data · workflow · system ownership
06
Execution
Everyone agrees something needs to change. Then the meeting ends, normal work takes over, ownership gets fuzzy, and two weeks later you're discussing why the same damn thing is still happening.
We Start Tracing
Ownership · priority · follow-through
↓ This Is Where Diagnosis Actually Starts ↓
Below the Surface
01
Decision Rights
Who is actually allowed to decide without sending everything uphill?
02
Ownership
Is responsibility genuinely clear, or just assumed?
03
Workflow
How does work actually move when the day isn't perfect?
04
Handoffs
What information, ownership, or next action disappears between people?
05
Systems
Do the tools reflect the real operation or an imaginary cleaner version of it?
06
Follow-Through
What turns an agreed decision into work that actually gets finished?
The Question I'm Asking
“Why does this keep happening — and what in the operation keeps making it possible?”
Diagnose Before Prescribing
Fix what keeps creating the problem, not just whatever broke today.
What We Actually Fix
Ownership, workflow, handoffs, documentation, systems, execution, and capacity all affect each other. A problem can surface in one layer while being created somewhere else. So we don't start by choosing a service. We figure out which part of the operation actually needs attention.
01
Authority
Clarify who owns the work, who makes the decision, who gets consulted, and what genuinely requires the founder. “The team handles it” isn't an operating model.
We Need to Know
Who owns the outcome when something doesn't go according to plan?
02
Flow
Follow work from trigger to completion and remove unnecessary steps, duplicated effort, bottlenecks, dead ends, and those weird workarounds everyone forgot were supposed to be temporary.
We Need to Know
How does the work really move when the day isn't perfect?
03
Transition
Define what survives when work changes hands: ownership, context, expectations, deadlines, and the next action. A good handoff makes responsibility visible before the ball hits the floor.
We Need to Know
What disappears every time responsibility moves?
04
Knowledge
Pull critical operating knowledge out of people's heads and turn it into documentation the team can actually use. Not a 47-page SOP written solely so everyone can say an SOP exists.
We Need to Know
What stops working when the person who “just knows” isn't available?
05
Infrastructure
Make technology support the operation instead of forcing the company to work around its software. That can mean cleanup, redesign, automation, integrations, better visibility — or occasionally admitting a tool actually needs to go.
We Need to Know
Does the system reflect reality, or force people to fake the process?
06
Movement
Look at how decisions become action: priorities, meetings, follow-up, accountability, communication, and the rhythm used to move work forward. A decision nobody executes is just a conversation.
We Need to Know
What turns “we should do this” into something that actually gets finished?
07
Capacity
Determine whether the team actually needs more capacity, a different division of responsibility, or simply a better way of using the people already there. Hiring isn't automatically an operations strategy.
We Need to Know
Is the problem really workload — or is broken work creating fake capacity needs?
Why the Layers Matter
A systems problem may actually be a workflow problem. A capacity problem may be duplicated work. A people problem may be unclear decision rights. A handoff problem may really be missing ownership. That's why diagnosis comes before the solution.
Intervention Logic
Touch only what actually needs changing
01
Find the friction
02
Trace the cause
03
Change the right layer
04
Leave the rest alone
Jeremy's Rule
“I don't change something just so I can say I changed it. If it already works, leave the damn thing alone.”
Smallest Useful Intervention
Fix enough to solve the problem. No transformation theater required.
The Operator Lens
The thing everybody is complaining about might absolutely be a problem. It just might not be the problem. So instead of immediately changing something, we reconstruct what happened, compare it with what was supposed to happen, and find the gap that made the failure possible.
Operational Incident Reconstruction
Diagnosis In Progress
Reported Incident
A new client finished onboarding. Nobody followed up.
Reconstruct the Sequence
Compare intended workflow with what actually happened.
Expected
What the company believes should happen.
01 · Trigger
Onboarding complete
02 · Ownership
Account owner assigned
03 · System
Follow-up created
04 · Outcome
Client contacted
Actual
What really happened on Tuesday.
01 · Trigger
Onboarding complete
02 · Handoff
“I thought Sarah had it.”
03 · System
No task existed
04 · Outcome
Client chased company
What We Know So Far
The employee didn't simply “forget.” Ownership and the workflow diverged before the follow-up ever had a chance to happen.
Now We Test the Conditions
Any one of these could be contributing. Several might be interacting. We test before deciding what deserves to change.
01
Ownership
Was somebody clearly responsible for the account after onboarding?
02
Process
Was there a defined step that should have created the follow-up?
03
System
Could the CRM support the workflow — and was it configured to?
04
Human Behavior
Did the responsible person know the expectation and have capacity to execute it?
Before We Change Anything
Only then do we decide whether the answer is clearer ownership, a different handoff, better documentation, a CRM change, automation, additional capacity, management follow-through, or something else entirely. Change needs evidence.
01
Don't assume it's a people problem.
Good employees can look terrible inside unclear ownership, broken workflow, and conflicting expectations.
02
Don't rebuild what already works.
Existing processes and systems earn the right to stay when they're doing their job.
03
Don't automate confusion.
Make the workflow make sense manually. Then use technology to support something worth scaling.
Reconstruct · Test · Understand · Change
Fix the operating condition — not just today's incident.
What Better Looks Like
Operational improvement shouldn't only show up in an org chart, process map, or consultant's presentation. You should be able to feel the difference on a completely ordinary workday. Same people. Same customers. Same business. The work simply makes more sense.
Before
The business fights itself.
Tuesday
After
The operation makes sense.
Ownership
A routine exception immediately rolls uphill because nobody is quite sure where their authority begins or ends.
08:42 AM
Ownership
Responsibility, authority, and escalation paths are clear enough that normal decisions stay where the work actually lives.
Handoff
Work changed hands through assumptions, messages, memory, and whatever somebody happened to say in the last meeting.
10:06 AM
Handoff
Responsibility, context, information, and the next action are visible before the work leaves somebody's hands.
Process
The real process lives inside one experienced employee's memory, including every exception nobody bothered documenting.
11:47 AM
Process
Important knowledge is accessible enough that execution doesn't disappear when the person who “just knows” isn't available.
Systems
Somebody has a spreadsheet. Somebody else has notes. The official system stopped reflecting reality three months ago.
01:31 PM
Systems
The tools support the real workflow, information lives where the team expects it, and leadership can trust what they're seeing.
Execution
Everyone agreed what needed to happen. Somehow ownership disappeared between the conversation and the actual work.
03:08 PM
Execution
Owners, priorities, next actions, and follow-up are clear enough that progress doesn't depend on somebody remembering the meeting.
Leadership
Visibility means opening Slack, checking spreadsheets, calling people, and piecing together five versions of the truth.
04:36 PM
Leadership
Useful visibility comes from the operation itself instead of leadership becoming the company's human status-reporting system.
The Tuesday Test
Fewer unnecessary approvals. Cleaner handoffs. Less knowledge trapped inside people's heads. Systems people trust. Decisions that turn into action. Leadership that can see the business without interrogating it. That's operational improvement you can actually feel.
01
Ownership
Decisions live closer to the work.
02
Flow
Work moves without unnecessary friction.
03
Visibility
The operation can explain itself.
04
Resilience
Weird days don't automatically become emergencies.
The Actual Goal
Businesses will always have strange situations, difficult days, unexpected problems, and questions nobody planned for. Good operations don't eliminate reality. They make the company much better at dealing with reality without turning every problem into a fire drill.
The Swink Group · Operations Consulting
Build for the random Tuesday. Not the perfect Monday.
How We Can Work Together
I'm not going to pretend every company needs the same twelve-week transformation package. Sometimes the right answer is a focused set of experienced eyes. Sometimes the work needs to be rebuilt. Sometimes leadership needs another operator nearby as the company grows. The scope gets larger only when the problem gives us a reason.
Scope Principle
Start with the smallest useful intervention. Let deeper work earn its way in.
Narrower Scope
Broader Involvement
Understand
Defined Diagnosis
Define
Focused Correction
Design
Working Operation
Stay Close
Ongoing Judgment
No Forced Packages
I am perfectly comfortable telling you the useful answer is one clearer responsibility, one workflow change, one system correction, or one decision you've been avoiding. If what we uncover genuinely requires deeper work, we'll talk about that too. The scope should earn its way into the engagement. It shouldn't exist because somebody needed another line item on a proposal.
You Don't Need to Choose One
Start with what you actually know
01
“I know something is wrong, but I can't tell you what.”
That's enough to start.
02
“This one part of the business keeps driving everybody nuts.”
Bring me that.
03
“We already know what needs to happen. Nobody has actually built it.”
We can look at implementation.
04
“I just need another experienced operator to think through this stuff with me.”
That's what advisory is for.
No package-selection homework required. Tell me what's happening inside the business.
Diagnose · Solve · Build · Advise
The engagement gets bigger only when the problem earns it.
Jeremy's Rules for Operations
These aren't commandments, and I'm not pretending I invented operations. They're lessons learned from watching good businesses make the same avoidable mistakes over and over again. Simple rules tend to survive reality better than complicated frameworks.
Operational Guardrails · Field Standard
Keep the business from creating its own friction
01
Ownership
Shared responsibility sounds collaborative right up until something gets missed. Every important outcome needs a clear owner. Other people can contribute. Somebody still has to have the ball.
This Protects
Accountability
Prevents responsibility from disappearing inside collaboration.
02
Automation
Automation does not create clarity. It multiplies whatever you give it. If the manual process is confusing, inconsistent, or broken, automating it just lets the confusion happen faster.
This Protects
Process Clarity
Prevents technology from scaling nonsense.
03
Documentation
Documentation exists to help somebody do the work. If employees need a search party, a philosophy degree, and twenty uninterrupted minutes just to find the next step, we missed the point.
This Protects
Usability
Prevents documentation from becoming ceremonial paperwork.
04
Capacity
Sometimes you genuinely need more capacity. Great. But headcount should not become the default solution to unclear ownership, poor workflows, weak onboarding, or work nobody has bothered to structure.
This Protects
Capacity
Prevents structural problems from disguising themselves as hiring needs.
05
People
People absolutely make mistakes. They also work inside the systems, expectations, tools, training, priorities, and decisions leadership gives them. Before calling someone the problem, make sure the business didn't set them up to fail.
This Protects
Fair Diagnosis
Prevents system failures from being mislabeled as people failures.
06
Restraint
Consultants sometimes feel obligated to change things because they were hired to change things. I don't. If a process is simple, understood, reliable, and doing its job, it has earned the right to survive the consulting engagement.
This Protects
What Already Works
Prevents consulting from becoming a source of unnecessary disruption.
The General Philosophy
The goal isn't more process for the sake of process. It's enough structure to make ownership clear, execution repeatable, information trustworthy, and the company easier to navigate. Good operations should disappear into the way the business works — not become another layer everybody has to work around.
Before We Add Anything
Three questions the solution should survive
01
Clarity
Does this make the work easier to understand?
02
Usefulness
Will the people doing the work actually use it?
03
Necessity
Does this solve a real problem, or are we just adding process?
Ownership · Clarity · Usability · Capacity · Fairness · Restraint
Operations should help people work — not give them more shit to work around.
Let's Talk About the Mess
No Diagnosis Required
You bring what's happening. We'll figure out what it means.
That's Enough
You don't need a process map, polished explanation, consulting vocabulary, or a finished diagnosis before we talk. Tell me what keeps happening, what keeps breaking, what keeps landing back on your desk, or what your team keeps fighting with. The recurring sentence is usually a pretty damn good place to start.
Founder Dependency
“Why does everything still need me?”
A place to examine authority, escalation, ownership, workflow, and decision rights.
Ownership
“How did nobody realize this wasn't getting done?”
A reason to trace responsibility, handoffs, visibility, and follow-through.
Recurrence
“Why the hell are we having this same conversation again?”
Evidence that today's incident may be part of a larger operating pattern.
Systems
“I don't trust anything in our CRM anymore.”
A starting point for process, data, workflow, adoption, and system design.
Capacity
“Do we need another person, or are we just doing this badly?”
A reason to separate genuine workload from broken work creating fake capacity needs.
Unknown
“Something about this business just feels harder than it should.”
Completely valid. We can start there too.
What Happens Next
Maybe we find unclear ownership. Maybe it's a workflow issue. Maybe the CRM isn't supporting reality. Maybe the team lacks capacity. Maybe the founder is still holding decisions nobody else knows they're allowed to make. Maybe several things are colliding. We don't need to know before the conversation. Finding out is the point.
The First Conversation
Tell me what keeps happening inside the business. We'll talk through what you've seen, what you've already tried, and where the operation seems to keep fighting you. Then we'll decide whether The Swink Group can genuinely help.
You Can Literally Open With
“Jeremy, here's the thing in my business that's driving me nuts...”
One More Thing
“If I don't think you need me, I'll tell you. That's still a useful conversation.”
The Swink Group · Operations Consulting
Make the business easier to run.
