Why change management matters to a first-time founder
A change succeeds only when people understand it, can use it and reinforce the new behaviour. Founders often focus on choosing software or announcing a reorganisation, then underestimate training, incentives and local concerns. Poor adoption can erase the expected benefit even when the technical project finishes on time.
Examples of change management
A 40-person company replaces its customer system in eight weeks. It maps affected roles, trains sales staff on real accounts, appoints two support contacts and tracks weekly usage. After launch, 34 of 36 expected users work in the new system, so adoption is 94%: 34 ÷ 36 × 100.
Common misunderstanding
Change management is not public relations for a decision that cannot be questioned. Communication matters, but people may identify genuine risks or better ways to implement the goal. Hiding job losses, surveillance or material working-condition changes behind upbeat messaging is deceptive and may breach employment or consultation law.
When to use it
Use it when a change affects several people’s responsibilities, tools, incentives or routines. Scale the work to the disruption: a small process update may need one clear briefing, while a reorganisation needs consultation, training and follow-up. Do not add a ceremonial programme to a simple reversible experiment.