How The Kimberly Scarborough Model Actually Works When You Need It
I ran into this model about three years ago during a crisis simulation that involved a client deciding whether to fold a product line under regulatory pressure. The model itself is straightforward on paper but the way it structures decision trees and stakeholder mapping makes it genuinely useful when you have real money on the table and the clock is running. Here is the basic breakdown of how it functions in practice. The core mechanic is a four-layer filter system. First, you identify the constraint layer, which is usually something obvious like budget or a regulatory deadline. Then you move to the actor layer, where you map every party with leverage, not just the ones at the table. The signal layer separates noise from actual data points, and finally the outcome layer forces you to model at least three distinct end states before you commit to anything. Most people skip the actor layer and go straight to mapping outcomes. That is where things fall apart. I learned this the hard way on a merger negotiation where the opposing counsel had apparently forgotten that a mid-level compliance officer on the other side could block the entire deal. By the time we realized it, we had already invested two weeks of prep. The model would have caught that if we had been disciplined about it.
Here is a practical workflow I use now: Step 1: Constraint capture. Write down every hard limit in plain language. No jargon. If you cannot explain it to a junior analyst in one sentence, you do not understand the constraint yet. This usually takes ten to fifteen minutes. Step 2: Actor mapping. Draw a list of every person or group affected. Include people who can veto without being obvious about it. Regulatory bodies, internal compliance teams, even vendors whose contracts have change-of-control clauses. I keep this updated throughout the process because new actors always surface.
Step 3: Signal extraction. Take your information set and label each point as primary (documented, verifiable) or secondary (hearsay, inference). The model only counts primary signals as valid inputs. Everything else gets a warning flag. This cut my research time by about forty percent on the last engagement I worked on because it forced me to stop chasing ghost data. Step 4: Outcome modeling. Build three scenarios minimum. Optimistic, baseline, and worst case. Each one needs a concrete probability estimate, not just a gut feeling. I use a simple weighted scoring method where each scenario gets rated against constraints and actor influence. This step usually takes about an hour for a medium-complexity situation. One counter-intuitive thing about this model that people miss: the signal layer is actually the hardest part. We tend to treat every piece of information as equally weighted, but in high-stakes environments, bad data does more damage than no data. I once spent three days building a strategy on a regulatory filing that turned out to be a draft version. The model would have flagged that immediately if I had enforced the primary-only rule from the start.
Get the Full Details
Another nuance beginners overlook is the actor mapping. You will always underestimate the influence of people who do not look like they have power. In my experience, about sixty percent of the obstacles that blow up strategies come from overlooked actors, not from the obvious decision-makers. Building in time to interview mid-level operators before you finalize your plan pays for itself. There are limitations worth noting. The model requires a certain amount of upfront discipline and documentation that slows you down in the initial phase. If you are working on something with a tight timeline, say under forty-eight hours, the full application of this model might not be feasible. In those cases, I compress the actor and signal layers into a rapid brainstorm rather than a formal exercise. You lose some rigor but you still get the structure. Another scenario where this breaks down is when the environment is highly volatile and the constraints shift faster than you can document them. I ran into this with a tech client during a market correction where the regulatory landscape changed weekly. The model assumes a relatively stable information set, and when that assumption falls apart, the whole framework becomes a paper exercise. For those situations, I switch to a rolling three-day review cycle instead of the full model application.
If you want to start using this approach, there is a basic template available online. It is not affiliated with Scarborough directly but it follows the documented structure accurately enough for practical work. Look for the PDF version if you want something you can print out, though the digital fillable format works fine too. The key is actually doing the work in the signal layer, which most people rush through. The model has become part of my standard toolkit for anything involving strategic decisions under pressure. It does not guarantee a good outcome, and it does not replace judgment, but it does force you to be honest about what you know and what you are guessing at. That honesty alone is worth the effort it takes to apply it properly.
