Reflecting on my first 18 months at Paper
I started my role as a Delivery Manager (DM) at Paper in September 2019. It’s been an interesting introduction to the role as well as to the tech/digital and user experience (UX) industries. My first 6 months were spent working from the studio and onsite with clients, and for the past 12 months my new normal has been working and learning from home. For this article I’d like to reflect on some of the main things I’ve learned whilst being at Paper. I also plan to write another article about becoming a DM and what the role looks like at Paper, in case anyone is interested in moving into this type of role specifically.
Things that went well…
Public speaking can be enjoyable (sometimes)
I’m pretty scared when it comes to public speaking, especially to a group of strangers. However, as a DM I have to do a lot of facilitation of meetings and workshops so I knew it was something I had to throw myself into. One project I was particularly apprehensive about was when myself, Faye, Rachael and Urška designed and delivered an all day virtual practical workshop for Sheffield Digital festival to introduce the basic tools of research-led, user-centric design. I was nervous to ‘teach’ a room of strangers online when I still felt pretty new myself. Doing a test run of the workshop with a small group of volunteers was really helpful to work out any kinks in the workshop and practice how it would work.
The event itself went really well and turned out to be pretty fun - it helped that I had a great team of gals to work with and the people who attended were lovely. I feel much more confident to facilitate the next one, and we’re actually thinking of running it again for the next Sheffield Digital festival!
Teamwork makes the dream work
A key thing I’ve enjoyed at Paper is working in teams and solving problems. I’ve enjoyed working with lots of different people, and I appreciate that Paper always assigns at least two Paper people to every project so we never feel isolated or uncomfortable. In previous roles I felt ‘teamwork’ was just something that was mentioned in job interviews. You’d go to work, be told what to do and have no idea what other people were doing. Working at Paper has really shown me the benefits of working transparently in a close knit, self-organising team. The team may change from project to project, but it’s been interesting to see how having different skills and ways of thinking all aligned to solve a problem really works.
For example, in my last Discovery project as a DM, one of the client’s aims was to demonstrate a new agile way of working to the organisation and show why it’s valuable. We ran our project using agile practices (Scrum and Kanban) and principles (e.g. focus on user needs, do things iteratively, keep improving how the team works, work transparently etc.). Our team was a mix of Paper and client people and we collaborated with a lot of departments and stakeholders within the organisation throughout the project. The client actually wanted to replicate our agile approach in their own structure, which led to an interesting conversation about cultural and systemic change that was needed within the organisation to break out of working in siloed departments and encourage more collaboration across teams in order to solve problems for users collectively.
I’m starting to gain more confidence
I’m more honest these days about saying ‘I don’t know’. I used to not want to seem inexperienced or stupid, but now I find I learn more if I’m honest and say ‘I don’t know what that means’ and more often than not someone else in the conversation had the same thought. I’d say this is something I’ve developed at Paper specifically as it’s such a supportive working environment and I feel safe to be honest. For example, in my first project when I wasn’t sure how to run a design sprint, or when I was unsure how to run a virtual inception when the pandemic hit, I asked my peers to review my ideas and expect them to know exactly what to do, but they were just as clueless as me, which was a comfort as it helped me see that a lot of us are just figuring stuff out as we go, and we can work things out together.
It’s clear that imposter syndrome will always be there, but I’m getting better at dealing with it. I usually get nervous before the start of a project as I worry that the client will think I’m too junior and don’t know what I’m talking about and I often think back on things I’ve said or done and doubt them. I keep reminding myself that my role as DM is to help the team do their best work - they’re the specialists who do the work, I just need to make sure they’re happy and the work runs as smoothly as possible, and I think I’m doing alright at this so far.
Things I’ve learned…
There’s no set way of doing things
My background in project management involved a very linear, process-driven and siloed approach to delivering projects. After starting as a DM at Paper, it took me a while to realise that there wasn’t a set way to do a project, which I found quite difficult as a beginner. I assumed I’d read a ‘how to deliver a UX project’ guide, I’d follow the steps and I’d be sorted. I soon realised that each project and each team tends to need a different approach to how they work, so having a rigid process isn’t usually helpful as you’ll probably have to change how you work as you go - which is why agile methods work so well as they can be adapted in rapidly changing environments like the tech/digital industry.
A good example of this was in my first project, a 5 day Design Sprint, where I read a ‘how to’ article, tried to follow it step by step, and then it didn’t work like I’d hoped. I ended up developing a new way of working that suited our particular team - it still included the fundamental outcomes from the article but how we did it was different. We actually still use this approach for new projects with this client as it seems to work well.
It’s better to use plain English
I’ve learned a lot about how to introduce Paper’s way of working and thinking to a new client. Often each team we work with has varying experiences or understandings of aspects of Paper’s work (e.g. agile practices, the benefits of user research, how service design works) and I’ve found it beneficial to use plain English when explaining how we work and deliver projects to clients to keep things as clear as possible for everyone involved.
For example, I recently worked on a project where the client wanted to initiate more user-focused and agile ways of working, but the word ‘Agile’ was sort of taboo in the organisation due to a bad experience with a previous project. It was an interesting challenge to introduce what we were doing without using any buzzwords or business jargon, but I think doing so helped to prove the value of how we were working. Instead of saying we’re using Scrum ceremonies and Kanban boards to structure and track our workflow, we can simply say ‘we’re working in two week blocks of time where we plan, do and review each chunk of work’. It didn’t hide behind fancy words and processes, it was all about making things better for users, which is where the focus should be.
I prefer Miro over real post-its
Before the pandemic I’d never really worked remotely before, but one thing I’ve enjoyed is developing more digital ways of working. I actually think aspects of delivering a project are a lot easier done remotely e.g. you don’t have to get there early to prep a room or buy snacks or faff about with projectors. I’m also not a big fan of post-it notes (I’m sorry Paper people!). I can never fit what I want on a post-it, they fall off the wall, the sharpie sound on paper gives me goosebumps, handwriting can be hard to read, then you have to take pictures of what you’ve done, upload them and rewrite a lot of it for digital handovers anyway (rant over). I prefer using digital tools like Miro to brainstorm and capture everything neatly, I can easily make changes and it’s readily available. Of course there’s plenty of things I miss about working in-person and it has many benefits over remote working, but I think I’ll still keep a lot of the digital tools and processes in the way I work when we return to the studio.
Things to improve on…
Working on different types of projects
So far I’ve mainly worked on Discovery type projects and I’ve worked with a variety of clients including social enterprises, a city council and a University, which has been great. I also got some experience on a government Beta project in a ResearchOps role, but I’d like to gain more experience on how to deliver Alpha and Beta projects in the future.
To prepare myself, I’ve been trying to document the steps involved in delivering different types of projects, from doing the initial sales pitch to closing down a project. I’m trying to get to grips with the fundamental aspects and outcomes of each project phase (e.g. a Discovery will have a different set up and outcomes than an Alpha or Beta) whilst also documenting useful tools and techniques that will help me deliver them (e.g. tools for analysing research, sketching designs, helping the team get to know each other or define their scope etc.).
As a newbie it can be difficult sometimes to pinpoint what the fundamental steps are to delivering a project versus a useful tool to help you achieve something for your project. Thankfully, we’re currently working on an internal project that will start to document all the building blocks of how we do things at Paper (e.g. ‘how to’ guides, templates, patterns, policies, tools etc). The aim is for Paper newbies, or freelancers working with Paper for the first time, to see how we work and the standard we expect. I’m really looking forward to working on it as I think it will really help me get to grips with the foundation of a project versus how I can deliver it.
Dealing with conflict
A big part of being a DM is bringing the team together and creating a happy and productive working environment (aka bring all the snacks so people don’t get hangry), but this can also mean dealing with and calming down conflicts or facilitating difficult decisions, differing perspectives and tricky personalities. I’ve started to see these things pop up in projects, but at the moment I’d need a lot of support in knowing how to deal with them, so I’m currently looking into training courses on this subject.
I’ve learned a lot about myself…
With user guides
User guides are a tool we use in projects to help teams get to know each other. We also fill them out when we start at Paper - it wasn’t until I wrote mine that I realised a lot about how I like to work. For example, one thing I didn’t know until I came to Paper was my ‘thinking style’. I’m quite visual and like to map things out as a way of planning and understanding how things work, but I’m also a ‘linear’ thinker meaning I really like to go through my work in a logical, step by step approach. At first I struggled with the ‘agile’/rapid changes to Paper’s type of work as it would ruin my carefully laid plans, but I’ve since learned to create plans that can be adapted and anticipate change. A great tool for doing this is ‘scenario planning’, which I recently used to plan how to recruit Schools Buying Professionals for research during all the school closures and Covid-19 lockdowns.
With retrospectives
Doing retrospectives in general and reflecting on work isn’t something I’ve ever done before coming to Paper (except maybe informally at the pub). They’re really useful in projects for the team to reflect on what went well in the last bit of work and what they could improve on, concluding with actions they could implement in the next chunk of work. We use them at Paper from time to time to look at how we work internally. For example, at Christmas time every year I run a ‘Paper Retro-ho-ho’ where we reflect on the past year and what we improve on in the New Year. It’s great to tap yourself on the back for good work, learn from mistakes in a supportive environment and set new things to strive for in the future. I’ve even found writing this article quite therapeutic to look back on how far I’ve come in 18 months and I’m excited to keep learning and improving as I go.
Follow Paper on LinkedIn