Most organisations carry a version of the truth they have collectively agreed not to examine too closely. The strategy is fine. The culture is good. The processes work well enough. And then something breaks - a key person leaves, a competitor moves, a customer stops renewing - and the agreed version turns out to have been a story.
That is not a failure of data. It is a failure to ask the right question. The information was there. Nobody structured the question well enough to surface it.
Reveal is a fixed set of questions, not a report and not a scorecard. It takes a domain - a business, a team, a go-to-market function, a leadership group - and applies the same rigour every time, designed not to confirm what you already believe, but to surface what you have been unable to see. The output is not a report. It is a reading - precise, evidence-based, of where you actually are.
This is not a diagnostic. Not an audit. Not a scorecard with better graphics.
The thinking underneath is different.
Not a Framework. A Forcing Function.
Scorecards measure against criteria you chose in advance. Which means they confirm the things you already thought mattered, and miss the things you did not know to ask. Reveal is built the other way around: the framework comes first, and it is designed to surface what most familiar tools are built to avoid - the uncomfortable gaps between what leadership believes and what the evidence shows.
The questions are fixed. The scoring is calibrated. The output is comparable across time, across teams, across organisations. Not because standardisation is the goal, but because without it, you are not reading the situation - you are having a conversation.
Conversations are useful. Reveal is different. It is the structured foundation that makes the conversation mean something.
Reveal maps five dimensions of organisational readiness: clarity of purpose, quality of execution, strength of relationships, capacity for change, and coherence between what you say and what you do. Each dimension is probed through structured questions. Each response is scored. The aggregate produces a picture - broken, patchy, or strong - that reflects reality rather than aspiration.
The value is not the score. The value is what the score forces you to look at. Most leadership teams already sense where the weaknesses are. Reveal makes it impossible to look away.
And because the framework is consistent, a reading taken today can be compared to one taken in six months. Progress becomes measurable. Regression becomes visible. Reveal compounds - not into a fixed picture, but into a moving one. That is when it starts to function less like an audit and more like a navigation system.
The same questions work in two directions. Turned inward, they show an organisation where it is weak, on its own terms. Turned outward, they are how you meet a visitor on theirs. Someone arrives believing they have problem A, B, or C. Reveal does not argue with that. It shows them the real driver is Z, and that Z connects to something they had not seen before. Not "we sell you an XYZ." Solving the problem they actually have, in their language, using their evidence.
You do not need a new strategy to fix this. You need to see clearly what you are working with.
It gets richer still when different people across the same team complete it. Now you are not just comparing today to six months from now. You are comparing perspective to perspective, in the same moment.
That is Reveal.
The Icon
The Reveal Icon
Layered planes, each partially obscuring the one beneath. The top layer is clear. The ones below are progressively harder to read - until the diagnostic cuts through and the full picture emerges. The icon does not show a result. It shows the moment before clarity - and the structure that produces it.
Injections
Every domain is built from elements: pieces of working functionality, like a form that fills a database, a report, an alert, or a discussion.
An injection takes one of those elements out of its home domain and drops it into another, applied to a different problem. You get the working part, not the whole product, and you get it quickly.
Reveal's core element is the form that fills a database: a fixed set of questions, scored the same way every time.
Navigation already reuses it, applied differently: questions that find the real problem and point you to the right place.
The five questions you meet on arriving at philpin.com are exactly that. A Reveal injection.