Becoming a Delivery Manager
I started my role as a Delivery Manager (DM) at Paper two years ago. I had no experience in user research or service design and a basic understanding of what my role would entail. I wasn’t sure what to expect and I was worried that not having a background in the tech, user experience (UX) and general digital industry would be a hindrance, but thankfully that hasn’t been the case.
No-one grows up wanting to be a DM, but I think the work and skills would suit a lot of people if they knew the role existed. I’m writing this article to go over what I’ve learned about the role so far in the hopes that anyone who’s looking for a new role can see what it’s like (at least from my experience).
What is a delivery manager?
When I tell people I’m a DM, they seem to think I work for a delivery service like Amazon, someone actually once asked “Oh like a milkman?”. I usually end up saying I’m a project manager, but that’s not quite right.
I’d done some project management before coming to Paper in a localisation company. Work came in, I managed the budget, assigned and liaised with translators, conducted quality checks and delivered work to the client. I was in my own little silo where I followed a linear, step by step process - I was unknowingly learning a traditional ‘waterfall’ approach to managing projects, which works fine for the localisation industry. But I did find the focus to be more on profit margins rather than people, and even though I worked with other people I wasn’t part of a team, all the responsibility was on me.
Once at Paper I quickly learned a new way of managing projects called ‘Agile’. This approach is about making incremental changes that aim to continuously improve the thing you’re working on (i.e. you ‘iterate’ how you do things). Its values are about putting people first, meaning multidisciplinary teams work together with the people who will end up using what they’re designing, so that it actually works for them. Using Agile works well in the tech industry as things are constantly changing and products and services need to be able to adapt to user behaviours and feedback.
My experience of being a project manager was quite work focused, whereas I’d say being a DM is more people focused. I think the fundamental difference between the two roles is the idea of ‘servant leadership’ and putting people first. A DM is someone who serves the needs of the team and guides them in the right direction. You don’t tell them what to do because you all work as a self-organising team with equal responsibility for delivering the work.
Your goal is to help the team with their approach, keep them happy and protect them from anything that might hinder them so that they have the space to do what they’re best at.
The role is often described as a sh*t umbrella or silent protector:

Image: The Silent Protector adapted by Beth
The main skills of a delivery manager
Emily Webber wrote a great article about being a DM and neatly summed up the DM role in the following venn diagram:

Image: Delivery Manager Venn Diagram
I’d recommend reading Emily’s article, but the highlights for me are how each area involves different skills:
- Agile practices are the ‘tangible skills’ - knowing about Agile tools and which ones might work best for the project and team. There is no set way of doing things - each project and team will need a tailored approach to help get things done successfully. I’d say anyone can learn these skills and apply them to how they work.
- Team health and happiness are the ‘people skills’ i.e. being good with people, keeping the team happy through motivation and encouragement, helping them work well together and creating an environment where they can do their best work. Most people can learn these skills, but I’d say you need to be someone who fundamentally cares about people and likes to be around them.
- Delivery support is the ‘other stuff’ (financial management, planning, building and supporting teams, plus any- and every- thing else the team needs e.g. prepping the workspace or assisting with their work). Most of this can be learned (and don’t worry, you don’t have to be a maths whizz to figure out budgets).
Then finally there are some core skills that DMs use, the main ones being:
- Coaching - helping people, teams or the client to understand your ways of working
- Facilitation - facilitating meetings and workshops to keep them on track; facilitating difficult discussions and differing perspectives with diplomacy and active listening
- Communication - setting up how the team communicates; visualising the team’s workload so everyone knows what’s happening; thinking about and reacting to any changes or risks; updating the client and stakeholders about the team’s progress; public speaking e.g. in pitches and presentations
These skills can be learned too, although it helps if you have some natural traits like organisation, caring about people, public speaking etc. to give you a headstart.
Some common characteristics
As I mentioned before, no-one grows up wanting to be a DM, but I think there are some common characteristics and traits that would make people suitable for the role:
- Good at remembering things e.g. birthdays, putting the bins out, plans for the weekend
- Quite organised e.g. making lists, using the calendar, good at revising for tests
- Good at planning stuff e.g. always the one making plans and booking things
- Looks out for other people e.g. checking in with people if they look upset
- Likes to help others and be useful e.g. helping out with cooking or cleaning up
- Good at time management e.g. getting to the airport on time
- Good at engaging with people e.g. talking to new people at a party
This isn’t an exhaustive list, and you don’t have to be great at all of them, but I hope it shows the type of person that would make for a good DM and may want to consider looking into the role as a potential career option in whatever industry.
You don’t need specific experience to become a DM
A great thing about this type of role is that it’s transferable to a lot of industries. Before Paper, I had some of the natural traits listed above, some project management experience in the localisation industry and some experience of managing people from working as a manager in a shop. I knew nothing about tech or UX, but I learned many of the necessary skills on the job and built upon the skills I already had.
I’ve found it actually helps to not be an expert in the industry sometimes. On a project, the client will be the expert on whatever they do and your team members will be experts in their respective fields, but when working on problems together it helps to have someone who asks ‘what does that mean?’, ‘how does that work?’ or ‘why are we doing this?’ as it helps create a shared language and ensure everyone has a shared understanding of what we’re doing. More often than not, someone else on the team will have had the same question but may have been too uncomfortable to ask, or perhaps thought they knew it already but they confused it with something else. Having someone new to the sector can help clarify things and prevent misunderstandings further down the line.
What helped me learn the role
When I arrived at Paper I knew I was starting from scratch. I’ve summarised a few things that helped me get to grips with the role:
Networking and joining communities
I wanted to get to know other DMs and build my own network. I shadowed a few people on projects and arranged one-to-one chats where I could ask questions about a certain topic or general things about being a DM. I also joined a bunch of community groups on Slack, such as Agile in the Ether and ResearchOps, where you can ask questions, join talks and attend workshops.
Trying out a ResearchOps role
For a couple of projects I’ve been assigned as ‘Research Operations’. This role helps user researchers with certain aspects of the research process, such as recruitment, governance and data management. Researchers have a lot on their plate and the role aims to give them the time and headspace to do their best work. I think it’s a great stepping stone to being a DM as you focus on supporting researchers without the pressure of being the DM for the whole team. Plus you learn a lot about research processes and how best to support researchers for future projects. There’s also a DesignOps role that I’m keen to try out.
Learning how to self-organise
This is less of a thing you read about and more of a way of life/working. A self-organising team is where no-one tells you what to do, rather you manage and take responsibility for your work as a team as you’re trusted and empowered to get things done. This is how Paper works day-to-day, which was quite an adjustment at first, but I’d never want to go back to being told what to do and feel like I have to be chained to my desk precisely 8 hours a day.
Understanding Agile
At Paper we use Agile practices, and there are a bunch of different Agile methods that you can use, so I knew it was a big thing to get my head around for my role. At first I read a bunch of articles and blogs and tried to apply that to how I worked, but I found it quite theoretical and difficult to get my head around (with all the buzzwords, pillars, values, principles etc). It didn’t start to properly click until I’d worked on a few different types of projects e.g. a Design Sprint with a social enterprise, a Discovery with a city council and a private Beta with a government department. I also took a course to become a ‘Scrum Master’, which sounds like some sort of wizard, but it helped me understand the Scrum framework, (one of the Agile methods) and how I could apply it to projects.
I realised that, as each project and team are different, it’s common to ‘pick and mix’ whichever methods and tools will help the team deliver the most value. For example, at Paper we use Agile methods like Scrum and Kanban to structure and deliver work, and then we’ll use various tools depending on the type of project and problem we’re looking at, such as user guides to get to know the team, affinity mapping as a way to analyse research, crazy 8s as a way to ideate solutions or opportunity cards to show improvements to a service. No two projects are ever the same.
In the end, I found the best way to get to grips with Agile was to have a go. It’s all about trying things out, seeing what works or what doesn’t for each team, learning from your mistakes and improving as you go. I imagine this will be a never-ending experiment.
Finding my own ‘flavour’ of being a DM
Initially I thought there was a certain way you had to be and certain steps to follow to be a DM. After doing some shadowing, I had to get it out of my head that what I was seeing was ‘the’ way to do things. There may be set outcomes to reach, but the way you deliver them is entirely up to you and your team. As a DM you will try out loads of different tools and techniques for different situations and find your favourite ones. I’ve found that I like coming up with more interesting ways to do repetitive things.
For example, sometimes I find check-ins and check-outs can get a bit stale with the same team after a while. At the end of any workshop, I find most people are tired and keen to finish. I was inspired by those little Buzzfeed quizzes that ask ‘which Disney character are you?’ or ‘On a scale of Michael Scott, which one are you today?’. I like to do these when I’m low energy so I chose one where I ask the team ‘which cat are you checking out as today?’ I’ve used it a few times as it seems to boost the energy at the end of a long session and everyone tends to leave in a good mood.

Image: Cats in various moods
How I explain the role to others
I don’t really like the title Delivery Manager. It’s true that you help teams to deliver something, and there are times when managing the team is needed to keep them on track, but there’s so much more to it and no-one ever understands the role from the name alone. Some people have suggested alternate titles such as Team Enabler or Facilitator, which I think is a step in the right direction.
Anyway, I think I’ve finally figured out how to explain what delivery managers do when people ask - we’re basically like Gandalf:
- We build the team (like the Fellowship - each member has their own unique strengths and skills i.e. a multidisciplinary team)
- We guide them to deliver a thing (like the One Ring to Mount Doom i.e. designing or improving a service for a client)
- We support the team in their journey and protect them from stuff along the way so that they continue to do what they’re supposed to do (like stop fiery demons from killing the Fellowship i.e. shielding the team from outside distractions or politics)
Gif: Gandalf shouting “You shall not pass”(i.e. a DM shielding their team)
If you’re not a LOTR fan, (I’m sorry, we can’t be friends 😜) another delivery manager icon is Ginger from Chicken Run. She organises the chickens, builds a multidisciplinary team with diverse skills and aligns them to one goal - to escape.
Useful things I’ve read
Here’s a list of books, articles, courses and communities to check out. It’s a mix of delivery and agile stuff. I didn’t fully understand them and had imposter syndrome when I first read them - don’t worry too much, they’re just a place to start.
Books:
- Resilient management by Lara Hogan
- Good Services: How to design services that work by Lou Downe
- Surrounded by idiots by Thomas Erikson
- Sprint: How To Solve Big Problems and Test New Ideas in Just Five Days by Jake Knapp
Websites:
- GOV.UK Service Manual - this is like a bible, it’s well written and has everything you need to know about pretty much anything to do with creating services.
- ResearchOps website
Articles:
- Explaining the role of a Delivery Manager by Emily Webber
- So what does a Delivery Manager do? by Yiannis Godfrey
- A day in the life of a delivery manager by GDS
- What each role does in a service team by GOV.UK
- How I Co-Created the Delivery Managers Learning List by Myles Jarvis (includes a link to the DM Learning List with tons of useful links)
- “The Design Sprint” by Google Ventures
- It takes two - a post about the difference between product and delivery managers by Matt Jukes
- Agile without ‘agile’ by James Plunkett
Courses:
- Scrum Master course (there are lots out there, I took this one)
- Delivery Manager course by GDS
- How to deal with conflict and difficult conversations (lots out there)
- Designing good services - Masterclass by Lou Downe
Follow Paper on LinkedIn