Implementation Manager

• A generous annual bonus based on business performance
• Pension scheme
• Enhanced Maternity and Paternity leave
• Electric car salary sacrifice scheme
• Long service rewards after 5 and 10 years with Five Guys
• Five Guys Perks & discounts
• Invite to our annual General Managers conference - this year we celebrated in Lisbon!
• Life assurance
• Private medical via Vitality
• Wellbeing support

BURGERS & FRIES AND INCREDIBLE CAREERS!

We're the burger restaurant with the uncomplicated formula: burgers and fries cooked to perfection, with no frozen ingredients. And we've stuck to the same 'perfect and serve' philosophy since our family business began in 1986.

These days, we're still just as much a family as we always have been. We have tons of integrity, we're enthusiastic. we're competitive and we just get it done - whatever the challenge.

At Five Guys, the Project Management Office (PMO) is the team responsible for making sure technology and business change actually lands. It focuses on outcomes, not just delivery, ensuring what gets built is understood, adopted and used across the business.

The PMO is a small, delivery‑focused function reporting to the Head of Projects and is actively being built. Its current focus is cybersecurity and Microsoft 365 improvement, with broader programmes to follow as the business grows.

The Implementation Manager role exists because while Five Guys invests in technology, it needs stronger, hands‑on implementation to make change stick. You close that gap by personally owning rollouts end‑to‑end, creating guidance and training, running sessions and measuring adoption. This is a practical implementation role where you do the work, not just oversee it.

• Build and execute rollout plans from scratch

  • Take a workstream brief and turn it into a practical delivery plan
  • Identify who is impacted, what changes, sequencing and dependencies
  • Execute the plan yourself rather than handing it off

• Create the materials that make change stick

  • Write clear, role‑specific user guidance and training materials
  • Design communications people actually read and understand
  • Run training sessions and answer questions directly
  • Confidently guide others on using Microsoft 365 tools including Teams, SharePoint and OneDrive

• Track whether the change is working in practice

  • Build feedback loops and adoption measures
  • Spot when something has landed poorly and intervene
  • Stay accountable for outcomes rather than just delivery

• Act as the bridge between IT, Security and the business

  • Translate technical and security requirements into usable guidance
  • Turn real user feedback into clear input for technical teams
  • Ensure changes feel logical, helpful and well explained

• Bring structure and consistency to PMO delivery

  • Build templates, checklists and repeatable delivery patterns
  • Establish ways of working that become standard for future programmes
  • Manage your own risks, progress and reporting within the PMO cadence

• Drafting a rollout plan for the next phase of Microsoft 365 changes
• Running a project checkpoint call and tracking actions
• Writing a one‑page user guide for an IT change
• Reviewing adoption data to check if a rollout is on track
• Joining alignment calls with IT, Operations and Security
• Updating the PMO delivery tracker and escalating blockers
• Following up with stores or teams where adoption has dropped off

• You have delivered at least one workstream end‑to‑end, from plan to confirmed adoption
• A repeatable rollout framework exists because you built it
• Business teams can name you as the person who made a recent change make sense
• IT trusts you to accurately represent business needs
• You can show clear feedback and adoption data

• Adoption metrics are measurably better on workstreams you delivered
• The PMO has a delivery playbook with you as a primary author
• Technology change is described as well‑managed rather than chaotic
• New workstreams follow your patterns without starting from scratch
• You are already planning what comes next

• 4 to 7 years delivering technology or change programmes hands‑on in a business
• Built rollout plans, training or user guidance yourself and can show examples
• Worked effectively across technical and non‑technical stakeholders
• Tracked adoption and outcomes after go‑live rather than moving on immediately
• Operated with autonomy, owning your workstreams end‑to‑end
• Brought structure to complex or messy environments without waiting for instruction