Best on desktop or laptop — but you can run a diagnostic from here too
The Premis™ Brief
Most failed initiatives were working on the wrong problem. Are you solving the right one?
Clear diagnosis. Transparent reasoning. Honest about its limits.
Try:
A few things that sharpen the read
Reading your input...
What's your read on what's causing this?
How long has this been the case?
Is there a decision you need to make because of this?
1
Research
~40s
2
Classify
~15s
3
Hypothesize
~15s
4
Test Design
~60s
Reading the problem
Diagnosing:
01Classify: What kind of problem, and what decision actually needs to be made
⚠ Analysis operating without
The following was absent from the input and may affect diagnostic reliability:
02Hypothesize: What's most likely broken, and what would change that view
03Interrogate: The issue tree, built to test the diagnosis
04Design the Test: What to prove and how to prove it
Premis frames. You decide.
When to use it
When everyone in the room disagrees on what's actually broken, and the cost of misdiagnosing it is months of executive time lost in revisiting problems.These are "wicked problems" — Rittel & Webber, Dilemmas in a General Theory of Planning, Policy Sciences, 1973.
Leave with a diagnosis you can act on
Most problems get solved at the symptom level. Premis identifies the root cause — and shows the alternatives it weighed. *Deep Research mode adds ~2 min.
Know how the conclusion was reached
A diagnosis you can't question is just an opinion. Every step of the reasoning is visible and traceable.
Uncover what's missing
The gaps in your input are named explicitly so you know what the analysis is working without, before you act on it.
Walk in with a report worth presenting
The full diagnostic downloads as a structured report. Ready to share, present, or build on.