Skip to content
Rafael Patron

How I work · Method

A tailored method, built around your organisation.

Every programme starts from the constraints, numbers and objectives of the organisation. The method stays constant; the design changes with each engagement.

§ 01 Principle

The method adapts to the context; the rigour stays constant.

An AI programme works when it grows from the organisation’s real processes and from the people who run them every day.

Each phase therefore produces a verifiable result, shared with leadership, which becomes the basis of the next phase.

  • Explicit, measurable business objectives
  • Processes observed in the field, with the teams
  • Available data and constraints stated from the start
  • Governance and change management alongside technology

§ 02 Phases

Four phases, one concrete output each.

  1. M.1 · Listen

    Understand before proposing.

    Conversations with management, operational teams and the people who use the systems daily. A reading of processes as they actually run, and an analysis of available data, including the constraints that surface only in the field.

    OutputA clear map of what exists, what is missing and what comes first.

  2. M.2 · Map

    Define before building.

    Use cases are ranked on three criteria: potential business value, technical feasibility and organisational complexity. Feasibility is checked with technical teams; expected return is sized with leadership.

    OutputAn ordered roadmap with estimates, dependencies and owners: an execution plan.

  3. M.3 · Execute

    Build together with the teams.

    The work coordinates those who build — internal teams and vendors — and moves forward with the people who will use the system. Technology, governance and change management advance in the same plan.

    OutputA system in production, an autonomous internal team and complete documentation.

  4. M.4 · Measure

    Programmes that grow after go-live.

    Impact is measured at three, six and twelve months after launch, with indicators shared with leadership and periodic reviews. What works is consolidated; what underperforms is redesigned.

    OutputA living programme, with current indicators and an improvement plan.

§ 03 Scope

A directing role, with clear boundaries.

The role is the strategic direction of the programme: specifications, coordination and review of the work of those who build.

The analysis points to the solution that best fits the problem, including when it is simpler than an AI system. The format suits programmes where the value at stake justifies senior support.

  • Programme direction and vendor coordination
  • Solutions proportionate to the problem
  • Support to leadership on key decisions
  • Skills transfer to the internal team

§ 04 Further reading

Where to continue.