Home / The FiveForward Framework

Adoption framework

The FiveForward Framework

A five-stage method for turning Microsoft Copilot from a licence into a working habit.

FiveForward author profile Written by FiveForward

UK Microsoft 365 Copilot and AI adoption consultancy. About FiveForward

Why most Copilot rollouts stall

Most Copilot rollouts do not fail because the tool is weak. They stall because access arrives before people know what to do differently on Monday morning.

The licence is bought, the announcement goes out and a training session is booked. A few people find useful habits. Others try it once, get an average answer and go back to the familiar way of working.

The missing piece is not another feature demo. Staff need clear use cases, real examples, safe-use rules, follow-up support and a route for the repeated work that should be automated rather than prompted each time.

The FiveForward Framework is a practical way to create that route: Discover, Design, Enable, Automate and Embed.

The five stages, at a glance

The framework follows five stages in sequence. Each can be scoped as a standalone engagement or run as part of a wider programme.

01
Discover

Map the work, hear from the people doing it and identify the Copilot use cases worth pursuing.

02
Design

Choose the first teams, workflows, training route, governance points and measures of progress.

03
Enable

Run training and support around real emails, meetings, files, reports and decisions.

04
Automate

Use Power Automate, Microsoft 365 workflows or agents where a repeated process is ready for them.

05
Embed

Keep adoption moving with champions, office hours, examples, reviews and ongoing support.

01

Discover

What happens

We talk to the people doing the work, map repeated tasks and find the places where Copilot could reduce friction without creating avoidable risk.

Why it matters

Most rollouts stall because the training starts before anyone knows what staff should use Copilot for. Discovery gives the rollout a useful target.

What you get

A prioritised set of use cases, the blockers that need attention and a recommendation on where to start.

Examples

  • Interview tax, audit or operations teams about repeated admin and handovers.
  • Review where important files, meeting notes and templates actually live.
  • Separate good Copilot candidates from tasks that need SharePoint cleanup or a human review step first.
Explore Discover services
02

Design

What happens

We turn the discovery findings into a plan: which teams go first, which workflows are covered, what training needs to include and how progress will be reviewed.

Why it matters

A rollout cannot cover everything at once. Design keeps the first wave focused enough for people to understand and leaders to measure.

What you get

A rollout roadmap, training brief, governance notes, success measures and a sensible order of work.

Examples

  • Choose client meeting follow-up before more complex client drafting.
  • Create separate training paths for partners, managers and support teams.
  • Define what good usage should look like after 30, 60 and 90 days.
Explore Design services
03

Enable

What happens

We deliver practical training, office hours and role-based examples so staff can try Copilot in the work they already recognise.

Why it matters

People do not change habits because they saw a feature demo. They change when they can practise a useful task, get help and see managers reinforce the behaviour.

What you get

Training sessions, role examples, prompt guidance, follow-up actions and support for the first real questions after launch.

Examples

  • Train fee earners on meeting summaries, follow-up emails and document preparation.
  • Show finance teams how to draft commentary without treating AI output as final analysis.
  • Run office hours where staff bring failed prompts and live workflow questions.
Explore Enable services
04

Automate

What happens

We build or improve the workflows where automation is a better answer than asking a person to prompt Copilot every time.

Why it matters

Some work should not depend on memory, chasing or copy-paste. Automation helps when the process is clear enough to run safely in the background.

What you get

Documented Power Automate flows, Microsoft 365 workflow improvements, agent scope or build work, plus handover notes.

Examples

  • Route training bookings, reminders, feedback and certificates from one form response.
  • Move document approvals through SharePoint and Teams without manual chasing.
  • Build a narrow Copilot Studio agent for internal knowledge or intake once the source content is ready.
Explore Automate services
05

Embed

What happens

We help the change continue after the launch with champions, office hours, prompt libraries, usage reviews and small improvements.

Why it matters

Copilot habits fade when the support fades. Embed gives people somewhere to take questions and gives leaders a clearer view of what is improving.

What you get

A support rhythm, champion guidance, reusable examples, review points and a backlog of the next use cases worth developing.

Examples

  • Set up monthly office hours for awkward prompts and real workflow blockers.
  • Give champions examples they can share inside their own teams.
  • Review usage themes and decide whether the next step is training, SharePoint work, automation or an agent.
Explore Embed services

How the stages connect

The stages are flexible, but the order matters when the work is unclear.

Discover before Design. If you do not know where time is being lost, the plan will be based on guesses.

Design before Enable. Training works better when the first teams, examples and success measures have already been chosen.

Discover before Automate. A workflow that looks simple often contains exceptions, handovers and judgement calls. Those need to be visible before anything is built.

Enable before Embed. Champions and office hours work best once people have tried Copilot against real tasks and have real questions to bring back.

You do not have to buy all five stages. The point is to choose the right starting point with the dependencies in view.

Who the framework is for

The FiveForward Framework is designed for UK mid-market organisations where Copilot has been purchased and the next question is what to actually do with it. Professional services in particular, where the work is knowledge-heavy, the Microsoft 365 dependency is high and the risks of poor adoption are well-understood once named.

The framework applies across sectors. Use the sector pages for more specific examples of where Copilot, automation and Microsoft 365 adoption fit the work.

What it looks like in practice

The examples below show how the stages translate into decisions, training and workflow work.

Accountancy firm, 600 staff

The firm had purchased Copilot licences across the organisation but had not yet started training. Rather than begin with training, they commissioned a Discover engagement first.

The Discover work took three weeks. It involved structured interviews with fee earners across tax, audit and advisory, mapping the tasks that consumed the most unrecoverable time each week. Three workflows emerged as clear priorities. The first was the monthly client management report: a recurring task that took the team six hours per cycle, drawing on meeting notes, emails and spreadsheet commentary. The second was the preparation of engagement letters, which were being drafted largely from scratch despite following predictable patterns. The third was internal knowledge retrieval: junior staff spending time searching for precedent documents and past advice scattered across a fragmented SharePoint structure.

None of those three workflows came up in the initial licence conversation. Two were invisible to management because the time cost was distributed across junior staff who had not been asked about their workload.

The Design stage took those three use cases and built a phased enablement plan: which team first, which Copilot features to cover, what success looked like for each workflow and in what order the rollout would run. The Enable stage built specific training sessions around each workflow rather than running generic feature demos.

Professional services firm, 200 staff

A consultancy had completed their own Discover and Design work internally and came to FiveForward for Automate support. The specific need was a Copilot Studio agent to handle the initial briefing and intake process for new client engagements, reducing the time partners spent on administrative coordination.

The Automate engagement began with a process review, which surfaced two edge cases in the intake workflow that would have broken the agent if not accounted for. The build and testing took four weeks. The agent went live with clear governance: a defined scope, a human review step and a documented process for handling exceptions.

Where to go from here

If you are thinking about how the framework applies to your organisation, the most useful next step is a conversation. Not a sales call. A working conversation about where you are now, what adoption looks like today and which stage of the framework would move things forward most quickly.

Talk through your rollout with someone who has seen a lot of Copilot adoption work. Or if you want to understand the individual services first, explore the service map.

Standard rates and how engagements are structured are on the pricing page.

Next step

Talk through what would be useful.

A 30-minute conversation is enough to work out where the framework fits your organisation and what a sensible next move looks like.