Carlson BCMMethods
Repeatable paths from strategic intent to measurable change. Each method is the same discipline, applied to a different question.
Most transformations miss their objectives for the same reason.
People, process, and technology are the usual explanations. They are symptoms. The root cause is the absence of a design method that links strategy, operations, and technology to one definition of what the enterprise must be able to do.
Every method in this volume has been applied in practice, on programs in insurance, capital markets, and private equity. Where an engagement has been published in full, it is linked beside the method it demonstrates. More are in preparation.
Every method begins in one place.
Business and IT Planning and Analysis
What must the enterprise be able to do, and what does each strategic intent require of it?
Existing artifacts are consumed rather than discarded, the missing linkages are authored, and the result is a reusable architecture asset every later method draws on. When the requirement arrives from outside, in law, the same foundation translates the statute into an operating model.
Published example: Capital Markets Under New LawWhere the discipline was forged.
Unify the Customer and Agent Experience
How do customer, agent, and broker journeys align across products, coverages, channels, and regions?
An omni-channel design that removes fragmentation, sustains the agent's role in the value chain, and carries AI-native enablers consistently across the enterprise.
Applied in practice · paper in preparationStreamline and Optimize Business Processes
What is the unit of analysis a process method is missing?
Normalized, non-redundant, non-sequential capabilities: the functional index that Lean, Six Sigma, and process mining lack, with performance measured against it.
Published example: The Voice of an InstitutionEnable Growth through Integration and Acquisition
Are the target's capabilities redundant or additive, and where does the business actually divide?
Business and technology capabilities interrogated on both axes, before and after the transaction, so the seam is a decision rather than a discovery.
Published example: The Seam, Before the PriceModernize and Scale Platform Technology
Which capabilities should the modern platform carry, and what can the legacy estate stop specifying?
Legacy consolidation and platform modernization aligned to business value, full stack, with each ability authored once and reused wherever it occurs.
Published example: The Book They Could Not MoveThe same discipline, across industries.
Digital and Customer Experience Transformation
Which abilities does every journey depend on, whatever the channel?
Experience designed once against the abilities beneath it, rather than rebuilt for each channel and touchpoint.
Applied in practice · paper in preparationData, AI, and Cloud Transformation
Which data assets serve which capabilities, and which are redundant?
Lineage embedded in business context: every data asset mapped to products, markets, and users, revealing ownership, redundancy, and value.
Applied in practice · paper in preparationInnovation and Product or Service Transformation
What does a new product, line, or partnership require that the enterprise cannot yet do?
A product becomes a change to attributes rather than a new specification, and the gap to a new line is visible before it is funded.
Applied in practice · paper in preparationApplication and Portfolio Modernization
Which capabilities should modernize, which should hold, and which should retire, and in what order?
Every application bound to the capability it carries, so the disposition is made once, at the capability level, and defended to the people who own it.
Published example: Cloud Migration for Capital MarketsCost and M&A Transformation
Where is the enterprise paying for the same ability more than once?
Cost removed at the level of specification, where redundancy actually lives, rather than at the level of headcount or systems alone.
Applied in practice · paper in preparationThe Future of IT Operations
Which capability, and which customer, does an infrastructure event reach?
Observability and operations traced to business impact, chip to experience, so availability is measured against what the enterprise must be able to do.
Applied in practice · paper in preparationWho does the work, and who is allowed to commit.
Workforce Capacity Intelligence
Where does enterprise work actually concentrate, and what portion can AI transform without breaking governance?
Four independent relationships separated for every capability: who owns the outcome, who must retain decision rights, who performs the work, and what AI can do to it.
Applied in practice · paper in preparationAI Fit and Authority
For every capability, what may the machine do, where does the human decision sit, and which models fit the work?
Business value, AI classification, retained authority, and model alignment scored independently against the same abilities, before any model is chosen.
Applied in practice · paper in preparationCompetency Transformation
What must people be able to do, and how far is each person and team from it?
A competency model governed by the same architecture as the enterprise, with objective mapping and a transformation method for individuals and teams.
Applied in practice · paper in preparationOne definition of the enterprise. Every method renders from it.