AI strategy starts with the decisions that matter
Build an AI investment agenda around consequential decisions and the capabilities behind them.
Insights
Clear thinking for
a changing enterprise.
Strategy, enterprise architecture, Industry 4.0, AI, supply chains, and the organisational choices that connect them.
Agentic AI needs an authority model
Treat delegated action as an organisational design decision, with explicit limits and accountable owners.
AI needs a visible place in enterprise architecture
Introducing CEAF as a conceptual contribution from my graduate work, with a clear account of its limits.
Decide when a workflow should become agentic
A practical way to decide whether a task needs an AI agent, a defined workflow, or simpler automation.
Budget for the whole AI capability
Make the full cost and recurring ownership of an AI service visible before approving its expansion.
Measure AI value at the level of work
Move AI evaluation from usage and generated output to the performance of the complete workflow.
Choose applications through the operating model
Use a realistic business journey to expose organisational misalignment before choosing an application.
Design recovery before choosing infrastructure
Bring recovery responsibilities and operational consequences into infrastructure decisions before purchase.
Application retirement is part of the investment decision
Plan the exit from old applications and shadow processes before funding their replacements.
Systems thinking starts with the boundary of the problem
Use end-to-end work and feedback to move beyond a departmental explanation of recurring problems.
Shared metrics need shared operating definitions
Use a shared definition of readiness to connect supply-chain measures with dependable execution.
Agile needs strategic stability
Distinguish useful adaptation from priority churn, and give Agile teams a dependable decision context.
Architecture should move with Agile teams
Make enterprise architecture a practical partner in incremental delivery and cross-team learning.
Delivery is done when the operation can use it
Build operational readiness into acceptance so delivered work can become dependable everyday practice.
Lead without authority through a credible coalition
A practical approach to creating commitment when the people involved report to different leaders.
Leadership listening is a design skill
Use listening to improve the design of a change and establish a shared understanding of what it requires.
Design people into the operating model
Treat employee capability and workload as part of the design of change, from the first proposal onward.
Middle managers translate strategy into daily choices
Strengthen the link between strategic intent, local execution, and the evidence that should travel back to leadership.
A north star must help people choose
Turn an inspiring direction into a practical guide for resource allocation, commitments, and everyday judgment.
A strategy needs a stopping rule
Make subtraction part of strategy execution and give initiatives an explicit basis for continuation.
Use the Star Model to design change that holds
Apply Galbraith’s organisation-design framework to diagnose misalignment and shape a practical transition.
Reward prevention as seriously as recovery
Examine how informal recognition and formal performance measures can strengthen or undermine a change.
A strategic PMO must challenge the project list
Connect project governance with capability priorities, dependencies, capacity, and the continuing case for investment.
Portfolio capacity is a strategic choice
Use Run, Grow, and Transform as a discussion about commitments and constraints, without treating a fixed allocation as a universal answer.
A project benefit needs an operating owner
Connect project investment with adoption, operating decisions, and evidence of realised value.
Roadmaps should make dependencies visible
Build roadmaps around enabling conditions, decision points, and the evidence needed to advance.
Choose the customer promise before expanding the factory
Connect market choice with production, supply, quality, and service decisions when building a manufacturing business in Africa.
Strategy shapes the organisation
A strategic choice becomes credible when the organisation’s structure, capabilities, and incentives support it.
Industry 4.0 must connect the factory to the strategy
Digital manufacturing creates value when connected technology improves the operating decisions that matter.
The AI revolution demands a redesign of work
AI creates organisational value when leaders redesign tasks, decision rights, and accountability around its actual capabilities.
Technology hype is a test of leadership judgment
Separate what has been demonstrated, what is assumed, and what the business would need to make an emerging technology useful.
Supply chain resilience needs decision rights
Visibility becomes useful when people can act on constraints, coordinate trade-offs, and protect the customer promise.
Africa’s manufacturing ambition needs businesses that can scale
Connect the market opportunity with the people, structure, and operating discipline needed to deliver it.
Capability models should guide investment
A capability map earns its place when it helps leaders decide what to strengthen, what to fund, and what to leave alone.
Enterprise architecture earns influence through decisions
An effective architecture practice helps leaders compare options, understand consequences, and commit to a course of action.
Evaluate technology against the business need
Use strategic fit, operating readiness, and a testable benefit to decide which technologies deserve investment.
Prepare for technology through capabilities
Build the foundations that let the organisation evaluate and absorb change without committing to every prediction.
Cloud security needs named owners
Translate shared responsibility into specific ownership for access, configuration, information, and response.
Security is an organisational capability
Resilience depends on the way leaders connect risk decisions, technical controls, people, and operating responsibilities.
Integration deserves enterprise ownership
Treat the movement of information and work across systems as a business capability with clear ownership.
Modernise infrastructure around service needs
Use business criticality, recoverability, and operating capacity to guide infrastructure investment.
Data creates value through decisions
Build data capabilities around a decision or service whose performance the organisation can improve.
Fragmented data creates an organisational cost
Repeated reconciliation is a signal to examine ownership, definitions, and the architecture behind the work.
Composable ERP requires integration discipline
Modularity creates options when the business can govern the interfaces, information, and responsibilities between components.
API-first starts with a clear contract
Reliable integration depends on shared meaning, ownership, and failure handling as well as technical connectivity.
Cloud value depends on the operating model
Cloud services create options; the organisation must develop the practices that turn those options into useful results.
Small technology requests reveal design choices
An app or dashboard request can expose a deeper question about work, information, and decision rights.
Clarity comes before accountability
What leading a struggling operation taught me about the conditions people need to succeed.
What capability are we actually funding?
A practical question for connecting investment decisions to the way a business creates value.
Who owns the decisions between departments?
Why enterprise leadership has to reach beyond the boundaries of the organisation chart.
The collection includes revised editions of my 2025 writing on The Loop. Each revised article links to its original article and coursework bibliography.