You measure delivery. You do not measure the thinking that comes before it.
The Architecture of Analysis is a proprietary model for measuring how well an organization can analyse: understand a problem, weigh options, and decide on evidence rather than on the loudest opinion in the room.
01 / The gap
Bad analysis has no metric of its own.
Velocity, burn rate, delivery dates. Every organization tracks the work of building. Almost none track the quality of the reasoning that decided what to build.
So weak analysis stays invisible. It does not appear on a dashboard. It appears eighteen months later, as a system nobody uses, a budget spent twice, or a requirement that was never the requirement.
By then it is filed as a delivery problem, and the organization fixes delivery again.
This model exists because the question "how good are we at analysis?" is usually answered with an anecdote. It should be answered with evidence.
02 / The instrument
A capability model built over years of practice, applied to your organization.
The model breaks analytical work into discrete, observable capabilities, each phrased as something an organization can either do or not do. Your teams are measured against it directly, so the result is a position, not an impression.
The model itself is proprietary and is not published. What you receive is your organization measured against it.
Layers, from strategic to supporting
Capability areas
Individual capabilities assessed
03 / What you receive
Where your organization stands, and what follows from it.
-
01
A measured position
Your organization's analytical capability, area by area, based on structured input from the people doing the work rather than on a management view of them.
-
02
The gaps that matter
Not every gap is worth closing. You get the ones that carry consequences for the decisions your organization is making now.
-
03
Development recommendations
What to build, in whom, and in what order. Specific enough to plan against, and separated from what training cannot fix.
-
04
A conversation about the findings
The report is walked through with you. Numbers on a page settle nothing; the decisions they lead to are the point.
04 / Where it is used
The same model answers several different questions.
For leadership
-
A
Analytical process design
Establishing how analysis is actually run in your organization: who decides what, what gets written down, what gets approved, and where work stops being guesswork.
-
B
AI adoption, judged against capability
Which analytical work in your organization an AI tool can genuinely take on, and which parts will fail quietly if you hand them over. The recommendation follows from the measurement, not from the vendor's demo.
-
C
Due diligence on your own practice
Before a reorganization, a transformation programme or a major system decision, an evidence-based answer to whether the analysis underneath it can be trusted.
For L&D and HR
-
D
Competency mapping and development paths
A defensible basis for a development plan: what this team can do, what it cannot, and what a realistic next level looks like for each person.
-
E
Recruitment
Hiring against the same capabilities you measure internally, so a new analyst is assessed on the work rather than on a familiar list of tools.
-
F
Assessment centre
Structured exercises drawn from the model, used for selection or promotion, scored consistently rather than by impression.
05 / Who runs it
Agnieszka Balcerzak
President of the IIBA Poland Chapter. Business analyst, trainer and mentor, working with analysts and with the organizations that employ them.
The Architecture of Analysis is her own model, developed in practice and not published. Assessments are run by her personally.
Related work: theBABrain, an open framework for how analysts keep and use context.
06 / Start
Find out where your organization actually stands.
Write with a sentence or two about your organization and what prompted the question. You will get an answer about scope, timing and whether an assessment is the right instrument at all.