Digitisation, digitalisation and transformation
Start by defining terms precisely, because they are often confused and markers notice.
| Term | Meaning | Example |
|---|---|---|
| Digitisation | Converting analogue information into digital form | Scanning paper patient records |
| Digitalisation | Using digital technology to improve existing processes | Online appointment booking |
| Digital transformation | Rethinking the business model, customer value and operations using digital capabilities, with organisational change | A manufacturer selling equipment-as-a-service with remote monitoring |
A transformation paper should be about the third level. If your recommendation only automates an existing process, call it digitalisation and justify why that is the right ambition.
Reading the brief
Digital transformation assignments come in a few forms. Identify yours before planning:
- Case analysis: evaluate a company's transformation, what worked and what did not.
- Strategy recommendation: propose a transformation strategy for a case or real organisation.
- Your own organisation: common in executive MBA programs; balance insider knowledge with confidentiality.
- Critical essay: evaluate a concept, such as why many transformations fail, using literature.
Assessing the current state
A strategy needs a baseline. Analyse:
- Strategic context: industry disruption, customer expectations, competitor moves; tools such as PESTLE and Five Forces help.
- Digital maturity: where the organisation stands across strategy, customer experience, operations, technology, data, culture and talent. Many consulting firms and researchers publish maturity models; cite the one you use.
- Capabilities and gaps: data infrastructure, legacy systems, skills, leadership commitment.
- Customer journey pain points: where digital could create the most value.
| Dimension | Questions to ask |
|---|---|
| Strategy | Is digital part of the corporate strategy or a separate IT plan? |
| Customer | How do customers prefer to interact, and where are the frustrations? |
| Operations | Which processes are manual, slow or error-prone? |
| Data | Is data accessible, trustworthy and used in decisions? |
| Technology | How flexible is the architecture? What legacy constraints exist? |
| People and culture | Do staff have digital skills? Is experimentation encouraged? |
Building the transformation strategy
Structure the strategy around business outcomes, then the capabilities and technologies that deliver them.
- Vision: what the organisation will do differently for customers, in one or two sentences.
- Strategic objectives: three to five measurable goals, for example "50% of sales through digital channels within three years".
- Priority initiatives: the projects that will deliver each objective, sequenced by value and feasibility.
- Enabling capabilities: data platforms, cloud, cybersecurity, digital talent, agile ways of working.
- Roadmap: phases, typically quick wins, foundation building and scaling.
Technology follows strategy
Name technologies (cloud, AI, IoT, automation) only where they serve a stated objective. "Implement AI" is not a strategy; "use demand forecasting to cut inventory costs by 15%" is.
| Phase | Focus | Example initiatives |
|---|---|---|
| 1. Quick wins (0 to 6 months) | Visible value, build support | Online self-service for common requests |
| 2. Foundations (6 to 18 months) | Data, platforms, skills | Customer data platform, staff upskilling |
| 3. Scale and new models (18 to 36 months) | New revenue and operating models | Subscription services, predictive maintenance |
The business case and KPIs
MBA markers expect financial reasoning. Estimate investment, benefits and timing, and state assumptions.
- Costs: technology, implementation, training, change management, ongoing operations.
- Benefits: revenue growth, cost savings, risk reduction, customer retention.
- Evaluation: NPV, payback or ROI; our valuation and DCF guide covers the methods.
| KPI type | Examples |
|---|---|
| Customer | Digital adoption rate, Net Promoter Score, digital channel conversion |
| Operational | Process cycle time, automation rate, error rate |
| Financial | Digital revenue share, cost-to-serve, return on investment |
| People | Digital skills coverage, employee engagement, attrition in key roles |
Leading the change
Research and practitioner surveys repeatedly point to people, culture and leadership, not technology, as the main reasons transformations stall. A strong paper devotes real space to change management:
- Leadership sponsorship and a clear governance structure.
- A change model such as Kotter's eight steps or ADKAR, applied to your case.
- Stakeholder analysis: who gains, who loses, who must be persuaded.
- Skills and talent: reskilling, hiring, partnerships.
- Ways of working: cross-functional teams, agile delivery, test-and-learn.
- Communication: a consistent story about why the change matters.
Our organizational change paper guide explains how to apply change models in depth.
Measuring adoption, not just delivery
A common weakness in transformation plans is measuring whether systems were launched rather than whether they are used. Include adoption measures, such as active users, share of transactions completed digitally and staff proficiency, and explain how the organisation will respond if adoption lags, for example through redesign, training or incentives.
Risks, governance and ethics
| Risk | Mitigation |
|---|---|
| Cybersecurity and data breaches | Security by design, regular testing, incident response planning |
| Data privacy and regulation | Compliance with applicable laws (for example GDPR where relevant), clear consent and data governance |
| Legacy integration failure | Phased migration, architecture review, pilot testing |
| Staff resistance | Involvement, training, visible early wins |
| Vendor lock-in | Open standards, contract terms, multi-vendor strategy |
| Ethical and bias risk in AI | Governance, testing for bias, human oversight |
A short worked example
Case (hypothetical): a regional insurer losing younger customers to app-based competitors, with claims handled by phone and paper forms.
| Element | Application |
|---|---|
| Current state | Low digital maturity in customer experience and data; claims take weeks; strong brand trust among older customers |
| Vision | "Insurance that settles simple claims in a day, on the customer's phone" |
| Objectives | Cut average simple-claim time from 14 days to 2; raise digital policy sales to a third of new business; reduce cost-to-serve |
| Initiatives | Mobile claims app with photo upload; automated triage of simple claims; customer data platform; staff reskilling for complex claims |
| Change | Kotter: urgency from customer loss data; guiding coalition of claims, IT and marketing leaders; early win from the app pilot |
| Risks | Fraud in automated claims (rules and audits); data privacy (governance); staff fears (redeployment plan) |
Notice that every initiative serves an objective, and the objectives respond directly to the problems found in the assessment. That chain of logic is what markers reward.
A paper structure that works
- Executive summary: the recommendation, investment and expected value.
- Introduction and definitions.
- Strategic context and current-state assessment.
- Transformation vision and objectives.
- Initiatives and roadmap.
- Business case and KPIs.
- Change management and governance.
- Risks and mitigation.
- Conclusion and recommendations.
- References and appendices.
Theories that strengthen the paper
- Dynamic capabilities (sensing, seizing, transforming): explains how firms adapt to technological change.
- Resource-based view: whether digital assets create sustainable advantage or are easily copied.
- Disruptive innovation: how new entrants use technology to unseat incumbents.
- Technology acceptance and diffusion of innovations: why users adopt or resist new systems.
- Business model frameworks such as the Business Model Canvas: how value creation and capture change.
Use one or two theories well rather than naming many briefly. Cite peer-reviewed sources and respected practitioner research, and treat vendor white papers with caution.
Mistakes to avoid
- A technology list Start from business outcomes and customer value.
- Ignoring people and culture Change management deserves substantial space.
- No business case Estimate costs, benefits and timing with stated assumptions.
- Vague KPIs Use measurable indicators with baselines and targets.
- Generic recommendations Tie every initiative to the specific case evidence.
- Uncritical sources Vendor marketing is not evidence; balance it with academic research.
Checklist before you submit
- Are terms defined and the level of ambition clear?
- Is the current state assessed with evidence?
- Do objectives and initiatives link to business outcomes?
- Is there a phased roadmap?
- Is there a business case with KPIs?
- Is change management addressed with a named model?
- Are risks, governance and ethics covered?
- Is theory applied, not just mentioned?
If you are working to a deadline and want expert help, you can order MBA strategy paper help.