Leading through uncertainty: six questions for digital leaders

The pressure on leaders is not simply to adopt more technology. It is to make better choices while risks, expectations and ways of working change at the same time. These questions can structure a useful conversation between business, technology, security and people leaders.

1. What is the decision?

Start with the outcome and the work. Which customer or employee problem matters most, what changes in the workflow, and who remains accountable for the result? An AI use case is only useful when it belongs to a clear operating decision.

2. What must remain dependable?

Treat resilience as part of transformation planning. Ask which data, identities, suppliers and processes the change depends on, and who can act when one of them fails. The security function should shape choices early, while specialist testing and assurance stay with qualified practitioners.

3. Who needs to understand and act?

Make adoption visible. Employees know where workarounds, friction and tacit knowledge live. Involve them in discovery, teach the judgement the new system requires and use feedback to revise the plan. A policy that nobody can use is not yet an operating practice.

4. Where should investment begin?

Invest where a failure would interrupt the most important work. Map critical services and dependencies, then improve the basics that support them: access ownership, awareness, response roles and the ability to recover. A security specialist should test and validate technical controls.

5. How does governance stay useful?

Ask what the organisation needs to document, review and decide, and which requirements apply to its actual use case. Build a review cadence that can adapt as guidance and products change. Legal interpretation belongs with qualified counsel; the operating model must still be usable by the people doing the work.

6. What must leaders learn?

Leaders need fluency across disciplines: enough technology understanding to ask good questions, enough security and governance awareness to see dependencies, and enough empathy to learn how change lands with employees. Their job is to make trade-offs explicit and keep learning visible.

A useful first move

A practical next step is a short cross-functional review: choose one priority, name the decision owner, map the human and technical dependencies, agree what evidence would change the decision, and set a date to learn from it.

This is a discussion framework, not a legal assessment or technical security review. The linked Institute sources are starting points for further reading.