Maturity is about how the platform is used

A common mistake is to confuse deployment milestones with maturity. Installing Kybera Impact, configuring the tenant, and onboarding business areas are the start, not the end. The platform is fully installed on day one. Maturity is what happens over the following years, as the catalog evolves, retention rules deepen, process automation expands, and the operating model self-improves.

This document maps maturity along five dimensions, each of which advances at its own pace. An organization can be highly mature on one dimension and early on another. The roadmap is a portfolio view across all five.

Five maturity dimensions

Dimension	What advances over time
Catalog and information model	Library templates, content types, taxonomies, and workspace templates evolve from a baseline that ships on day one to a rich catalog shaped by real organizational patterns.
Retention and classification	Manual retention application gives way to library-level defaults, then auto-apply rules, then event-driven rules, then AI/trainable-classifier-driven classification.
Process automation	Manual approval and submission processes are progressively automated using stock Microsoft 365 capabilities, Power Automate, and Power Apps. Covered in detail in Doc 4.7.
Operating model	Roles transition from central to distributed where appropriate. The IM Governance Body and CoP run a steady gap-to-deployment loop. Audit findings decline.
AI and Copilot adoption	Restricted SharePoint Search at first; then broad Copilot adoption; then Copilot Studio agents and AI-augmented automation.

Why dimensions, not just phases

Treating maturity as a single phase ('we're in Phase 3') hides the reality that catalog evolution can race ahead while retention auto-apply lags, or AI adoption can advance while process automation stalls. The dimensions let the forum see where to invest next.

Four phases across all dimensions

Phase	Focus	Typical duration
Phase 1 — Foundation	Platform installed and configured. Operating model launched. Initial business areas onboarded with baseline catalog.	3–6 months
Phase 2 — Coverage	Enterprise-wide platform use. Migration substantially complete. Generic retention applied. CoP active and surfacing gaps.	6–12 months
Phase 3 — Maturation	Crowdsourced catalog evolution flywheel running. Auto-apply retention deployed at library level. First wave of process automation in production. Lifecycle steady-state.	12–24 months
Phase 4 — Optimization	Process automation broad across business processes. Auto-classification (event-based, trainable classifiers) operating. Copilot fully adopted with mature AI-era governance.	Year 2 onward

Watch out

Phases overlap. An organization with strong Phase 2 coverage may still have early Phase 3 process automation. A mature Phase 4 AI posture can coexist with residual Phase 1 work in specific business areas. Maturity is a center of gravity across dimensions, not a binary state.

Phase 1 — Foundation

Goal: stand up a governable platform with the operating model in place.

Tenant configured. Sharing posture, naming policy, conditional access, MFA, sensitivity label taxonomy.
Platform installed. All capabilities deployed and ready — not phased. The starting point, not the destination.
Baseline catalog. Initial library templates, content types, taxonomies, workspace templates published.
Operating model launched. Brokers, Site Owners, Information Managers trained and active. Main forum operational. IM Governance Body chartered. CoP started.
Pilot wave. First 2–4 business areas onboarded with the baseline catalog.

Indicators: pilot areas operational; operating model functioning; baseline KPIs measurable; first CoP gap proposals queued.

Phase 2 — Coverage

Goal: extend the platform across the enterprise and start the maturity flywheel.

Onboarding complete. All planned business areas onboarded. Migration substantially done.
Generic retention applied. Per-app retention defaults from Doc 2.7 in effect across the tenant. Sensitivity label coverage on the highest-value content.
CoP active and feeding the IM Governance Body. First round of crowdsourced catalog gaps identified, approved, deployed. The flywheel begins to turn.
Lifecycle events visible. Project Teams archiving on schedule. First disposition reviews underway.
Audit cadence. Monthly audits running and acted on. Findings trending down.
First process automation candidates. High-friction processes identified for Phase 3 automation work.

Indicators: enterprise-wide platform use; coverage KPIs at target; first dozen catalog updates deployed via the IM Governance Body; first process-automation pilots in design.

Phase 3 — Maturation

Goal: the platform actively improves itself, and process automation starts to compound the value of the platform.

Catalog evolution flywheel running. Quarterly waves of catalog improvements coming out of the CoP and IM Governance Body. Templates, content types, and taxonomies keep pace with reality.
Auto-apply retention deployed. Library-level retention defaults applied broadly. The first set of auto-apply rules (based on metadata or content type) deployed for high-volume content.
Sensitivity label coverage growing. Auto-labeling on patterns in production for PII, financial data, regulated categories. Manual labeling adoption growing through champion-led training.
Process automation in production. First wave of approval and submission processes automated — typically document approval, departmental submissions (HR, Finance, Records), routine request flows. See Doc 4.7.
Operating model self-sustaining. Roles transition where appropriate from central to distributed. Audit findings declining. CoP attendance steady.
Lifecycle steady-state. Archive, hold-period, and disposition activity normal. Records hubs operational with structured retention.

Indicators: catalog updated 4–6 times a year via the IM Governance Body; retention coverage at high target with auto-apply contributing materially; 5–10 process automations in production; lifecycle KPIs steady.

Phase 4 — Optimization

Goal: AI-era capabilities, advanced classification, and broad process automation deliver continuous improvement.

Process automation broad. Many business processes automated end-to-end — submission, review, approval, audit trail. Power Platform footprint significant and well-governed.
Trainable classifiers and event-driven retention. Auto-classification deployed for content categories where pattern detection isn’t enough (resumes, contracts, policies). Event-based retention on lifecycle events (project closure, contract end).
Copilot fully adopted. Restricted SharePoint Search relaxed broadly. Container labels protect sensitive content. AI-era governance running through the main forum’s regular review cycle.
Advanced records management. Disposition reviews on cadence; records integrity defensible to external auditors; multi-stage retention with archival transfers operating.
Continuous improvement loop strong. CoP-driven, IM Governance Body-cycled, KPI-tracked. The platform improves measurably each year.
AI agents and Copilot Studio. Custom AI agents and Copilot Studio extensions deployed selectively, governed through the main forum’s AI-era review.

Indicators: retention auto-apply broad; process automation deployed in many domains; Copilot adoption broad and governed; KPIs strong across all four lenses; the platform shapes how the organization works.

How the dimensions advance over time

A heat-map view of where each dimension typically lands by phase:

Dimension	Phase 1	Phase 2	Phase 3	Phase 4
Catalog and information model	Baseline shipped	First gap-closure waves	Quarterly evolution flywheel	Mature catalog; minor refinements
Retention and classification	Generic policies live	Specific labels on highest-value content	Auto-apply rules at library level	Event-driven, trainable classifiers
Process automation	Stock M365 (Lists, Forms, Approvals)	First candidates identified	First wave in production	Broad coverage; AI-augmented
Operating model	Roles trained, central	Operating; some distribution	Self-sustaining; CoP→IMGB loop steady	Audit findings minimal; near-zero drift
AI and Copilot	Restricted SharePoint Search; pilot only	Pilot expansion	Broad adoption; container labels mature	Custom agents; AI-augmented automation

Watch out

Maturity in one dimension doesn’t carry the others. An organization with mature catalog evolution but weak process automation is leaving most of the platform’s value on the table. An organization with broad Copilot adoption but immature retention is creating compliance debt. Track the dimensions individually and invest in the laggards.

Roadmap mechanics

Annual roadmap review. Forum reviews position on each dimension, KPI trends, upcoming Microsoft platform changes. Sets the next year’s targets.
Quarterly adjustment. What’s slipped, what’s accelerated, what’s been added. The IM Governance Body’s catalog backlog feeds this view.
Capability owners. Each dimension has an owner — usually an Information Manager, domain lead, or process owner.
Communication. Roadmap is visible to the organization. Champions and CoP know what’s coming. Surprises are governance failures.

With Kybera Impact

Kybera Impact is installed at baseline and supports the platform across all four phases — the modules don’t sequence with maturity, the use of them deepens with maturity. Insights surfaces where each dimension stands. The Workflow Engine and Compliance module enforce standards as they evolve. The Library Catalog and Information Model deepen as the IM Governance Body approves changes. Most maturity work is configuration and process — the platform is ready for it from day one.

Discussion Questions

• Where do we sit today on each of the five dimensions — catalog, retention/classification, process automation, operating model, AI/Copilot?

• Which dimension is our biggest gap — what would advancing it unlock?

• What’s our 12-month target on each dimension?

• What’s our 3-year target — where do we want each dimension to land?

• What capability owners do we have today, and where are owners missing?

• What’s blocking us from advancing on each dimension — capacity, sponsorship, skill, licensing?

• How often do we review the roadmap — quarterly, annually?

• How do we communicate the roadmap to the organization to set expectations?