Three levels of measurement
The first is activity: attendance, communications sent. The second is usage: how many people actually execute the new process in the system. The third is outcome: what changed in the business indicator. Programs usually report the first and stop there.
- Real usage of the new process or tool by area and by week
- Rework and exceptions to the new procedure
- Perceived usefulness through brief, frequent pulse checks
- The business indicator associated with the target behavior
Define the behavior in observable terms
"Be more collaborative" can't be measured. "Log the opportunity in the CRM before the first visit" can. Translating every cultural value into observable behaviors by role is the groundwork that makes any measurement possible.
The curve reverses if nobody sustains it
Adoption rises in the first weeks from the launch effect and falls once attention shifts to another topic. Reinforcement — recognition, direct-manager follow-up, visible consequences — is what separates a curve that stabilizes at the top from one that returns to the baseline.
Key takeaways
- Attendance is activity; real usage and outcomes are adoption.
- Every cultural value must translate into observable behaviors by role.
- Without reinforcement, the adoption curve returns to baseline.
NS frameworks and reference sources
- Proprietary NS framework · AE·NS — methodological notes from the Culture and Change practice
- NS project base: anonymized cases by sector and geography
- Open market evidence and academic literature, recalibrated with client data
- McKinsey — 'Why do most transformations fail?' (success rate ~30%)
- Kotter (1996) — Leading Change
- Prosci — Best Practices in Change Management
This article develops proprietary NS Business Strategy frameworks, drawing on our project base and on public industry literature and studies cited above. Figures are reference ranges; each project is measured against the client's actual data.