The Reading
Whole-System Assessment
Before a system can be measured, repaired, defended, or handed on, it has to be understood. A Reading is that understanding, set down in writing by someone from outside it. The question a Reading answers is what do we have?
When it is commissioned
A sponsor needs to know what they are holding—before they restructure it, defend it, put money into it, or hand it to someone else—and has nothing to go on but the account the system gives of itself. The situation is usually one of three.
You have inherited a system and need to know what you have.
Before you act on it, and before someone else forces the question.
Something is off and you cannot say where.
You need the picture before you can know where to look.
You must account for the system to a board, a regulator, or a legislature.
You want to answer from what's there, not from what you've been told.
What is delivered
A Reading gives you an understanding of the system you are responsible for: what it actually is, as distinct from what it is said to be, and why it behaves as it does. That includes what no one inside it can see from where they sit, and where it runs on assumptions no one has tested. It comes as a written report and a working session with you.
The report reads the system as one thing. Along the way it records what it finds, each finding located in relation to the whole and named for the kind of problem it is, so the direction of the fix is clear. It is a flight over the territory, not a ground survey.
A sponsor who needs every fault located and scored buys a Grade; a sponsor who needs a single failure diagnosed and its remedy defined buys a Fault Investigation.
How it runs
A system cannot be read until we understand what it is meant to do and where it ends. Every Reading therefore begins by settling the system's purpose and boundary. That first deliverable sets the access required, fixes the fee for the remaining work, and gives you a clean decision point on whether to proceed. Then the system is read whole, against the purpose it is meant to serve.
Charter
The Charter records the system, its purpose as you give it, a proposed boundary, and a not-to-exceed fee.
The signed charter.
First deliverable
We settle the system's purpose and boundary. With them comes an inventory of the access the work requires, and fixed fees for the remaining milestones.
The purpose and boundary judgment, and the access inventory.
Reading the system
Documents, conversations with people across the system (not only in the department that raised the question), and time with the system in operation. The work looks at the system from every side that matters: what it is for, how it is arranged and divided, how its parts relate, what it assumes, and whether it corrects itself.
Draft report
You review a draft for errors of fact, and may attach a written response to any finding. We correct the facts the evidence confirms. The findings themselves change only on new evidence, not on request. Your response travels with the final report, together with our reply.
The draft report.
Final report
What was seen is brought together into an account of the system as a whole. Each finding is then placed where it lives and classified by its nature. We take you through it in a working session.
The final report and working session.
What it asks of you
Your time at four points: at the start to frame the Charter, at the first deliverable to decide whether to proceed, at the draft for a factual review, and at the end for the working session. Access to the documents, the people, and the system in operation. And the understanding that a finding may land outside the department that raised the question: it is delivered to you unedited.
Terms
- Fee
- From $30,000 for a system within one department. From $45,000 for a multi-department system. From $60,000 for a system spanning organizations.
- How it is set
- The Charter sets a not-to-exceed ceiling. With the first deliverable, we fix the fee for the remaining work based on the scope and complexity the inventory reveals. Fees are paid by milestone. They change only if the boundary or purpose changes, and are never contingent on findings.
- Timeline
- The first deliverable usually arrives within two weeks. The final report follows four to six weeks after you decide to proceed.
- Approval
- Approved by a sponsor with the authority to grant access across the system's boundary. In public work, by an assembled authority where leadership is divided.
- Public bodies
- Invoiced in arrears. This work is usually procured as an organizational assessment, an operational review, or a Public Systems Assessment. We supply the scope-of-services language your procurement office requires.
What it is not
A sponsor who has commissioned a program evaluation or a management review will know what those return: a measure of performance against targets, and recommendations for running things better. Both are useful, but both take the system itself for granted. A Reading starts a step earlier, with what the system actually is and whether it is sound. It tells the sponsor what they have.
Where every fault must be found and scored—an annual health check, diligence before a transaction, evidence for a regulator—the product is a Grade. Where one specific fault must be traced to its source and its remedy defined, it is a Fault Investigation.
Begin with the situation
Tell us what you own and what the situation is. We will confirm whether a Reading is the right approach, or direct you to the engagement that is.