Thinking · Technology and Transformation
Making technology useful in the system around it
Technology changes what an organisation can do. Its value depends on the problem being addressed, the service it supports and the decisions people make around it.
My work in transformation connects product direction, operational needs, data and delivery. I am interested in how an organisation moves from acquiring a technical capability to using it well.
Product and service direction
A product needs a clear account of whose problem it solves and what improvement matters. That direction helps a team make choices about priorities, scope and trade-offs.
I work with stakeholders to connect user needs with organisational objectives and practical delivery. This can involve examining a service journey, clarifying the purpose of a product or identifying what should be learned before committing to a larger change.
AI and practical adoption
AI creates opportunities in content, analysis, assistance and automation. The useful question is where it improves a task and how that improvement can be judged.
I am interested in the workflow around an AI tool: the information it uses, the quality expected, the person responsible for reviewing its output and the cost of operating it. Those questions help distinguish an attractive demonstration from a capability that can be used repeatedly.
Data and decisions
Data contributes value when people can understand it, trust it sufficiently for the decision and act on what it shows. A dashboard or risk indicator sits within a wider process of interpretation, ownership and response.
That makes definitions, data quality, access and the decision process part of the product conversation. I look at how the information moves through a service and what the user needs to do with it.
Operating models and ownership
The way an organisation makes decisions affects the performance of its technology. Teams need clarity about ownership, priorities and the relationship between policy, operations and digital delivery.
I am interested in operating models that make those relationships workable. The objective is a structure that supports decisions and learning in the actual service environment.
Legacy modernisation
Modernising a system requires understanding what the existing service does, what depends on it and how users and operations will move to the new arrangement. Migration, readiness and continuity are part of the change.
My experience in public services, healthcare and funding has involved those relationships between existing systems, new capabilities and the people who rely on them.
Control and dependency
Owning data is one part of retaining control over a technology service. Organisations also need to understand their ability to access it, move it, operate the service and change suppliers or components when necessary.
I explore how decisions about architecture, contracts and operational capability create or reduce dependency. The relevant choice depends on the value required and the organisation’s ability to sustain it.