Sooner or later, every company faces a change it hadn't planned for. A strategic supplier shuts down, a major customer requires a certification that means rewriting half the supply chain, new management software arrives with the invoice already signed, a long-standing partner leaves and takes half of the operational memory with them. In the weeks that follow, some people charge ahead, some hold back, and three months later almost everything is back to how it was — only with more tension than before.
Change management in business is the set of methods and practices through which a company plans a transition, prepares people, carries out the shift and consolidates the new ways of working. It is not the decision to change: it is the way that decision travels through the organization without dissolving.
The numbers make the topic practical, not theoretical. European micro-enterprises are projected to operate in 2025 at about half the productivity of large companies, and the real value added of small and medium-sized enterprises in the EU fell by 0.2% in 2024 [4]. In management literature, the figure that about 70% of organizational change projects fail to reach their stated goals has been circulating for a long time [5]. Those who have traced it back to its origin, however, didn't find it: the review that follows five separate appearances of the figure concludes that there is no valid and reliable empirical evidence to support it [6]. It is not used as a measure here.
This guide walks through the practical steps of managed change in a company: from diagnosing readiness to the execution framework, from internal communication to measurement, all the way to the mistakes that make a project fall back before it shows results.
Understanding when a change is really needed, before launching it
Which part of the company's current change agenda is driven by a measurable need, and which by perceived pressure? The distinction changes the project's timeline, budget and success metric — and it's the first thing to go when change starts on a wave of enthusiasm.
Not every change deserves a formal management project, and not every formal project stems from a change that is really needed. Companies often launch a transition — new software, a new procedure, a department reorganization — because of external pressure or industry fashion, without a preliminary needs analysis.
An operational definition: change management in business is the method through which a company governs the transition from one way of working to another, with defined goals, planned timelines and measurement mechanisms. Four semantic boundaries to clarify:
Change vs transformation — change is incremental: it modifies one part of the system while leaving the overall architecture intact (new management software, a new sales process). Transformation is structural: it changes the business model, the scope or the very way value is created. The two concepts require different governance and timelines.
Change vs reorganization — reorganization acts on the structure (organizational chart, reporting lines, merging of functions). It is a specific type of change. A change may not touch the structure (introducing a measurement system), and a poorly managed reorganization may produce no real change in the way people work.
Change vs continuous improvement — continuous improvement (kaizen) is a permanent flow of small adjustments, built into the routine. Change is a discontinuous intervention, with a beginning, a peak of effort and a consolidation. The two are not mutually exclusive: there are companies with highly developed continuous improvement and no ability to manage change, and vice versa.
Change vs innovation — innovation introduces something new (a product, a technology, a market). Change concerns the transition from one way of working to another, regardless of whether the end point is innovative. You can change without innovating (aligning with an existing industry standard) and you can innovate without managing to change (the new product is created but the organization doesn't absorb it).
The OECD finds that Italian micro-enterprises are about 30% less productive than their European counterparts and that small family-run businesses often lack the scale for research, management skills and incentives to adopt technology [1]. The figure is not deterministic: many small Italian companies manage complex change effectively. But the lack of method — not of will — is the factor that separates projects that reach consolidation from those that dissolve halfway.
Diagnosing readiness for change before you start
If the planned change started next Monday, how many people in the company could say exactly why it's starting and what will change in their work? When the answer is "the founder and maybe a couple of managers," the project isn't ready — it's waiting for a preparatory phase that often gets skipped.
How many change projects fail to reach the finish line is not known: the figure circulating in the literature has no survey behind it [5][6]. What is observed in practice, however, is recurrent, and concerns the cause more than the frequency: changes that stall rarely stall on the quality of the technical solution chosen, and almost always on underestimating the organization's starting point.
A quick diagnostic grid in five dimensions, observable in a business owner's working week:
| Dimension | Diagnostic question | Green signal | Red signal |
|---|---|---|---|
| Clarity of the goal | Is the goal of the change worded in a way that can be verified? | "Reduce order fulfillment time from the 3rd to the 1st business day within 6 months" | "Improve processes" |
| Guiding coalition | Are there two or three key people — besides the founder — who actively support the change? | Yes, with visible roles and behaviors | No, or only under hierarchical pressure |
| Absorptive capacity | Do the departments involved have operational bandwidth available for the change? | Workloads allow time to be devoted to the transition | Teams are already at their limit; any additional request causes quality to drop |
| Quality of current management practices | Do meetings produce decisions? Are the main processes documented? | Yes, for at least 60–70% of critical activities | No, most things happen through informal agreement and individual memory |
| Measurement in place | Is there a system, even a simple one, to measure whether the change is progressing? | At least three verifiable indicators on a monthly basis | No agreed metric; the evaluation will be subjective |
The Bank of Italy, in a survey of about 3,200 Italian companies with at least twenty employees, finds that the adoption of structured management practices — monitoring indicators, setting goals, results-based incentives — goes hand in hand with higher productivity [2]. This association is not causal in the strict sense — the authors state that the analysis is purely descriptive: it suggests that companies with more structured practices tend to be better able to manage transitions, but every situation has its own specifics.
A four-phase operational framework for managing change
What is the smallest possible scope in which you could test the change, in two to three months, without paralyzing the rest of operations? When this question goes unanswered, the project is usually starting from too many points at once — and that is already a risk signal.
Management literature offers several models. The best known in academic circles is Kotter's eight-step sequence (1996), alongside Hiatt's individual ADKAR model (2003); both are useful conceptual references, but designed for large companies. The framework proposed here has four phases calibrated to the decision-making scale of smaller companies.
Phase 1 — Diagnosis and change contract
Indicative duration: 4 weeks.
The goal is to share a diagnosis of the problem and define the terms of the change so that you can verify whether it has happened. The output of this phase is a short document (one or two pages) that answers: why we are changing now, what specifically will change, who is responsible, how we will measure progress, and under what conditions we are willing to stop and correct course.
This document is discussed with the key people before the project starts, not circulated for information once the project is underway.
| Output | Metric | Condition for postponing |
|---|---|---|
| Shared diagnosis document | Signed by the founder and at least 2 key managers | No agreement on the causes: resolve the disagreement before signing |
Phase 2 — Pilot in a limited scope
Indicative duration: 6–12 weeks.
The change is applied to a subset of the organization: a department, a product line, a team, a process cycle. The pilot is not a lab test: it is a real application within a contained scope, with systematic observation of the difficulties.
Process mapping is useful in this phase: mapping the process in the pilot scope before and after the change makes the real differences visible. The link with business systemization is structural: changes consolidate more quickly in companies where processes are already documented.
| Output | Metric | Condition for postponing |
|---|---|---|
| Pilot report with problems and adjustments | At least 3 success signals defined in advance | If no success signal is observable, redesign before scaling |
Phase 3 — Scaling with short review meetings
Indicative duration: 12 weeks.
The model tested in the pilot is extended to the whole organization, with the adjustments learned along the way. Short review meetings (not "rituals" — too evocative a word for an ordinary work context) serve to collect signals in real time: what's working, what isn't, where the change is meeting unreported resistance.
Communication in this phase is not a separate activity: it is built into execution. The cluster on effective business meetings describes how to structure these meetings so they produce decisions, not just updates.
Phase 4 — Consolidation
Indicative duration: 6–12 months.
The change is consolidated when the new way of working has become standard practice, and newcomers to the company learn the new way from the start without having to adapt. Signs of consolidation: written procedures reflect the new way of working, metrics show stability, new hires receive no instructions about the "old way."
Communicating change to the team without being misunderstood
If a team member told a family member tomorrow what is changing at work, how closely would their version resemble the founder's? The gap between the two versions is the most underrated metric of change — and in many companies, before any change management effort, it is beyond the warning level.
The point at which most change projects lose traction is not the launch: it's the first week of execution, when the founder's message reaches the team filtered through one or two layers and becomes something different.
Three principles of internal communication during change:
The "why" before the "how" — people accept change more easily when they understand why it is happening, before receiving instructions on how to adapt. Communication that starts from the "how" (new procedures, new tools, new hours) without establishing the "why" creates resistance even when the change is rationally reasonable.
Frequency beats perfection — imperfect weekly communication is worth more than perfect monthly communication. A lack of updates is read as a lack of clarity, or worse, as deliberate opacity. It's a good idea to communicate even when there's no news: "The project is proceeding as planned; next week we'll share the pilot data."
Keeping an eye on informal talk — in every organization, information travels through formal and informal channels. Hallway rumors fill the gaps left by official communication. Whoever manages the change must be aware of these channels and actively keep them consistent with the formal message.
The three-channel operational plan for communicating change in a company:
All-hands meeting (1–2 a year, at crucial moments of the project): presenting the why, sharing the diagnosis, open questions. Goal: build shared understanding.
Department meeting (monthly or every two months): an update on the status of the change for the specific team, adapting the message to the local context. Goal: answer the group's operational questions.
One-on-one conversations with key roles (periodic, as needed): individual conversations with the people who shape the team's climate. Goal: pick up signals that aren't voiced in group meetings.
Adopting new technologies — a particularly common change among Italian companies, with 48.8% having adopted ERP and 21.1% CRM according to ISTAT (2025) [3] — calls for especially careful communication in the scaling phase: people tend to resist not the tool itself, but the uncertainty about how the new tool will change their daily work.
Measuring the progress of change (and correcting along the way)
Is there currently an agreed indicator whose drop below a threshold would automatically stop the project and reopen the diagnosis? When the answer is no, the change isn't proceeding by measurement: it's proceeding on the momentum of whoever launched it.
A change project without measurement is a statement of intent. The three families of indicators for measuring progress:
Adoption indicators — who is really using the new way of working? They can include: the percentage of people using the new process in the first two weeks, a number of support requests that decreases over time (a sign that the team is becoming self-sufficient), how often the tools introduced are used.
Outcome indicators — what has changed in the process numbers? They can include: average order fulfillment time before/after, number of operational errors per week, hours devoted to specific activities. Among the management practices the Bank of Italy finds associated with higher productivity is the monitoring of performance indicators, both in number and in frequency of review [2]: measuring the outcomes of change lets you connect the organizational investment to operational results.
Climate indicators — how is the organization reacting? They can include: the number of problem reports (high in the first weeks, then decreasing, is a positive sign), the quality of feedback gathered in department meetings, informal signals about the tone of internal conversations.
How the indicators are structured in practice:
| Indicator | What it measures | Cadence | Correction threshold |
|---|---|---|---|
| % of people using the new process | Adoption | Weekly | If below 60% at 30 days, reopen communication |
| Average completion time [key activity] | Operational outcome | Monthly | If above baseline at 60 days, review the procedure |
| Open problem reports | Climate | Weekly | If steadily increasing after the first month, diagnose the cause |
The link with the cluster on business KPIs is direct: change indicators fit into the company's measurement system, not as a temporary exception but as part of ordinary management oversight. The link with business performance measurement is just as relevant for the consolidation phase.
Avoiding the mistakes that make a change fall back before it shows results
Is there a change project in the company, launched in the last two years, that nobody can say for sure is still underway? If so, the problem isn't people's laziness: it's that the project was never declared finished, postponed or corrected — and that's the first of six mistakes to catch before they become structural.
Change costs the business owner time, attention and relational capital. Doing it badly uses them all up without delivering results. European micro-enterprises are projected to operate in 2025 at about half the productivity of large companies [4], and the figure that recurs in the literature for change projects that fail to reach their stated goals [5] rests on no verifiable survey, whether of Italian companies or anywhere else [6]. In this context, mistakes aren't accidents along the way: they are factors that compound.
| Mistake | Early warning sign | Practical fix |
|---|---|---|
| Launching to imitate the industry | There is no verifiable goal; the change is happening "because the competition is doing it too" | Before launch, word the goal so it can be verified at 90 days |
| Saturation from parallel initiatives | Several simultaneous changes with no stated priority; the team doesn't know what to focus on | Sequence them: one change at a time, with a consolidation phase before the next |
| Delegating the project only to the HR or operations manager | The founder isn't visible in the project; the team sees the change as a marginal initiative | The founder must be the main voice of the "why" in the early communications |
| No correction point | The project carries on even when signals show it isn't working | Define in advance the indicators and thresholds that authorize correction |
| One-off communication | A single initial announcement; then silence until the end of the project | Set up a regular update cadence for the entire duration of the project |
| Missed consolidation | The change is declared complete but old habits return after 2–3 months | Define the signs of consolidation and don't close the project until they are observable |
Limits and conditions of applicability
The four-phase framework is designed for medium-scale organizational changes — introducing a new process, changing an IT system, reorganizing a department, revising the sales model — in companies with at least five to ten people involved.
Contexts in which the framework requires significant adaptation:
Acute crises — in a liquidity or market crisis, the priority is operational survival, not structured management of the transition. In these cases, the framework shrinks to phase 1 (rapid diagnosis) and emergency communication.
Externally imposed changes with a hard deadline — regulations, certification requirements, tax obligations. In these cases the pilot phase isn't feasible: the change must happen by a fixed date. The framework focuses on preparation and communication.
Micro-businesses with fewer than five employees — in these contexts, change almost always happens informally and structured management may be out of proportion. A preparation checklist and a direct conversation with the people involved are preferable.
The 70% failure figure for change projects is not a measured finding. The source that reports it [5] in turn cites it from a strategy textbook, and the review that traced five separate appearances of it concludes that «there is no valid and reliable empirical evidence to support such a narrative» [6]. In this article it is cited as a widespread story whose lack of substance is worth knowing, not as a quantitative reference: an earlier version presented it as an indicative estimate applicable to smaller companies, and that presentation has been corrected.
FAQ
Is switching management software an "organizational change" that requires this approach? It depends on the scale of the switch. If the new system changes the workflows of more than three or four people and requires redefining established processes, yes: it deserves a structured approach with diagnosis, pilot and communication. If it's a version upgrade that doesn't change operating habits, no.
How long should a change project last in a company? A medium-scale change typically takes six to eighteen months from diagnosis to consolidation. Timelines shorter than three months leave almost no room for the pilot phase. Timelines longer than twenty-four months signal that the scope was too broad or that initial readiness was insufficient.
How do you handle people's resistance? Resistance is almost always a sign of insufficient information, not of opposition to change as such. People resist when they don't understand the why, when they fear losing something, when they don't see how the change applies to their specific work. The answer isn't to force it: it's to communicate better, listen to concerns and adapt the project where possible.
Operational summary
The operational path for managing change in a company: (1) word the goal so it can be verified; (2) run the readiness diagnosis across five dimensions; (3) build the diagnosis document and share it with the key people; (4) define the smallest pilot scope that lets you observe real signals; (5) run the pilot with systematic observation; (6) communicate at a regular cadence throughout the project; (7) define indicators and correction thresholds before starting to scale; (8) don't declare the change complete until the signs of consolidation are observable.
Conclusion
Well-managed change is not change that proceeds without friction. It is change that absorbs friction without dissolving: it reaches consolidation because it was prepared, measured and corrected along the way, not because whoever launched it held on longer than everyone else.
The institutional surveys cited here form a consistent picture. The adoption of structured management practices goes hand in hand with higher productivity in Italian companies with at least twenty employees [2]. European micro-enterprises remain at about half the productivity of large companies [4]. On the share of change projects that fail to reach their stated goals, by contrast, there is no survey: the figure in circulation has no verifiable empirical basis [5][6]. In a context like this, change management stops being a big-company specialty: it becomes everyday oversight, accessible even at a small scale, buildable step by step.
The common thread of this guide is a renunciation: giving up the "big project" and adopting a sequence of sustainable interventions — diagnosing readiness before starting, choosing a defensible pilot scope, communicating the "why" before the "how," measuring with a few indicators whose drop authorizes correction, avoiding the mistakes that make the project fall back before it shows results.
To place change within the broader architecture of the company, the reference is the pillar on business organization. To integrate it with the flow of continuous adjustments that keeps the results achieved alive, the cluster on continuous improvement describes its everyday practices. For the system of meetings that supports the scaling phase, the cluster on effective business meetings is useful.
A company that really manages its changes sees projects that reach the end, not the middle. It sees team members who, facing the next transition, ask "how do we tackle it" instead of "do we tackle it." It sees the business owner come back from a trip to find the pilot already scaling, rather than falling back. It's a concrete projection, not a promise: it depends on the discipline of the method, not on the energy of whoever leads it. And methods, unlike energy, don't run out.
{ "tipo": "immagine-interna", "posizione": "dopo H2-2 (griglia di prontezza al cambiamento)", "descrizione": "Infografica a griglia 5×2 che mostra le cinque dimensioni di valutazione della prontezza al cambiamento (urgenza esterna, consenso interno, risorse disponibili, capacità di esecuzione, meccanismo di feedback) con una scala visuale a tre livelli per ciascuna (bassa/media/alta prontezza). Stile: minimal, palette navy #090A3A e coral #FF5137, font Montserrat. Sfondo bianco. Dimensione: 1200x630px.", "alt": "Griglia di prontezza al cambiamento per PMI: 5 dimensioni di valutazione", "formato": "PNG", "priorità": "alta" }
{ "tipo": "immagine-interna", "posizione": "dopo H2-3 (framework operativo in 4 fasi)", "descrizione": "Diagramma a flusso orizzontale in 4 fasi del framework di gestione del cambiamento (Diagnosi / Progettazione / Esecuzione pilota / Scaling). Ogni fase ha un'icona, i principali output e la durata indicativa. Le fasi sono collegate da frecce con un loop di feedback dalla fase 3 alla fase 2. Stile: minimal, palette navy e coral, font Montserrat. Dimensione: 1400x500px.", "alt": "Framework gestione del cambiamento aziendale in 4 fasi per PMI", "formato": "PNG", "priorità": "alta" }
Sources and references
[1] OECD, "Economic Surveys: Italy 2024", OECD, January 2024. Italian micro-enterprises are about 30% less productive than their European counterparts; for small family-run businesses, the report points to a lack of scale for research, management skills and incentives to adopt technology. Available at: https://www.oecd.org/content/dam/oecd/en/publications/reports/2024/01/oecd-economic-surveys-italy-2024_18011b9d/78add673-en.pdf
[2] Baltrunaite, A., Formai, S., Linarello, A., Mocetti, S., "Proprietà, governance, management e performance delle imprese", Banca d'Italia, Questioni di Economia e Finanza no. 678, March 2022. Invind 2019 survey of about 3,200 manufacturing and service companies with at least 20 employees; structured management practices (monitoring, goals, incentives) are positively associated with productivity, with an analysis stated to be purely descriptive. Available at: https://www.bancaditalia.it/pubblicazioni/qef/2022-0678/QEF_678_22.pdf
[3] ISTAT, "Imprese e ICT — Anno 2025", Italian National Institute of Statistics, 2025. Available at: https://www.istat.it/comunicato-stampa/imprese-e-ict-anno-2025/
[4] European Commission, JRC, "Annual Report on European SMEs 2024/2025, SME Performance Review", Publications Office of the European Union, 2025. In 2024 the EU non-financial business sector had about 26.1 million small and medium-sized enterprises (99.8% of companies); their real value added fell by 0.2% in 2024, with a recovery of +1.6% expected in 2025, and micro-enterprises are projected to operate in 2025 at about half the productivity of large companies. Available at: https://publications.jrc.ec.europa.eu/repository/handle/JRC142263
[5] By, R. T., "Organisational change management: A critical review", Journal of Change Management, 5(4), 369-380, 2005. Available at: https://doi.org/10.1080/14697010500359250 — the 70% figure appears there as data reported from a third-party source (Balogun and Hope Hailey, 2004), not as a finding of the article.
[6] Hughes, M., "Do 70 Per Cent of All Organizational Change Initiatives Really Fail?", Journal of Change Management, 11(4), 451-464, 2011. DOI 10.1080/14697017.2011.630506. Record and abstract on the University of Brighton's institutional repository: https://research.brighton.ac.uk/en/publications/do-70-per-cent-of-all-organizational-change-initiatives-really-fa/ — «This paper critically reviews five separate published instances identifying a 70 percent organizational change failure rate. In conclusion, whilst the existence of a popular narrative of 70 percent organizational change failure is acknowledged, there is no valid and reliable empirical evidence to support such a narrative.»