WCNMEASUREMENT & EVOLUTION MAP08 · GOVERNANCE → F
← 08 · GOVERNANCE
Measurement & evolution · F
Does it
still work?
still work?
A brand system is never finished. This cluster closes the loop — feedback, a version roadmap, audit cadence, compliance tracking, and how things are retired. Tap any card to open its spec.
FEEDBACKROADMAP
AUDITCOMPLIANCE
SUNSET20%
EVOLUTION COVERAGE
0 shipped
2 in progress
3 planned
08F01
Feedback loops
WIP
A system improves only if the people using it can push back into it. Feedback loops give that input one door, a fair triage, and a reply — so contributing feels worth it.
INTAKEOne door
TRIAGESteward
CLOSEAlways replied
SOURCEAll teams
F01.1 · INTAKE
One door.
All feedback enters through a single channel — not scattered DMs and hallway comments. One door means nothing is lost and everything can be triaged.
CHANNELOne
NOTScattered
LOSTNothing
OPENTo all
F01.2 · TRIAGE
Sorted, fairly.
The steward triages on a regular cadence — bug, request, or won’t-do — each with a consistent rule, so similar feedback gets similar treatment.
WHOSteward
CADENCERegular
BUCKETSBug · request · no
FAIRConsistent
F01.3 · CLOSE THE LOOP
Always a reply.
Whatever the outcome, the person hears back. Closing the loop is what makes people give feedback twice — silence is what kills the channel.
REPLYAlways
EVENIf declined
WHYTrust
SILENCEFatal
F01.4 · SOURCES
Listen wide.
Beyond the inbox, feedback is pulled from reviews, support themes and audits. The loop actively listens, rather than waiting to be told.
INBOXPlus
REVIEWSMined
SUPPORTThemes
MODEActive
DON'T
×
Don't scatter intake — One door for everything.
×
Don't triage by mood — Consistent rules per type.
×
Don't go silent — Always close the loop.
×
Don't only wait — Actively mine other sources.
“People give feedback twice only if the first time mattered.”
08F02
Version roadmap
WIP
A roadmap turns a backlog of wishes into a plan people can see. It shows what the brand system is working on, grouped into themes, on a horizon teams can rely on.
HORIZONQuarterly
THEMESGrouped
VISIBLETo all
INPUTFrom feedback
F02.1 · HORIZON
Near, mid, later.
The roadmap works in three bands — now, next, later — not exact dates. It commits to direction without pretending to predict the distant future precisely.
NOWIn build
NEXTCommitted
LATERDirection
DATESNot promised
F02.2 · THEMES
Grouped by intent.
Items group into themes — accessibility, motion, docs — so the roadmap reads as intent, not a flat list of tickets. Themes make trade-offs legible.
GROUPBy theme
READSAs intent
NOTA ticket list
TRADE-OFFSVisible
F02.3 · VISIBILITY
Out in the open.
The roadmap is public to the org. Teams plan around it, and seeing their feedback appear on it is the strongest signal that contributing works.
PUBLICTo org
PLANAround it
SIGNALFeedback lands
UPDATEDEach cycle
F02.4 · HOW IT’S SET
From signal, not whim.
The steward sets the roadmap from triaged feedback, audit findings and strategy — reviewed with the council so it reflects real need, not the loudest voice.
FROMFeedback · audits
WITHCouncil
REFLECTSReal need
NOTLoudest voice
DON'T
×
Don't promise exact dates — Now / next / later.
×
Don't list raw tickets — Group into themes.
×
Don't keep it private — Public builds trust.
×
Don't set it by whim — From signal, with the council.
“A visible roadmap is a promise people can plan around.”
08F03
Brand audit
PLANNED
Drift is invisible day to day and obvious in hindsight. A regular brand audit takes a deliberate step back, scores the brand against its own rules, and turns findings into work.
CADENCEBiannual
SCOREScorecard
SCOPEAll touchpoints
OUTFindings → roadmap
F03.1 · CADENCE
Twice a year.
The audit runs on a fixed schedule — twice yearly — so it actually happens. A standing date beats good intentions every time.
WHENBiannual
FIXEDScheduled
WHYIt happens
OWNERSteward
F03.2 · SCORECARD
A repeatable measure.
The same scorecard is used each time — consistency, coverage, compliance, freshness — so results are comparable and trends are visible across audits.
SAMEEach time
DIMENSIONS4
COMPARABLEYes
TRENDSVisible
F03.3 · SCOPE
Every touchpoint.
The audit samples across the brand — product, site, decks, social, print — not just the flagship. Drift hides in the places no one is watching.
SAMPLESAll channels
NOTFlagship only
FINDSHidden drift
REALIn the wild
F03.4 · FINDINGS → ACTION
From report to roadmap.
Findings don’t sit in a slide deck — they’re prioritised onto the roadmap with owners. An audit that doesn’t change anything is just a grade.
FINDINGSPrioritised
ONTORoadmap
OWNERSAssigned
ELSEJust a grade
DON'T
×
Don't skip the date — A fixed cadence, or it won’t happen.
×
Don't change the scorecard — Same measure for trends.
×
Don't audit only the flagship — Sample everywhere.
×
Don't shelve findings — Onto the roadmap, with owners.
“You can’t fix drift you never stop to measure.”
08F04
Compliance tracking
PLANNED
Rules only matter if they’re followed. Compliance tracking measures real adoption of the system, spots drift as it starts, and turns a vague worry into a number.
METRICAdoption
DRIFTDetected early
REPORTDashboard
OWNERSteward
F04.1 · ADOPTION
Count what matters.
Adoption is measured where it’s meaningful — components used from the system vs. rebuilt, on-palette colour, current logo. Pick a few real signals, not vanity counts.
MEASURESReal use
EXAMPLESystem vs custom
FEWSignals
NOTVanity
F04.2 · DRIFT DETECTION
Catch it starting.
Trends matter more than snapshots. A slow rise in off-system components is an early warning the audit can act on before it’s everywhere.
WATCHTrends
EARLYWarning
BEFOREIt spreads
ACTVia audit
F04.3 · REPORTING
One dashboard.
Compliance lives on a simple dashboard, not in a quarterly PDF. Always-on visibility means problems are seen when they’re small.
HOMEDashboard
NOTA PDF
ONAlways
SEESSmall problems
F04.4 · RESPONSE
Numbers to nudges.
Low adoption is a prompt — better docs, a fix, a conversation — not a punishment. Tracking exists to improve the system, not to police people.
LOWA prompt
ACTIONSDocs · fix · talk
NOTPunishment
GOALImprove system
DON'T
×
Don't measure vanity — A few real adoption signals.
×
Don't wait for snapshots — Watch the trend.
×
Don't bury it in a PDF — Always-on dashboard.
×
Don't weaponise it — Nudge the system, not people.
“A rule no one follows is a rule that needs fixing, not enforcing.”
08F05
Sunset policy
PLANNED
Adding is easy; removing is where systems get messy. The sunset policy is how the brand retires something on purpose — with notice, an alternative, and a clean archive.
STEPSDefined
NOTICEPeriod given
ALTProvided
ARCHIVEKept
F05.1 · WHEN TO RETIRE
Past its use.
Something is sunset when it’s superseded, unused, or off-strategy. Keeping dead options alive is its own kind of debt — removal is maintenance.
TRIGGERSSuperseded · unused
ALSOOff-strategy
KEEPCosts too
REMOVALIs upkeep
F05.2 · NOTICE PERIOD
Warned, not surprised.
Deprecation comes with notice proportional to use — the more something is relied on, the longer the runway before it’s gone.
NOTICEGiven
LENGTHBy usage
MORE USELonger
SURPRISENever
F05.3 · THE ALTERNATIVE
Always a way forward.
Nothing is removed without a documented replacement or path. A sunset without an alternative is just breakage with a polite name.
REPLACEDocumented
PATHProvided
ELSEIt’s breakage
LINKFrom notice
F05.4 · ARCHIVE
Gone, but recoverable.
Retired assets and rules move to a dated archive with the reason. History is preserved — so a future question about “why did we drop that?” has an answer.
MOVETo archive
WITHThe reason
DATEDYes
ANSWERSWhy later
DON'T
×
Don't remove silently — Notice, proportional to use.
×
Don't leave no path — Always an alternative.
×
Don't hard-delete — Archive with the reason.
×
Don't keep dead options — Retiring is maintenance.
“How a system removes things says more than how it adds them.”
In progress
The system that improves itself.
Feedback loops and the roadmap are forming. Audit cadence, compliance tracking and the sunset policy are scoped — the cluster that keeps the brand honest over time.
WCN Measurement & Evolution Map · 5 topics · F01–F0508 · GOVERNANCE · F · v1.0