Digitisation and transformation
| Digitisation | Transformation | |
|---|---|---|
| What changes | The medium | The process |
| Example | A leave form becomes an online leave form | Leave is approved automatically within policy, with exceptions routed |
| Typical result | Same steps, faster, fewer lost forms | Fewer steps, and some decisions no longer made by a person |
| Risk | Existing flaws are preserved and accelerated | Requires deciding what to stop, which is politically harder |
Both are legitimate. Digitisation delivers real benefits: fewer lost documents, an audit trail, remote access, and data that can be reported on.
The problem is describing it as transformation and then being disappointed that the organisation did not change. A five-step approval chain that becomes a five-step online approval chain has been digitised, and the reason it is still slow is that nobody removed a step.
Why HR programmes stop at digitisation
The reason is not ignorance. It is that digitisation is possible without anyone giving anything up, and transformation is not.
Removing an approval step means telling an approver they are no longer required. Automating a decision means accepting that some judgement is now a rule. Consolidating systems means a team losing the one they chose. Each requires a decision someone will resist, and the safe route is to keep every step and put it on a screen.
The tell is a project scoped around implementing a system rather than around changing an outcome. A programme whose goal is to deploy a platform will deploy a platform; a programme whose goal is to halve the time to hire may or may not need one.
The corrective is to specify what will stop, in advance, as part of the business case. Anything the organisation is unwilling to name at that point it will be unwilling to remove later, under delivery pressure.
The workforce that decides whether it worked
HR technology is usually specified by people with laptops, in offices, with good connectivity, and it is evaluated on how it works for them.
A large share of the workforce in most Indian organisations is not in that position: field staff, site workers, shift workers, and people whose only device is a personal phone on a metered connection.
- Test on a mid-range phone on a slow connection, not on a laptop in an office.
- Assume no company email address, since processes routed through one exclude a large population by design.
- Check what the experience is in the languages the workforce actually uses.
- Ask whether someone can complete the task while standing on a site, which is where they will be doing it.
Where this is not done, the programme reports adoption in head office and silence elsewhere, and the silence gets read as disengagement rather than as exclusion.
This population is also the one for whom the benefit is largest, because they are the people currently dealing with paper, WhatsApp messages and a supervisor who forgot.
Data quality decides what is possible later
Most of what organisations want from HR technology, being analytics, prediction and automation, depends on data that is accurate, complete and historical.
Programmes routinely migrate whatever exists, discover its condition afterwards, and build reporting on top of records that disagree with each other. The output looks authoritative and is not.
- Assess data quality before migration and decide what will be corrected rather than carried.
- Preserve history where it exists, since most useful analysis is about change over time and cannot be reconstructed later.
- Establish field ownership at migration, because that is when it is cheapest to settle.
- Do not build reporting on data nobody has validated, since a wrong number presented confidently is worse than no number.
The second point is the one that cannot be recovered. History not migrated is generally history lost, and its absence is discovered years later when someone asks a question about a trend.
Measuring it honestly
Transformation programmes are measured on delivery, which is a measure of activity.
Systems launched, modules deployed, users onboarded and processes digitised all describe what the programme did. None describes whether the organisation works differently.
- What stopped: steps removed, forms retired, systems decommissioned, manual reconciliations ended.
- Time from request to outcome for the processes in scope, measured before and after.
- Adoption by the least-connected population, not the aggregate.
- Effort released, and whether it was actually redeployed or simply absorbed.
- Error rates in the outputs that matter, principally payroll.
The first is the most revealing and the least often reported. A programme that launched four systems and decommissioned none has added to what the organisation maintains, whatever else it achieved.
Frequently asked questions
What is digital transformation in HR?
Redesigning how work is done using digital capability, as opposed to digitisation, which moves an existing process onto a screen unchanged. Most programmes described as transformation are digitisation.
What is wrong with just digitising a process?
Nothing, provided it is called that. The problem is expecting organisational change from it. A five-step approval that becomes a five-step online approval is still slow, because nobody removed a step, and digitising a flawed process makes it faster rather than better.
Why do HR digital programmes stop short of transformation?
Because digitisation requires nobody to give anything up and transformation does. Removing an approver, automating a judgement or consolidating systems each requires a decision someone resists, so the safe route is to keep every step and put it on a screen.
How should adoption be measured?
By the least-connected part of the workforce rather than in aggregate. Field, site and shift staff are usually the population with most to gain and the least likely to be considered during specification, and their silence gets misread as disengagement rather than exclusion.
What is the most useful measure of a transformation programme?
What stopped: steps removed, forms retired, systems decommissioned, reconciliations ended. A programme that launched four systems and decommissioned none has added to what the organisation maintains.
How Engage reaches the whole workforce
Engage delivers leave, attendance, payslips and requests through a mobile app that works without a company email address, so the part of the workforce furthest from head office is not excluded by design. Because process usage is reportable by team and location, adoption can be read where it is weakest rather than in aggregate.
See Engage on mobile