Insights · September 6, 2026 · 3 min
Break the Problem Down Until You Can Fix It
Large operational problems often become manageable when separated into specific processes.
"Everything feels hard" is a real feeling. It is a poor unit of work.
When owners say operations need to improve, they often mean a cluster of frictions that have fused into one story: late jobs, missing information, status chasing, invoices that wait, schedules that live in one person's head. Treated as one object, that story is too large to finish. Accountability softens. The week stays the same while the conversation stays ambitious.
The practical move is to break the large operational problem into specific processes with edges. Quote-to-schedule. Intake-to-job. Job-to-invoice. How a request becomes a booked day. How completed work becomes a billable invoice. Each of those is something you can follow, name, and change. "Operations" is not.
The goal of breaking the problem down is a right-sized—Cotomic—process unit you can actually work on. The work is getting there from the fused mess.
Edges matter because they separate what was stuck together. A process with a start and an end lets you watch a real job move through it. You can see the side spreadsheet, the re-email, the "just call me" loop that exists because the main workflow does not. Without edges, every fix bleeds into every other fix, and you cannot tell which change did what.
In a service business, "we need better systems" often hides three different processes. Intake loses a field. Scheduling depends on a private spreadsheet. Invoicing waits on a code that never entered the tracker. Those feel like one mess because they collide every Tuesday. They are still separate processes. Separate them, and each becomes fixable. Leave them fused, and the remedy tends to arrive as a platform purchase before anyone has named the cause.
That premature leap is common. Paul Nutt studied 356 organizational decisions and found that roughly half failed by sustained-use criteria. Failures often traced to managers who imposed a solution early, limited search, and tried to push the plan through. Setting clear desired results before locking the fix was associated with better sustained use. Breaking the problem down is how you get those clear results: not "modernize operations," but "quotes no longer sit three days waiting for a code."
Visible friction points you to where to investigate. It does not automatically tell you the cause. Write the gap you can count before you pick a remedy. Then choose the process unit that owns that gap.
You do not break problems down to make them sound smaller than they are. You break them down so a broad, messy operational story becomes separate processes with edges—units you can finish changing one at a time.