What a digital transformation programme actually involves

Start from the service, not the system

Pick the service that matters most to the people you serve or to your mandate: issuing a licence, registering a beneficiary, paying a supplier, reporting to a funder. Describe it end to end as it happens today, including the parts done on paper, by phone or by walking a file across the building. That map is the programme’s starting point.

Put the data in order first

Every digital service depends on a registry: of citizens, beneficiaries, facilities, assets, cases or accounts. If the registry is duplicated across spreadsheets with different spellings, the software will faithfully digitize the confusion.

• Decide which registry is the source of truth for each kind of record
• Agree identifiers: national ID, phone number, facility code
• Clean and deduplicate before migration, not after
• Decide who may create, change and retire a record

Digitize one workflow end to end

A first phase that takes one workflow fully digital, including approvals, reporting and the back office, teaches the organization more than a broad system that digitizes every form halfway. It also gives staff a success to point to.

• Choose a workflow with a clear owner and visible pain
• Include the approval and the report, not just the data entry
• Run it in parallel with the old process for a defined period
• Retire the paper version on a date, formally

Connect; do not replace everything

Existing systems that work should be connected, not rebuilt. Payroll, accounting, a ministry reporting platform or a donor’s system usually stays. The new system should exchange data with them through documented interfaces so information is entered once.

Plan for people, not just software

The budget lines that get forgotten are the ones that decide adoption.

• Devices and connectivity for the staff who will use the system daily
• Training by role, repeated as staff change
• A named internal owner with time allocated to the programme
• Help for the first months: someone to call when a case does not fit the form
• Change to procedures, forms and sometimes regulations

Build the back office from day one

Roles, approvals, audit trails and reports are not phase two. Without them, managers cannot trust the system, auditors cannot check it, and staff work around it. Every system we build ships with its back office in the first version.

Sequence in phases you can finish

A phase should be short enough that the organization can see it finish and long enough to deliver a complete workflow. Each phase ends with something in daily use, documented and supported, before the next begins.

Measure what the service delivers

Pick a few measures before the work starts: time to issue a document, cases closed per month, reports produced without manual compilation, complaints. Track them from the old process onward so the programme can show what changed.

Where we fit

We run discovery, design the solution and the phases, build and integrate the systems, train staff and support the result. For institutions, we also work within tender and procurement processes. The digital-transformation service page describes the engagement; the procurement checklist lists what we provide for a tender.