Locate. Name. Replace: The Jewels Framework for Operational Diagnostic
By James Pemberton
Every broken business pipeline has a starting point. Whether the problem is high caregiver turnover in a healthcare agency, missed bookings for a local service company, or direct-response funnels that run dry, the symptom is rarely the root.
In our work building custom operational setups, we use a diagnostic approach called the Jewels Framework. It relies on a three-step cycle to fix systemic bottlenecks: Locate, Name, and Replace.
1. Locate the Word (or Input)
Every broken structure is caused by an unintended input. In direct response copy, recruitment scripts, or workflow configurations, this is often a literal word or setting that creates the wrong pattern.
For example, when a staffing agency describes their intake as an "autonomous scheduling queue," they unconsciously build a system where recruiters wait for candidates to act. By locating that single word—autonomous—we realize the system has been trained to be passive.
The first step of the framework is to trace the flow backward from the pain point until you find the exact input that encoded it.
2. Name What It Produces
Once the unintended input is located, you must measure its real downstream cost. This is not about general industry averages or generic metrics. It is about naming the exact operational friction:
- Turnover: How many hires are lost in the first 60 days because of passive credentialing?
- Burnout: How many hours does your clinical director spend manually checking registries because there is no automated verification?
- Leakage: What percentage of inbound leads go cold because your system's response latency is hours instead of minutes?
The moment you name the exact cost, the case for changing the system becomes undeniable.
3. Replace It
The final step is installing the replacement structure. This is where the precision model takes over. You swap passive routing for active engagement, manual tracking for automated triggers, and vague metrics for direct-attribution data.
A successful replacement doesn't add complexity. It simplifies the operational loops so that your team only shows up for the high-value conversations that matter.
The Diagnostic Rule: The value of the diagnostic is finding the truth, regardless of the answer. If the system is broken, name the input and build the machine that makes the next right action obvious.