BP-027Grade B27 supporting cases (26 counted), 0 counter-examples
Scale risk, quality and control functions with the speed and size of the change
The practice
Keep compliance, risk, quality, safety and accounting controls independent and resourced in proportion to the change, and scale them as the business speeds up, grows or concentrates its risk.
Why it works
Transformation increases risk while often reducing the attention given to control: agile teams move faster than change control, growth outpaces safety assurance, commercial complexity outpaces accounting, and a refocused portfolio concentrates risk in the business kept. Controls that are independent of the businesses they check, and resourced with the change, catch the failures that speed creates. The control culture also needs testing separately from the growth culture, because a successful growth story can mask a weakening control environment. Centralising risk and HR oversight before a business line becomes too autonomous to challenge is easier than doing it after.
KB synthesis: the mechanism is the knowledgebase's own reasoning, drawn from the member lessons. Factual support is the case claims under evidence.cases and the research under evidence.research (R-refs).
How to apply it
- Set control-function capacity as a ratio to the change (releases, growth, complexity) and review it quarterly.
- Keep compliance and risk independent of the business lines they check, with direct board access.
- Scale quality and regulatory controls with the strategic bet when the portfolio concentrates.
- Test the control culture separately from engagement or growth measures.
- Centralise oversight before a business line becomes too autonomous to challenge.
Warning signs
- Control headcount is cut in the same programme that speeds delivery.
- Accounting adjustments rise with supplier or commercial complexity.
- Safety or quality audits fall behind growth.
When it applies
- Agile and digital transformations, rapid growth, portfolio concentration and regulated industries.
When it does not
- Where the change reduces risk (simplification, exits); control capacity can then shrink with it.
Evidence grade: Grade B
At least 6 counted supporting cases for every 100 cases in the knowledgebase (6 × cases ÷ 100, rounded to the nearest whole number), whose primary regions span at least 4 regions.
Why this grade
Grade B by schema 4.10 route: >=14 counted cases across >=4 primary regions (the case bar is 6 per 100 cases in the knowledgebase, 235 cases). A needs a systematic, peer-reviewed study that tests this practice. None of the research cited in the KB does. 1 supporting case(s) rest only on company-reported claims and are not counted toward the grade.
Where it applies
- Transformation type
- Topic (business problem)
- Function
- Starting situation
- Industry
- Region
Supporting and counter cases
Siemens AG CS-028
ING Group (ING Netherlands) CS-012
Wells Fargo & Company CS-081
Ethiopian Airlines Group CS-030
Magazine Luiza S.A. (Magalu) CS-022
Microsoft Corporation CS-013
County of Marin, California CS-105
Dewey & LeBoeuf LLP CS-108
Bancolombia S.A. (Grupo Bancolombia, renamed Grupo Cibest) and its digital platform Nequi CS-129
Avast Software (Avast plc from 2018), Prague-based consumer cybersecurity company CS-229
Researched and fact-checked knowledgebase · Knowledgebase built 5 November 2026
Practices, their evidence grades and case summaries are public. Full case studies are available in AXIOM to subscribers and AXIOM Discover participants.

