Understanding Allison Essence Of Decision
I ran into this myself when a team lead asked me to help them structure a procurement review. The method sounded straightforward on paper but turned out to be messier in practice. Here is what I figured out after working through it a few times. The core idea is to strip a decision down to its essential components before letting stakeholders pile on criteria, timelines, and budget concerns. It starts with writing a single sentence that captures what is actually being decided. Not the context around it. Not the desired outcome. Just the decision itself. Once you have that sentence, you map out the factors that would make one option clearly better than another. This is where most people get it wrong. They list every possible consideration they can think of instead of identifying only the ones that would actually change the choice. I once spent three weeks un-doing a session where someone had listed forty-seven "factors" for a vendor selection that really hinged on two things: delivery timeline and total cost over three years. Narrowing it down took us about twenty minutes.
How to apply it
Step one: write the decision statement
Keep it to one line. Avoid including the answer you already want. A bad example is "we should switch to Vendor B because they are cheaper." A correct version is "which vendor should we select for the Q3 contract renewal." These are the attributes that, if they differed significantly between options, would actually flip your choice. Write each one as a measurable or observable property. If you cannot picture how you would verify it, it is not a decisive criterion. It is a preference. Preferences belong somewhere else in the process. Rate each option against each criterion on a simple scale. Then look for the option that wins on the criteria that matter most. Do not weight them unless you genuinely need to. Most decisions do not require weighted scoring to produce a clear answer.
This is where I hit a real problem once. We were evaluating two software platforms using this method and both scored nearly identical on the top criteria. The deciding factor ended up being something we had not listed at all: how difficult it would be to migrate our existing data without downtime. That was a hidden constraint. The workaround I use now is to add a short "what could break this?" question before finalizing the criteria list. It catches things like regulatory dependencies, integration bottlenecks, and internal capacity limits that usually show up right when you commit to a direction. The biggest issue I see is people treating Essence Of Decision as a pure analysis tool when it is actually a conversation management tool. It does not produce the right answer by itself. It prevents the discussion from becoming so wide that no one can act. If you use it without actually making a choice at the end, you have just added paperwork to the process. Another problem is scope drift. Someone will start with a clean decision sentence and then quietly expand it mid-process to cover related questions. "Should we buy this tool?" becomes "Should we buy this tool and also restructure the team that uses it?" Once that happens, the method stops working. The criteria multiply and nothing gets decided. You have to call it out and split the problem into two separate decision sessions.
Get the Full Details
When it does not work
This approach breaks down when the decision is truly value-laden rather than informational. If you are choosing between two options that both meet your hard requirements and the difference comes down to taste, culture fit, or leadership philosophy, running through criteria scores will not give you clarity. It will just give you a false sense of precision. In those cases, the more useful step is to define what success looks like after the decision is made and work backward from there. It also does not help when there is insufficient information. I watched a team try to use it to pick a cloud provider before they had even scoped their storage requirements. The exercise produced confident-looking charts built on guesses. The fix was to insert a discovery phase first. Get the facts. Then run the method.
Bottom line
Allison Essence Of Decision is not a framework that guarantees good outcomes. It is a discipline for stopping the noise so you can actually hear what the decision is. Use it when the problem is clear but the conversation is not. Skip it when the problem itself is unclear or when the outcome depends on something you cannot measure. Those are the situations I have found where it adds more friction than value.
