Growth: organisation maturity on your home page

Growth is your organisation’s maturity story in one place: how balanced the six pillars of data practice are, whether momentum is improving or slipping, what unlocked recently (celebrations, not permission walls), and — when you have access — your contribution this month.

When you see it

• Home page: After your organisation has enough catalogue and glossary activity, the home layout puts Growth front and centre. Until then, home stays focused on Quickstart so new workspaces are not overwhelmed.
• Threshold (today): at least five published Data Catalog assets and five approved Business Glossary terms. The product may tune these numbers; the idea is “we have a minimal footprint of governed objects before the maturity story is meaningful.”
• Permission: You need the DNA Growth (read) role (or a role group that includes it) to see scores, pace, projection, unlocks, and personal contribution. Without it, you may still see home in “setup” mode with Quickstart and an explanation that Growth requires access.

What the numbers mean

Idea	Plain language
Pillars (six)	Coverage of the catalog, glossary depth, quality/contracts, automation, use of intelligence (e.g. HERC and assisted workflows), and stewardship engagement. Each pillar is scored 0–100 and has a stage (from reactive toward prescriptive).
Organisation stage	The org is only as mature as its weakest pillar — the headline stage is driven by the lowest pillar stage so a single neglected area is visible.
Pace	Based on recent daily snapshots — whether pillar scores are trending up, flat, or down versus an earlier window. Not a prediction by itself; it describes recent slope.
Projection	An estimate of when a pillar might cross a score threshold if recent trends continue. Built from simple linear regression on history — useful for planning, not a guarantee. Volatile weeks make the estimate less reliable; the UI should reflect that uncertainty.
Unlocks	When a pillar combination crosses a defined threshold, the platform records a one-time unlock for a capability label. This is a celebration and timeline event — it does not turn features off or on in the product today.
Your contribution	Actions that fed maturity signals are rolled up for you (e.g. this month). Administrators can view another person’s contribution summary where policy allows; there is no org-wide leaderboard in v1.

How it stays fresh

A scheduled job runs once per day (UTC) for each organisation: it refreshes signal snapshots, recomputes pillar scores and stages, records stage history, detects new capability unlocks, and updates contribution rollups. The home page and APIs read stored results so loading stays fast.

HERC and Growth

HERC can answer questions about your maturity using dedicated tools (for example: current snapshot, what unlocked lately, what small action might help most). Narration is generative; the numbers are deterministic from the Growth engine. When capability unlocks are narrated, short diary-style context may be stored so HERC can refer to “what changed since last month” without recomputing history each time.

Setup — roles

Your administrator assigns a role group that includes DNA Growth (read) for users who should see the composite on home. A separate permission may allow reading other users’ contribution summaries for support and governance (admin-style). Exact names appear in your tenant’s Roles UI.

Limitations (today)

• Projection is linear and history-dependent — sudden process changes or one-off imports can skew “when we reach X” estimates.
• Pillar weights and signal definitions are platform-defined in v1 — not yet editable per tenant in the UI.
• Unlocks do not gate features — they are milestones on the journey timeline, not license or menu switches.
• No org-to-org benchmarking — comparisons are only within your tenant’s own history.
• Team or department rollups of contributions are not in v1.

Audit and compliance

• Maturity data is tenant-scoped — other organisations never see your scores.
• Unlock and related events are intended to leave audit-friendly metadata (what happened, when, for which org) consistent with your platform’s audit log policy; diary text for HERC follows the same privacy rules as other agent diary features.
• If your policy restricts who may see individual user activity, rely on role groups — the contribution view is designed so only the user and authorised admins see cross-user detail.

Troubleshooting

Symptom	Likely cause	What to try
Home still shows Quickstart only	Org below asset/term threshold	Publish more catalog assets and/or approve more glossary terms until counts pass the threshold.
“No access” / empty Growth	Missing Growth read role	Ask an admin to add DNA Growth (read) (or equivalent) to your role group.
Scores unchanged for days	Daily job delay or new tenant	Wait for the next daily snapshot cycle; if still stale, contact support with org id and date.
Projection seems wrong	Few data points or volatile history	Treat projection as indicative; widen time window conceptually — the product surfaces confidence where implemented.