Skip to main content

The Groundwork Method

Four phases. Four decision gates.

Most AI engagements lock you into a long programme before anyone knows whether the problem is clear, the stakeholders are aligned, or the technology fits the operation. The Groundwork Method was built to fix that.

The Four Phases

01

Discover

Purpose: Frame the problem before any solution is discussed.

Activities:

  • Stakeholder interviews across the organisation
  • Problem framing
  • Current state assessment (tools, data, processes)
  • Solution direction development
  • Risk identification

Output:

  • Problem statement
  • Stakeholder map
  • Solution direction document
  • Go/No-Go recommendation for Design phase

Decision Gate:

Do we proceed to Design, pause to address blockers, or close the engagement?

02

Design

Purpose: Document the solution architecture.

Activities:

  • Solution architecture documentation
  • Data requirements definition
  • Integration mapping
  • Security and compliance review
  • Build plan preparation

Output:

  • Architecture decision records
  • Data model and integration specs
  • Security review document
  • Build plan with milestones
  • Go/No-Go recommendation for Build phase

Decision Gate:

Do we proceed to Build, pause to address gaps, or close the engagement?

03

Build

Purpose: Construct the system.

Activities:

  • System construction in defined increments
  • Integration development
  • Testing and validation at each increment
  • Scope change logging
  • Test result documentation

Output:

  • Working system components
  • Test documentation
  • Change log
  • Client progress updates
  • Go/No-Go recommendation for Enable phase

Decision Gate:

Do we proceed to Enable, continue building, or close the engagement?

04

Enable

Purpose: Handover and training to enable independence. Your team owns and runs the result.

Activities:

  • Runbook and documentation writing
  • Team training
  • Change management planning
  • Engagement close documentation
  • Content generation (optional)

Output:

  • System runbooks
  • Training materials
  • Handover documentation
  • Engagement Brief
  • Optional: Capabilities to continuously improve automations independently
  • Optional: LinkedIn posts, case study, capability statement

Decision Gate:

Is the system fully handed over? Is the team ready to run it? Are you ready to independently maintain and improve automations? Close the engagement.

Entry Points

Not every engagement runs all four phases.

Common entry scenarios depending on what you already have in place.

Start in Discover

You have a problem but it's not clearly framed. You need help deciding whether AI is the right solution and how AI might be that solution.

Start in Design

You already know the problem. You need someone to architect the solution and map the integrations before you commit to building.

Start in Build

The architecture is approved. You need someone to construct the system and get it into production.

Start in Enable

The system is built but not adopted. You need runbooks, training, and change management to get your team using it efficiently.

Services

Which service fits your situation?

Discover

For: Sponsors evaluating whether to proceed with an AI initiative

You need this when:

  • You're considering AI but don't have a clear problem statement
  • You've been pitched a solution and need independent validation
  • You need to map stakeholders before committing budget
  • You're not sure whether AI is the right solution

Design

For: Leaders who know the problem and need the system designed

You need this when:

  • The problem is clear but the solution is not
  • You need integration specs before requesting build budget
  • You're operating in a regulated environment and need compliance mapped
  • You want architecture decision records before construction begins

Build

For: Operations teams that need a system constructed and deployed

You need this when:

  • The architecture is approved and you need someone to build it
  • You have a stalled pilot that needs to be salvaged
  • You need integrations, tools, or agents built on existing systems
  • You want a system your team can run and extend without external dependency

Enablement

For: Organisations that have a system but need adoption

You need this when:

  • The system is built but not being used efficiently
  • You need runbooks and documentation written
  • Your team needs training on the new system
  • You need change management planning

Retrospective Documentation

For: Completed projects that need narrative and content

You need this when:

  • A project is complete and you need a case study
  • You want LinkedIn posts or other content from the engagement
  • You need an Engagement Brief for internal or external use
  • You want a capability statement for your team

Not sure which service fits?

Start with a short conversation. We'll map your situation to the right entry point and decide together whether to proceed.

Contact