Why a method
Many technology projects fail for reasons that are not technical. They fail because the objective was not clear, because nobody had the authority to arbitrate, because the solution never left the demonstration stage or because those who were supposed to use it did not adopt it.
Our method addresses these causes. It comes from our original business: project, programme and portfolio management. It rests on a simple idea: divide the path into four stages, and end each one with a decision.
Frame
Framing answers three questions. What problem do we want to solve, and for whom? How will we know it has succeeded? What constraints apply: available data, security, regulation, budget, skills?
Our consultants meet the business teams concerned with you, help examine the existing environment and rank the options according to their value and feasibility. Framing ends with a short document: the objective, the scope of the first stage, the success criteria and the known risks.
It is also the moment to say no. If the data does not exist, if the sponsor has not been identified or if the expected benefit does not justify the effort, we say so at this stage. A framing exercise that concludes a project should not be launched has done its job.
Prove
An idea is tested in real conditions. Our consultants contribute to a first version on a deliberately limited scope: one use case, one application, one team. It works with real data and real users, and not in a demonstration environment.
This stage is not a proof of concept destined to stay in a drawer. It is built to be extended: the architecture, security and quality choices are already those of what comes next. At the end, we help measure the gap against the success criteria set during framing, and we present a recommendation: continue, adjust or stop.
Industrialise
What has proven itself must be able to scale. Industrialisation means extending the solution to the whole of the target scope, on a shared foundation.
In practice, our consultants help your teams deal with what the first version could still tolerate: deployment automation, monitoring, security, access management, quality, documentation and cost control. They pass on their practices as the solution expands, so that the knowledge stays with you.
This is often the most underestimated stage. Going from one use case to ten does not take ten times the same work: it takes a platform, common rules and governance. Our experience in transformation management comes fully into its own here.
Operate
A solution that goes into service is only beginning its life. Our consultants support your teams in operations: monitoring service levels, handling incidents, continuous improvement, tracking costs and usage.
Our objective is your autonomy. Skills transfer to your teams is prepared from the framing stage and happens gradually. Depending on your wishes, we remain in support or step back, leaving up-to-date documentation and procedures.
What never changes from one project to the next
The content of the four stages varies by domain. Three principles remain constant.
- A decision at every stage. No stage leads automatically into the next. You decide, on the basis of facts, whether to continue, adjust or stop.
- Security and compliance from the start. Data protection, regulatory requirements and risk management are addressed during framing, not added at the end.
- Continuity is possible. The consultants who contributed to framing can carry on alongside your teams: you do not have to explain your context again at each stage.
To see how this method applies to a specific domain, see our expertise. To understand the principles behind it, read our Mission and values page.