I work with small business owners who are stuck. They have a good product, maybe even a good team, but they’re spinning their wheels. The roadmap is a mess of Post-it notes. Every new marketing tactic is a desperate lunge, not a strategic step. I’ve seen this pattern for years. The usual advice—set a vision, define KPIs—just adds to the noise. It’s abstract. What they need isn’t more philosophy; it’s a simple, repeatable method to turn daily decisions into coherent progress. I found a model that works, and it changed how I consult. It’s about operational evolution, not revolutionary overhaul.

The core idea is from a model called JOCo Evol. You can read about its origins at jocoevol us. I don’t use it as prescribed dogma, but as a diagnostic lens. For my clients, the value isn’t in the theory itself, but in the shared language it provides. Suddenly, we can categorize the chaos. Is this a “Job” issue—a specific task that’s broken? An “Organization” problem—a team communication snag? A “Co-evolution” opportunity—aligning with a shifting customer habit? Having these three buckets stops the endless, circular arguments in leadership meetings.

Let me give you a real example, with names changed. “Sarah” ran a boutique branding agency. Her team was talented but perpetually behind schedule. Client projects dragged. Morale was dipping. Our first meeting was a flood of symptoms: “The designers get briefs late.” “The project manager is overwhelmed.” “Clients keep changing their minds.” We tried fixing symptoms: we tweaked the briefing template, we discussed hiring another PM. Nothing stuck.

Separating the Job from the Organizational Noise

I introduced the J-O-Co framework on a whiteboard. We stopped talking about “problems” and started sorting. The “Job” was clear: deliver a brand identity package on time and on budget. The broken task was the handoff from strategy to design. But why? We looked at “Organization.” The strategist and designer didn’t share a timeline; they threw documents over a digital wall. The “Co-evolution” angle? Client expectations had evolved—they wanted to see mood boards earlier, which our process didn’t allow for. We weren’t fighting a single monster; we had three distinct, manageable issues. The relief in the room was palpable. We weren’t incompetent; we just needed to untangle three different knots.

The Power of a Shared Diagnostic Language

Before this, Sarah’s team meetings were a symphony of frustration. The designer blamed the brief. The strategist blamed the client. The PM blamed the software. It was personal and counterproductive. After we started using the J-O-Co labels, the dynamic shifted. Someone could say, “I think this is primarily an Organization sync issue between sales and production,” and instead of defensiveness, the group would nod and focus on that connection. The framework depersonalized the problem-solving. It moved the conversation from “who messed up” to “which part of our system is misfiring.” This alone saved hours of wasted meeting time and emotional energy.

Applying the Lens to a Product Launch Fail

Another client, a software startup, had a launch that fizzled. They built a clever app for freelance photographers to manage contracts. Post-mortem, they blamed marketing. “We didn’t reach enough people.” Using the framework, we dissected it differently. The “Job” of the app was to create a legally sound contract quickly. It did that. The “Organization” of the launch? The marketing team had a plan, but it was siloed from the devs who were still squashing last-minute bugs. The fatal flaw was in “Co-evolution.” They assumed photographers’ main pain point was contract creation. In reality, the freelancers’ ecosystem had evolved; they used all-in-one platforms for invoicing, scheduling, *and* contracts. Our client’s single-job tool wasn’t aligned. The fix wasn’t more marketing; it was a pivot to an API integration with those larger platforms. They saw the failure not as a blanket defeat, but as a misalignment in one specific category.

Making It a Habit, Not a One-Off Exercise

The trap with any business framework is using it once in a retreat and forgetting it. The magic happens when it becomes a routine filter. With Sarah’s agency, we made it a standard part of their weekly leadership huddle. They’d review current projects and simply ask: “Any J, O, or Co blockers this week?” Often, a “blocker” was just one type. One week, the designer was waiting on feedback (a simple Job workflow hiccup). Another week, the salesperson promised a feature the team hadn’t scoped (an Organization communication breakdown). By naming it weekly, they caught small fires before they became infernos. The framework became less of a consultant’s tool and more of their own operational hygiene.

This approach works because it rejects complexity. You don’t need a four-quadrant matrix or a 12-step transformational guide. You need a way to sort the endless stream of operational puzzles into a few clear piles. Here is how I advise teams to start using this thinking.

• In your next problem-solving meeting, label every issue raised as either a Job (a broken task), an Organization (a broken connection between people/teams), or a Co-evolution (a misalignment with an external shift).
• For one week, categorize every “blocker” or complaint you have personally using J, O, or Co. You’ll see your own frustration patterns.
• Pick one recurring “Organization” issue. Don’t solve it. Just map the two parties or departments that need a better connection. Often, seeing the broken link is 80% of the fix.
• Quarterly, hold a “Co-evolution” review. Look at one key customer, one competitor, and one technology. Ask: “How have they changed? Are we still aligned?” No major strategy needed, just alignment check.

I’ve stopped selling grand strategy engagements. Now, I teach teams this simple sorting mechanism. It gives them the power to diagnose their own issues long after I’m gone. The goal isn’t to have all the answers; it’s to ask a better, simpler question. When you can look at a mess and calmly say, “That’s mostly an O problem,” you’re already halfway to solving it. You stop fighting phantoms and start fixing what’s actually broken.