This page helps place the type of intervention, the people involved and the elements that may be delivered within the agreed scope.
We start by looking at the issue, what already exists and the right level of support. The choice of tool or technology comes next, if it genuinely helps move the work forward.
When tools, accounts, information and decisions need a clear operating framework.
We frame the important tools, accounts and access, as well as how requests and decisions move through the organisation. The intervention documents that framework without replacing day-to-day tool administration.
May include: an inventory of tools and access, responsibilities, priorities and rules for creating, recovering or handing over access.
Present the situationWhen a service must be available to teams, clients or partners.
We design the system for the use: a website, web application, software product, client area or business interface.
May include: the target journey, a first version, the selected product, its code and the material needed to put it into service.
Describe the system to buildWhen AI must be introduced for a defined use, with a clear framework.
The intervention defines a bounded use, authorised sources, permissions, controls and human approval before any automation.
May include: use framing, selected sources, access rules, an agentic system and its verification method.
Describe the intended useWhen a website, application or software product must be recovered and stabilised.
We establish what exists, what is missing, available access and the priorities needed to stabilise or evolve the product.
May include: a diagnosis, access inventory, targeted fixes and a handover pack.
Show the existing productDescribe what exists, what is blocked and the expected outcome. The first exchange checks whether an intervention is relevant and under which conditions.
Describe the situation