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, and, with access, your own contribution this month.

Growth turns everyday work in the catalog, glossary, and contracts into a single, celebratory picture of how far your organisation has come — and where to push next.

PillarsSix · each scored 0–100

StagesReactive → Prescriptive

RefreshDaily · UTC

AccessDNA Growth (read)

When you see it¶

Front and centre on home

Once your organisation has enough catalogue and glossary activity, the home layout leads with Growth instead of Quickstart.
Setup mode until then

Below the footprint threshold, home stays focused on Quickstart so new workspaces are not overwhelmed.
Access-gated detail

The DNA Growth (read) role unlocks scores, pace, projection, unlocks, and personal contribution. Without it, home may still show "setup" mode.
Your own month

With access, the actions that fed maturity signals are rolled up for you — a personal contribution, not an org-wide leaderboard.

The footprint threshold (today)

Home surfaces Growth after at least five published Data Catalog assets and five approved Business Glossary terms. The product may tune these numbers; the idea is a minimal footprint of governed objects before the maturity story is meaningful.

How the Growth card is composed¶

The six pillars are scored daily, then the home page assembles four signals into one card: balance (which pillar lags), momentum (recent pace), recent unlocks (celebrations), and — with access — your contribution this month.

flowchart LR
    P["Six pillars<br/>each scored 0–100 + a stage"] --> BAL["Balance<br/>weakest pillar surfaced"]
    P --> MOM["Momentum<br/>recent pace: up / flat / down"]
    BAL --> CARD
    MOM --> CARD
    UNL["Recent unlocks<br/>capability milestones"] --> CARD
    ME["Your contribution<br/>this month (with access)"] --> CARD
    CARD(["Growth card<br/>on your Home page"])
    classDef accent fill:#ff8400,stroke:#e67700,color:#ffffff,font-weight:600;
    class CARD accent

Figure 1 — how the Growth card is composed. Pillar scores feed balance and momentum; recent unlocks and your personal contribution round out the story that lands on home.

Why teams reach for this

Growth answers one question on first load — where are we heading next? — without a diagnostics wall. It celebrates what unlocked (milestones, never permission walls), makes a single neglected pillar visible, and keeps the picture tenant-scoped so no other organisation ever sees your scores.

The six pillars¶

Each pillar is scored 0–100 and carries a stage. Together they describe how balanced your data practice is.

Pillar	What it reflects
Catalog coverage	How much of the Data Catalog is documented and governed.
Glossary completeness	Depth and completeness of the Business Glossary.
Quality & contracts	Data quality and contract coverage.
Automation footprint	How much of the work is automated across the platform.
Intelligence adoption	Use of intelligence — HERC and assisted workflows.
Stewardship engagement	Steward participation and engagement.

Each pillar's stage runs Reactive → Proactive → Predictive → Prescriptive (four stages). How a pillar's score is built from primitives, calibrated against your organisation's baseline, and rolled into a headline is covered on Growth maturity.

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	An equal-weight composite of all six pillars (each weighted 1/6) — the headline stage blends every pillar, not just the weakest. When one pillar sits well behind the rest it is surfaced separately as the bottleneck, so a single neglected area stays visible without dragging down the whole headline.
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.

flowchart LR
    JOB(["Daily job<br/>once per org · UTC"]) --> SIG["Refresh signal snapshots"]
    SIG --> SCORE["Recompute pillar scores + stages"]
    SCORE --> HIST["Record stage history"]
    SCORE --> UNL["Detect new capability unlocks"]
    SCORE --> ROLL["Update contribution rollups"]
    HIST --> STORE[("Stored results")]
    UNL --> STORE
    ROLL --> STORE
    STORE --> READ["Home + APIs read stored results"]
    classDef accent fill:#ff8400,stroke:#e67700,color:#ffffff,font-weight:600;
    class JOB accent

Figure 2 — the once-a-day refresh. Everything is computed in the job and persisted; home and the read APIs never recompute, so the page loads fast and the numbers are stable within a day.

Deterministic numbers, generative narration

The Growth engine produces the numbers deterministically. When HERC narrates them, the prose is generative — but it reads the same stored results, so what it says about your maturity matches what the card shows.

HERC and Growth¶

HERC can answer questions about your maturity using dedicated tools — for example: your current snapshot, what unlocked lately, and what small action might help most. 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 allows reading other users' contribution summaries for support and governance. Exact names appear in your tenant's Roles UI.

Prereq	Permission	Why
See Growth on home	`dna.growth.read`	Scores, pace, projection, unlocks, and your own contribution.
Read another user's contribution	`dna.growth.read_all_users`	Admin-style: view someone else's monthly contribution summary where policy allows.

Limitations (today)¶

Limitation	What it means today
Projection is linear and history-dependent.	Sudden process changes or one-off imports can skew "when we reach X" estimates — treat projection as indicative.
Pillar weights and signal definitions are platform-defined (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.
No team or department rollups.	Contribution rollups are per user, not per team, in v1.

Audit and compliance¶

Question	Where it lands
"Can another organisation see our scores?"	No — maturity data is tenant-scoped; other organisations never see your scores.
"Is an unlock auditable?"	Unlock and related events 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.
"Who can see an individual's activity?"	Only the user and authorised admins. The contribution view is gated by role groups — restrict cross-user detail with `dna.growth.read_all_users`.

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.