The BCB principle applied one layer further: if commercial content must be modular, audience-specific, behaviorally targeted, and reusable, so must the materials that train people to use it. A training ecosystem built as a collection of custom one-off documents is exactly as commercially inefficient as a marketing content system built without modular architecture.
Most BCB + CRM implementations apply modular architecture discipline to marketing and commercial content, then revert to ad-hoc, one-off documents for the training materials that teach people to use that same system.
The result is a familiar pattern: a beautifully modular component library and NBA engine, supported by a scattered set of PowerPoint decks, PDFs, and email threads that no one owns, no one versions, and no one retires. Training materials degrade exactly the way unmanaged commercial content degrades — they go stale, they duplicate effort across markets and cohorts, and they fail to reach the specific audience and moment where they would change behaviour.
This use case documents what that discipline looks like applied in full: a catalogue of 28 material types organised into five categories, each with a defined behavioural objective, a defined audience, a defined production specification, and a defined update cadence — the same three attributes the BCB Framework™ requires of every commercial content component.
Each category serves a different audience, a different learning objective, and a different stage of the implementation sequence.
Twenty-eight full specifications sit behind this catalogue. Five representative categories, expanded below, with their highest-impact material types.
The BCB Diagnostic Readout Deck converts executive curiosity into sponsorship: 15–20 slides for a 45-minute facilitated session, each gap finding paired with its estimated commercial cost. The Governance Committee Pre-Read Pack enforces a 3-page maximum as a decision-quality discipline, not an efficiency measure — “a governance committee that reviews a 25-page deck does not govern, it observes.” The Annual Commercial Performance Review Deck closes the loop, connecting implementation progress to commercial outcomes at month 11.
The BCB Field Playbook is a job aid, not a textbook — structured around the five questions a commercial team member asks daily, not around the framework's internal logic. The NBA Rationale Explanation Guide is the most frequently underproduced material in CRM + NBA deployments, and the one that most directly closes the trust gap driving the resistance peak at weeks 4–6: an advisor who understands why a recommendation was made is 3× more likely to accept the next one. The Top Performer Behavioural Patterns Report reframes training from “what does the system want you to do” to “what do your best colleagues actually do” — a fundamentally more persuasive commercial framing, available only after 8–12 weeks of live CRM data.
The Content Governance Manual is the operational bible for the modular library across six chapters — specification standards, metadata taxonomy, MLR submission process, assembly rules, expiry protocol, and agency briefing standard. The MLR Submission Guide for Modular Components exists because compliance reviewers who receive BCB components through the standard asset submission process will reject them for lack of context — a modular submission has no finished visual layout, because the component will be assembled into many. The Propensity Model Retraining Protocol is what prevents permanent vendor dependency, enabling the data engineering team to execute quarterly retraining independently from week 8 onward.
The CRM NBA Microlearning Series sequences twelve 5-minute videos across the first twelve weeks post-deployment — one CRM task at a time, timed to when it becomes relevant, not delivered as a single pre-launch bundle. Archetype Classification Scenario Exercises produce their highest value in group cohort review sessions at weeks 4 and 8: the disagreement conversations between participants produce deeper archetype understanding than any lecture content. The Knowledge Base starts at 40 FAQs at deployment and grows to 80+ by month 3, purely from real post-deployment questions — a living document, not a static release.
The Behavioral Objective Specification Template exists because a behavioral objective that is insufficiently specified cannot be encoded in a propensity model or CRM workflow — the template forces precision to target audience, observable action, timeframe, measurement method, success threshold, and leading indicator, one page per objective, typically three per engagement. The BCB KPI Tracking Template pre-specifies the three-tier dashboard — metric, formula, data source, cadence, threshold, alert condition, governance audience — before a single chart is built in Tableau or Power BI, because a dashboard built without this specification “looks like measurement but cannot be used for commercial decisions.”
Every format has production requirements that, if ignored, produce materials that look professionally made but fail to change commercial behaviour — functional requirements derived from how each format is actually used in the field, not aesthetic standards.
| Format | Critical Spec Requirements | Common Failure |
|---|---|---|
| Executive Deck (PPT/Keynote) | Maximum 1 idea per slide. No bullet points. Data visualisation, not tables. Print-readable at A4. | Too dense — executives extract 1 decision from a 40-slide deck by reading every third slide. |
| Field Reference (PDF, laminated) | Print-tested at A5/A4. Minimum 11pt body text. High contrast for bright environments. Indexed if >4 pages. | Designed for screen — impossible to read in field conditions. Never laminated or reprinted when the system changes. |
| Technical Specification (Word/PDF) | Version number and date on every page. Change log at front. Searchable. Navigable without reading sequentially. | Not version-controlled — outdated versions circulate. Critical detail buried in body text. |
| eLearning Module (SCORM) | Maximum 15 minutes per unit. Scenario-based. Assessment per unit. Branching by role. Mobile-compatible. | Too long. Passive content with assessment tacked on. No role branching — irrelevant to 40% of the audience. |
| Microlearning Video (MP4) | Maximum 5 minutes. Screen recording with voiceover. Subtitled. No corporate intro — starts on topic immediately. | Professional production that cannot be updated when the CRM interface changes. A 45-second intro on a 4-minute video. |
| Template Document (Word/Excel) | Example-completed version alongside the blank template. Mandatory fields marked. Instructions embedded in field labels. | Blank template with no example. Guidance in a separate, unread document. User guesses and produces unusable output. |
Materials that arrive late are often as commercially costly as materials never produced — they create gaps in the adoption programme at the exact moments the behavioural change they support is most needed.
Diagnostic Readout Deck (produced from live Diagnostic data, 1 week) and the Business Case & Value Model (1 week from Diagnostic completion) — both gated on Diagnostic completion. The Behavioral Objective Specification Template is blank-distributed at Stage 01 kickoff, ready for use.
The Brand Architecture Document Template is pre-built and available at Stage 01 kickoff; the completed document is produced during this stage and gates Stage 03 and 04 — work does not proceed until it is signed off by all BCB pillar owners. The Change Communication Toolkit's launch announcement component is due 3 days from programme launch confirmation.
The Content Governance Manual is due 3 weeks from Brand Architecture Document sign-off; the Component Specification Template and MLR Submission Guide must be available and in active use before any component is briefed to an agency or submitted for compliance review — these are hard prerequisites, not parallel-track documents.
The CRM Object Architecture Reference follows 1 week post-build; the Propensity Model Retraining Protocol is due 2 weeks before model deployment. The Data Governance Handbook requires compliance and legal sign-off before production go-live — begin 4 weeks before go-live to allow for that review cycle. The Governance Framework Document requires the executive sponsor's signature before deployment.
All Day 1 materials — Field Playbook, Conversation Guide, Quick Reference Card, Assembly Guide, Foundations eLearning, Scenario Exercises, Knowledge Base — are due a minimum of 3 weeks before deployment and must be finality-reviewed by a commercial team member, not the programme team. The NBA Rationale Guide follows at week 4 (requires live NBA data to exist); the Top Performer Patterns Report at week 8 (requires 8–12 weeks of live CRM data) — neither can be produced earlier, regardless of programme pressure.
The Governance Pre-Read Pack and Change Communication Toolkit run on a standing cadence. The Annual Commercial Performance Review Deck is produced at month 11 — its 3-week production and 1-week review window, and the Brand Architecture Document's 4-week annual review process that must complete before it, should be calendared at programme launch, not scheduled ad hoc when someone remembers.