What does a digital transformation lead actually do?

The supplier portal is ready. Suppliers still call Finance because its status does not match the payment system. Purchasing thinks Finance owns the fix. Finance thinks IT does.

A transformation lead needs to bring that disagreement to a decision. Until the teams agree which record to use and who handles discrepancies, the portal cannot give suppliers a reliable answer.

A digital transformation lead coordinates changes to how an organisation works with digital technology. The role connects the intended business result with process design, technical delivery, people and follow-up. Its authority varies by organisation; the title alone does not confer a budget or control over every team.

The transformation strategy note explains how to choose the work. Here, the question is who keeps the pieces connected once several teams must change together.

Start with an operating result

In our fictional distributor, the aim is to give suppliers reliable invoice and payment status through one service. That needs an agreed status definition, current records, an exception route and someone who can answer when the portal is wrong.

The transformation lead brings Purchasing, Finance, IT and supplier support together to define that service. They ask which status is authoritative, what delay is acceptable and which cases still need a person.

A useful result might be fewer unresolved status enquiries without incorrect payment information. The operating owner needs to choose the measure and baseline before the project claims a benefit.

Separate coordination from decision authority

Role in this example	Responsibility
Sponsor	Approves the outcome, funding and major trade-offs within their authority
Transformation lead	Connects the work, exposes conflicts and prepares decisions across teams
IT owner	Accepts the integration, access controls, reliability and technical support
Finance process owner	Owns the payment-status definition and the continuing service
Team managers	Allocate people and support the changed work in their teams

APM's project-management guidance connects delivery with requirements, resources, stakeholders and controlled closure. Its lifecycle guidance also distinguishes adoption and benefits beyond delivery. The role allocation above applies that separation to this example; it is not an APM standard job description.

The lead may also act as programme manager in a smaller organisation. That still needs clear delegated authority. The project, program and portfolio guide explains those different levels of decision.

Show the skill through a decision

The work calls for more than technical fluency or good presentations. Each skill needs something concrete to do.

Skill	What it helps settle here
Process understanding	Follow an invoice from receipt to payment and locate conflicting statuses
Data judgement	Decide which record supports the supplier-facing status
Technical understanding	Ask how updates, failures and access controls will work
Delivery coordination	Sequence definitions, integration, testing and staff preparation
Facilitation and negotiation	Resolve conflicting priorities without concealing the trade-off
Benefit and adoption review	Check correct service use and the operating outcome after launch

This assignment calls for the skills above. Work in healthcare or factory control also needs the relevant specialist knowledge and approvals; the role title does not supply them.

Data governance is relevant when “which status is right?” has no owner. A RACI matrix helps document the agreed responsibilities, once the people with authority have accepted them.

Make the exception route part of delivery

Suppose a supplier sees “paid” while Finance has only scheduled payment. The lead brings the definition conflict into the design and test plan. The team corrects the status meaning and agrees who handles any remaining discrepancy.

That may mean delaying a feature rather than letting an inaccurate message reach more suppliers. The sponsor needs the consequence, options and decision date. Any revised requirement needs the owner's agreement and an updated acceptance test.

During rollout, teams practise exceptions and know whom to ask. The change-management guide explains why training on the ordinary screen is only part of adoption.

Keep ownership after the project team moves on

At handover, Finance accepts the service measure, IT accepts support and the managers confirm cover. The benefit review follows unresolved enquiries, incorrect statuses and total handling effort, including the extra checking the portal may require.

If fewer calls simply mean suppliers cannot find the contact route, the headline has improved while the service has worsened. The lead needs evidence of the intended result, with the process owner responsible for sustaining it.

Before the project team leaves, the lead checks that Finance and IT have accepted their parts of the service, including the unresolved cases. That is how coordination carries through into an operation people can maintain.

Sources and example notes

• APM: Project management, delivery responsibilities and acceptance.
• APM: Life cycles, adoption and benefits.

The distributor, portal and division of responsibilities are fictional. Organisations assign this role different authority and responsibilities.