Our Perspectives
Penn Advisory shares occasional perspectives on leadership, governance and decision-making in the context of AI, data, technology and transformation.
These reflections are written for boards, executive teams and senior technology leaders who want to think more clearly about complex change, investment choices and delivery risk.
What you can expect
The aim is not to offer generic commentary or fashionable opinion. Perspectives from Penn Advisory are intended to be practical, considered and grounded in real delivery experience.
Typical themes include:
- how boards can govern technology and AI-enabled change with confidence
- why major programmes fail, and what sponsors can do earlier
- the difference between digital ambition and deliverable transformation
- how to make better investment decisions in uncertain technology environments
- what senior technology, data and transformation leaders need from their organisations
Featured perspectives
- AI governance: asking better questions before approving investment
AI investment is accelerating, but many boards are still being asked to approve initiatives without sufficient clarity on value, risk, accountability or operating impact. This perspective explores the questions leaders should ask before committing resources. - Why transformation programmes drift — and how to spot it early
Large programmes rarely fail suddenly. They drift through unclear scope, weak governance, optimistic plans and unresolved decisions. This piece examines the early signs of drift and the practical interventions that can restore control. - The difference between digital ambition and deliverable transformation
Most organisations now have some form of digital ambition. Boards want better data, more efficient services, modern platforms, stronger customer or citizen experience, and the ability to take advantage of AI and automation. These ambitions are understandable and often necessary. This perspective examines the complementary nature of digital ambition and deliverable transformation. - Draft perspective: How to make better investment decisions in uncertain technology environments Technology investment decisions are becoming harder, not easier. Boards and executive teams are being asked to commit funding in environments shaped by rapid innovation, supplier volatility, AI disruption, cyber risk, legacy constraints, skills shortages and changing public or customer expectations. This piece considers how investment decisions need to be structured, and how decision making has evolved alongside technology.
- What senior technology, data and transformation leaders need from their organisations Senior technology, data and transformation leaders are being asked to do more than ever. They are expected to modernise legacy estates, strengthen resilience, improve data quality, enable AI, reduce cost, protect against cyber risk, support growth, and deliver complex change across organisations that may already be stretched. The organisation wants business value, pace and innovation, but the leader often has to work through fragmented governance, unclear ownership, constrained budgets, competing priorities and legacy ways of working. This perspective discusses what technology, data and transformation leaders should demand from their organisations.
AI governance - asking better questions before approving investment
AI investment is accelerating. Boards and executive teams are being asked to approve pilots, platforms, productivity tools and more ambitious transformation programmes at pace. The pressure to move quickly is understandable. AI is already changing how organisations work, serve customers, manage information and make decisions.
But speed is not the same as confidence. In many organisations, AI proposals reach the board before there is enough clarity on value, risk, accountability, data readiness or the operating changes required to make the investment worthwhile.
The board’s role is not to become expert in every model, tool or technical architecture. Nor is it to slow innovation unnecessarily. The board’s role is to ensure that AI investment is aligned to strategy, governed responsibly and capable of being delivered in a way that creates real organisational value.
The governance challenge
AI governance is often presented as a compliance issue. It is more than that. Good governance should help organisations make better decisions, avoid unmanaged risk and scale successful use cases with confidence.
Weak governance tends to show up in familiar ways: unclear ownership, optimistic benefits cases, limited understanding of data quality, fragmented experimentation, poor monitoring and uncertainty about who is accountable if outcomes are wrong, biased, unsafe or simply ineffective.
These are not purely technical issues. They are leadership, investment and operating model issues. That is why board-level challenge matters.
Seven questions boards should ask before approving AI investment
1. What problem are we solving, and why is AI the right answer?
AI should not be approved because it is fashionable or because competitors are investing. The proposal should identify a clear organisational problem, opportunity or service improvement. Boards should ask whether AI is genuinely required, or whether process improvement, better data, automation or clearer accountability would address the issue more effectively.
2. What value will this create, and how will we know?
Many AI initiatives promise productivity, insight or better decision-making, but the benefits are often difficult to measure. Boards should look for a credible value case, baseline measures, expected outcomes and a clear method for tracking whether benefits are actually realised. If the value cannot be described in operational or financial terms, the proposal may not yet be ready for approval.
3. Who owns the outcome?
AI governance fails when accountability is spread too thinly. Boards should ask who is accountable for the business outcome, who owns the risk, who can stop or change the initiative, and who is responsible once the system is live. A steering group may support governance, but it should not obscure personal accountability.
4. What data is being used, and is it good enough?
AI depends on data quality, access, context and control. Boards do not need to inspect datasets, but they should be satisfied that the organisation understands the source, quality, limitations and sensitivity of the data being used. Poor data can create poor decisions at scale.
5. What could go wrong, and how would we know?
The risk discussion should go beyond cyber security and regulatory compliance. It should include operational risk, bias, explainability, customer or citizen impact, reputational exposure, supplier dependency, workforce implications and the risk of over-reliance on automated outputs. Boards should also ask what monitoring will be in place after implementation.
6. What operating changes are required?
AI is rarely just a technology deployment. It may change processes, roles, decision rights, controls, skills, supplier relationships and customer interactions. Boards should be wary of investment cases that describe the tool but understate the organisational change needed to use it safely and effectively.
7. What assurance will the board receive?
Approval should not be the end of board involvement. For material AI investments, boards should agree what assurance they will receive, at what cadence and in what form. This might include benefit tracking, risk reporting, incident reporting, independent review, post-implementation assessment or evidence that controls remain effective as the system evolves.
What good looks like
Strong AI governance does not need to be bureaucratic. The best arrangements are usually clear, proportionate and embedded into existing governance, risk and investment processes.
For boards, good governance should provide confidence that:
- AI investments are linked to strategic priorities and measurable outcomes
- accountability is clear from approval through to live operation
- risks are understood, owned and monitored
- data, security, ethics and regulatory considerations have been addressed
- benefits are tracked after implementation, not assumed at approval
- the organisation can explain how AI-enabled decisions are made and governed
A better approval conversation
The most useful board conversations about AI are not dominated by technology detail. They focus on purpose, value, accountability, risk and readiness.
Before approving significant AI investment, boards should feel able to say: we understand why this matters, what value it is expected to create, who owns the outcome, what could go wrong, how the organisation will manage it and how we will know whether it has worked.
That is not a barrier to innovation. It is what allows innovation to proceed with confidence.
How Penn Advisory can help
Penn Advisory supports boards and executive teams in shaping AI governance, testing investment cases and providing independent challenge before major commitments are made.
If you are considering a significant AI investment and would value an independent perspective, please get in touch for an initial confidential conversation.
Why transformation programmes drift - and how to spot it early
Large transformation programmes rarely fail in a single moment. More often, they drift. The programme remains active, the governance calendar continues, workstreams report progress and teams stay busy. From a distance, everything can appear to be moving forward.
The problem is that activity is not the same as progress. A programme can consume time, money and senior attention while gradually moving away from the outcomes it was originally created to deliver.
Drift is dangerous because it is rarely dramatic at the start. It often appears as a series of individually reasonable adjustments: a milestone moves, a decision is deferred, a dependency becomes more complicated, scope expands slightly, a benefit is rephrased, or a difficult issue is carried forward to the next meeting.
What programme drift looks like
Programme drift is the gradual separation between the work being done and the outcome the organisation needs. It is not simply delay, and it is not always visible through standard status reporting.
In a drifting programme, the team may still be committed and working hard. Suppliers may still be delivering. Governance packs may still be produced on time. The concern is that effort is becoming harder to connect to value.
That is why drift often becomes visible first in the quality of the conversation, rather than in the dashboard. Leaders find it harder to explain what has really changed, what is blocked, what decisions are needed and whether the original business case still holds.
Why programmes drift
Most drift has familiar causes. They are rarely surprising, but they are often tolerated for too long.
1. The definition of success becomes blurred.
At the start, the programme may have a clear strategic intent. Over time, that intent can become diluted by new priorities, additional scope or competing stakeholder expectations. Teams remain busy, but people are no longer aligned on what success means.
2. Governance reports rather than decides.
Many governance forums are good at receiving updates but weaker at making timely decisions. Risks are noted, issues are discussed and actions are carried forward, but the difficult choices remain unresolved. When governance stops deciding, delivery teams compensate by working around the uncertainty.
3. Plans remain optimistic after the facts have changed.
Programme plans are often built around assumptions about capacity, dependencies, procurement, data, integration, user readiness and organisational appetite for change. When those assumptions prove wrong, the plan should be reset. Drift begins when the plan remains formally intact while everyone quietly works around it.
4. Benefits lose their owners.
Transformation programmes are often justified by benefits that sit outside the programme team: better service, lower cost, improved productivity, reduced risk or stronger operational resilience. If those benefits are not owned by business leaders and tracked through delivery, they can become detached from the work being done.
5. Difficult trade-offs are avoided.
Most major programmes eventually face trade-offs between scope, time, cost, quality and risk. Drift accelerates when leaders avoid making explicit choices. The programme then absorbs the tension through delay, complexity, rework or reduced confidence.
6. Technology becomes the programme.
Technology may be central to the change, but it is rarely the whole transformation. When attention narrows to the system, platform or implementation plan, organisations can underinvest in operating model design, process change, data quality, adoption, capability and benefits realisation.
Early warning signs
Programme drift is easier to correct when it is recognised early. Useful warning signs include:
- status reports remain positive, but the underlying evidence is thin
- the same risks or issues appear repeatedly without resolution
- key decisions are deferred from one governance meeting to the next
- scope changes are accepted informally rather than actively prioritised
- benefits are described generally but not owned or measured
- dependencies are escalating faster than decisions are being made
- senior leaders spend more time reviewing activity than testing value
- teams are busy, but stakeholders struggle to explain what progress means
None of these signs proves that a programme is failing. Together, however, they suggest that the programme may be losing coherence and needs sharper leadership attention.
How to restore control
Recovering from drift does not always require a full reset. Often, it requires a short, disciplined intervention that brings the programme back to purpose, value and decision-making.
Leaders should consider five practical steps.
1. Reconfirm the outcome.
Return to the original purpose of the programme and test whether it still holds. If priorities have changed, say so explicitly. Do not allow the programme to continue against an outdated or ambiguous mandate.
2. Reset the facts.
Establish the current position honestly: scope, cost, schedule, risks, dependencies, resource constraints, supplier performance, user readiness and benefits. A realistic baseline is essential before any credible recovery plan can be agreed.
3. Strengthen decision rights.
Clarify who can make which decisions, what needs escalation and what the programme should stop doing. Governance should create decisions, not just documentation.
4. Reconnect work to value.
Map the main workstreams back to the outcomes and benefits they are intended to deliver. If activity cannot be connected to value, it should be challenged.
5. Create independent challenge.
When a programme has been running for some time, internal teams may be too close to the detail to see the pattern. Independent review can help distinguish normal delivery complexity from deeper issues of scope, governance, capability or viability.
The board’s role
Boards and executive teams do not need to manage the programme day to day. They do need to ensure that the programme remains strategically relevant, realistically governed and capable of delivering its intended value.
The most useful questions are often simple:
- Are we still clear what success means?
- Are we making the decisions the programme needs?
- Are benefits still credible, owned and measurable?
- Are risks being managed or merely reported?
- Are we prepared to stop, pause or reset if the evidence requires it?
Conclusion
Transformation drift is not inevitable, but it is common. It emerges when purpose becomes blurred, governance loses its edge and activity becomes disconnected from value.
The earlier leaders recognise the pattern, the more options they have. The task is not to wait for failure, but to create the conditions in which honest assessment, timely decisions and practical recovery are possible.
Spotting drift early is one of the most important responsibilities of transformation leadership.
How Penn Advisory can help
Penn Advisory provides independent programme review, assurance and senior advisory support for organisations seeking to understand whether major transformation programmes remain aligned, deliverable and capable of realising value.
If a programme is beginning to show signs of drift, an early independent perspective can help leaders decide whether to continue, correct, pause or reset.
The difference between digital ambition and deliverable transformation
Most organisations now have some form of digital ambition. Boards want better data, more efficient services, modern platforms, stronger customer or citizen experience, and the ability to take advantage of AI and automation. These ambitions are understandable and often necessary.
But digital ambition is not the same as deliverable transformation. Ambition describes the future an organisation wants. Deliverable transformation explains how that future will be achieved, funded, governed, adopted and sustained.
The gap between the two is where many programmes struggle. The strategy may be compelling, the roadmap may look credible and the technology choices may be sensible. Yet the organisation may still lack the operating model, decision discipline, funding approach, delivery capacity or leadership alignment needed to turn aspiration into value.
Why ambition is not enough
Digital ambition often starts in the right place: a recognition that current ways of working are too slow, too fragmented, too costly or too dependent on legacy systems. Leaders can usually describe the prize clearly — simpler services, better insight, faster decisions, improved resilience or lower cost.
The difficulty is that ambition is usually expressed at a level of abstraction that hides the real work. It does not, by itself, resolve competing priorities, simplify processes, improve data quality, change behaviours, retire legacy systems or create accountability for benefits.
That is why organisations can have a strong digital vision and still find themselves running disconnected initiatives, overloading delivery teams and struggling to evidence progress.
What deliverable transformation requires
Deliverable transformation translates ambition into a set of practical choices. It answers not only what the organisation wants to become, but what must change for that to happen.
It requires clarity in seven areas.
1. Outcomes before initiatives.
The starting point should be the outcomes the organisation needs, not the projects it wants to launch. Initiatives should be prioritised because they contribute to measurable value, not because they appear attractive, modern or urgent.
2. Operating model before technology scale.
Technology will not compensate for unclear decision rights, fragmented ownership or outdated ways of working. Before scaling new platforms or digital capabilities, leaders need to understand how work will be organised, governed, measured and improved.
3. Architecture that enables choice.
Deliverable transformation needs a coherent view of systems, data, integration, security and legacy constraints. Architecture should help leaders make informed trade-offs, sequence investment and avoid creating new complexity while trying to remove the old.
4. Funding that matches uncertainty.
Many digital programmes are funded as if the full answer is known at the start. In reality, transformation often requires discovery, learning and adjustment. Funding models should allow discipline and control without forcing false certainty too early.
5. Governance that makes decisions.
Governance should not simply review progress. It should make choices, resolve conflicts, manage trade-offs and protect the link between work and value. If governance meetings only receive updates, transformation will slow.
6. Capacity and capability to deliver.
Ambitious strategies often underestimate the pressure placed on internal teams. Deliverable transformation needs realistic capacity planning, access to the right skills, credible supplier arrangements and leadership time to make decisions.
7. Benefits owned by the business.
Digital transformation should not be measured only by systems delivered or milestones achieved. Benefits must be owned by the business areas expected to change. Without that ownership, benefits remain promises rather than outcomes.
Signs that ambition is running ahead of deliverability
Leaders should pay attention when:
- the vision is clear, but priorities keep expanding
- roadmaps list initiatives, but do not show how value will be realised
- technology decisions are being made before operating implications are understood
- governance forums review updates but defer the difficult choices
- delivery teams are stretched across too many competing priorities
- benefits are described in general terms but lack named owners
- legacy constraints are acknowledged but not actively addressed
- progress is reported through activity rather than measurable outcomes
These are not reasons to abandon ambition. They are reasons to make it more deliverable.
The board’s role
Boards do not need to design the transformation in detail, but they should test whether the organisation has moved beyond aspiration into credible execution.
Useful questions include:
- What outcomes are we trying to achieve, and how will we measure them?
- What will actually change in the way the organisation works?
- Who owns the benefits, and are they accountable for realising them?
- What operating model changes are needed before technology can scale?
- What assumptions are built into the plan, and how will they be tested?
- Where are the biggest constraints: legacy systems, data, funding, skills, governance or leadership capacity?
- What would cause us to pause, reset or stop?
Conclusion
Digital ambition matters. It creates direction, energy and permission to change. But ambition only becomes transformation when it is connected to choices about value, governance, operating model, architecture, funding and delivery capacity.
The organisations that succeed are not necessarily those with the boldest vision. They are the ones that can translate ambition into disciplined execution and measurable outcomes.
The task for leaders is not to lower ambition. It is to make ambition deliverable.
How Penn Advisory can help
Penn Advisory helps boards and executive teams test whether digital strategies, investment plans and transformation roadmaps are realistic, prioritised and capable of delivering value.
If your organisation has a strong digital ambition and wants greater confidence in the route to delivery, Penn Advisory can provide independent challenge and practical senior advice.