Change Management for Startups & SMEs (Part 4):A Practical Change Playbook - From Diagnosis to Reinforcement
- Nhi Hong
- 15 hours ago
- 3 min read
By: Nhi Hong
So far in this series, we’ve covered:
Now comes the most practical part:
How do you actually run change in a startup or SME without turning it into a corporate project?
This article lays out a simple, realistic playbook founders can use.
Not a heavy framework.
Not a consulting model.
Just a sequence of steps that works in resource-constrained environments.
#1 Change Is a Process, Not an Announcement
Many change initiatives fail because they start with:
“Here’s the new direction.”
But sustainable change usually follows a different flow:
Understand -> Design -> Align -> Execute -> Reinforce
Skipping any of these creates gaps that show up later as resistance or low adoption.
Let’s walk through each step.
Step 1: Diagnose the Current Reality
Before proposing solutions, take time to understand what is actually happening today.
Not what is written in SOPs.
Not what people say in meetings.
What really happens on the ground.
Focus on:
how work flows between teams
where delays or rework appear
who makes which decisions
where founders step in
what frustrates customers or employees
Simple methods work well here:
short interviews
shadowing daily work
reviewing handovers
mapping one or two core processes
The goal is clarity.
You want a shared picture of the current state.
Without this, change is built on assumptions.
Step 2: Define the Future State Clearly
Avoid vague goals like:
“be more professional”
“work more efficiently”
“improve ownership”
People need concrete direction.
Instead, define:
who owns what
how decisions will be made
what success looks like
how workflows should run
which behaviors are expected
This doesn’t require perfection.
It requires visibility.
Even a rough operating model is better than ambiguity.
Step 3: Identify the Gaps
Now compare:
Current reality -> Desired future
Look for gaps in:
skills
processes
clarity of roles
mindset
capacity
This step prevents overreacting.
Sometimes the issue is training.
Sometimes it’s structure.
Sometimes it’s simply unclear expectations.
Not every problem needs a big solution.
Step 4: Build a Change Narrative
People don’t follow spreadsheets.
They follow stories.
A simple change narrative includes:
Where we are today
What’s not working
What will improve
What the future looks like
What each team’s role is
This is not marketing.
It’s alignment.
Repeat this narrative consistently across meetings, 1:1s, and team discussions.
Step 5: Design Interventions (Not Just Training)
Training alone rarely changes behavior.
Think in combinations:
communication
role adjustments
SOP updates
coaching
KPI alignment
incentives
pilot projects
For example:
If you want ownership, clarify decision rights.If you want accountability, connect performance to outcomes.If you want consistency, remove parallel ways of working.
Change needs reinforcement in daily operations.
Step 6: Execute in Waves, Not All at Once
Avoid “big bang” transformations.
Instead:
start with a pilot team
test new ways of working
learn from friction
adjust
then scale
Early wins matter.
They build confidence and show the change is practical.
Step 7: Reinforce Until It Becomes Normal
This is where many founders stop too early.
After launch, you still need to:
review progress regularly
recognize new behaviors
adjust KPIs
remove old processes
address relapses
If old habits remain available, people will return to them under pressure.
Reinforcement turns change into routine.
Common Execution Mistakes to Avoid
Across startups and SMEs, we often see:
designing change without frontline input
launching before leadership alignment
keeping old systems alongside new ones
measuring business results but not adoption
expecting fast behavior change
moving on before habits stabilize
Awareness of these patterns already improves outcomes.
A Simple Rule for Founders
If you want change to stick:
Align People + System + Leadership.
Not sequentially.
Together.
That means:
people understand and feel supported
systems guide daily behavior
leaders model the change consistently
When one layer is missing, progress slows.
Final Thought
Change doesn’t require perfection.
It requires presence.
Founders don’t need to become change experts.
They need to stay engaged long enough for new ways of working to become normal.
That’s what makes the difference.
What Comes Next
In Part 5 (the final article of this series), we’ll address a common frustration:
Why many changes look successful at first, then slowly fade.
We’ll explore:
why momentum drops
how founders unintentionally undo progress
and how to sustain change over time
This is about turning change into capability, not one-off projects.
--
𝐒𝐎𝐒𝐏 𝐂𝐨𝐧𝐬𝐮𝐥𝐭𝐢𝐧𝐠 𝐆𝐫𝐨𝐮𝐩
🏢 Headquarter: 17F, 72 Le Thanh Ton, Saigon Ward, HCMC, VN,
🌍 Community: ScaleX Founders
Comments