Reading: How to build and define the scope of an MVP with Monika Ocieczek10 min
How to build and define the scope of an MVP with Monika Ocieczek
SOAKED AT SLUSH 2021 – ARTICLE 2/10
Founded in January 2020, Primer is the world’s first no-code automation platform for payments. They enable companies to consolidate their payments stack, and build end-to-end payment flows with a checkout developers love. They raised their Series B in October 2021, with a current team of over 100, working across 20 different countries on four continents – fully remotely. In this instalment of the Soaked by Slush interviews at Slush 2021, we talked to Monika Ocieczek, Head of Product Design at Primer. She told us about what makes a good product person, and gave us her best insights into building and scoping MVPs.
Expect to learn:
- The product mindset: key qualities of a good product person
- About the process of building an MVP
- How to define the scope of an MVP
- The importance of design thinking
The product mindset: key qualities of a good product person
Monika’s road to her current role at Primer was full of interesting pit stops; starting from business studies, spontaneously moving onto design, then marketing and comms strategy, to eventually working with and for startups Squid news, Tink, and Gimi. Before her work with these startups, Monika worked at a product design agency, helping incumbents like SAS and Danske Bank build digital products, which was when she got drawn into the world of product.
“During business school, I was bored with the one-dimensional perspective. I needed to complement my finance and management classes with something more creative… so I learned design. I was never a great designer, but my business background combined with design, an interest in tech, and my love for building things got me a job at a product design agency where I had the opportunity to use both halves of my brain! Here, I discovered that building products was my calling.”
Like Monika herself, product people can come from many different backgrounds.
“I think the best product people are generalists, and they can come from different perspectives or angles. It can be tech, it can be business, it can be design. In the end it’s really about having ‘the product mindset’.”
What are the intrinsic qualities that make someone a good product professional that you should look for when hiring?
Ability to shift between mental models. “An essential skill for a product person is alternating between small and big thinking, alternating between tech, design, business, and understanding them. This also means alternating between talking to users and feeling empathy, but also looking at tech stack and the JIRA tickets and making sense of how to build something that would answer user needs.”
For Primer, shifting between small and big thinking was essential when tackling one of their biggest issues in the development of their workflows.
“One interesting challenge we’ve had at Primer was 3-D Secure. It’s a regulation on how banks have to authenticate users when they’re paying with cards. Consumers sometimes get prompted to authenticate their purchase, and it’s really not a great user experience, and it brings a lot of technical complexity.”
Put the big thinking hat on and it’s just a detail, something that will soon be completely seamless.
“It’s not going to work like this in the future. But right now it’s a mess, it’s really important with a huge impact, and we have to zoom in and figure out how to make it work for all use cases.”
A combination of creativity and analytical skills. These two can sometimes feel contradictory, but having both, and being able to switch between them is what makes for strong product people. “Creativity is needed to connect unexpected dots, to find new solutions to known problems, and in making interesting products that have personality. On the other hand, analytical and critical thinking are needed to evaluate things and make sure that they’ll work, to make difficult decisions, and to extrapolate. They help you see the long term implications of choices.”
Visualization skills: being able to picture the product in front of you. “Seeing what the product looks like, how it works and what it feels like using it. What it would do, and hopefully be able to make words of it. You don’t need to be a designer to sketch out something simple that allows others to see what you’re seeing in your head. A simple illustration helps you have a starting point for the conversation about the idea, which you can then evaluate and improve.”
Curiosity. “If you’re in an interview, and someone tells you what Primer does in five minutes, obviously, you have to ask questions – it is impossible to understand what we do in five minutes and not have any questions! Curiosity is really important. This goes beyond the interview situation, of course; curiosity about the market, your users, the technology, and trends in the sphere are also crucial.”
Observational skills. When you’re testing products, these skills will determine whether you ‘get it’ or not, whether you get enough of it to be able to improve an existing concept or come up with something new instead. These observations breed new ideas, as you start noticing things and making new connections.
“I love when people say, ‘I noticed this detail. I noticed you said something, I noticed that you have this thing on your website, and I connected that with something you said, or something that I’ve done before, something that I’ve experienced, or something another product is doing. What’s the relationship?”
Building an MVP
Monika says that she likes to ‘create things, ideally starting with nothing’. How do you build something when you only have the problem you want to solve to start with? A central part of this process is, of course, the minimum viable product (MVP). At Slush, Monika walked us through the whole process of how Primer built their workflow MVP at the Builders’ Studio. For the whole story, keep an eye out for Monika’s Slush talk in February, but for now, here are some of her learnings on the different phases of building an MVP.
1. Understand the problem
Understanding the problem is obviously all about knowing your market, users, and the problem you’re solving. In this phase, Monika highlights the need to alternate between small and big thinking; collecting all the small problems your users are communicating to you, and organizing them into a bigger entity to go beyond the obvious solution, beyond solving small problems in isolation.
There are limitations to user research, it will tell you what is wrong but not necessarily how to solve it – user research rarely leads to a great product by itself. There’s a difference between really getting to know your user and empathizing with them and conducting artificial focus groups.
2. Explore solutions
Don’t just look at what your competitors are doing. Try out a variety of solutions, even the ones that may seem counterintuitive to begin with. When you explore solutions, try to stay open minded, creative, have fun, and maybe look for inspiration in unexpected places. For example, for Primer the inspiration was found in LEGO and LittleBits.
3. Validate your solution
You need some validation for your product before implementing it. At Primer, they continuously show our work to customers for feedback. You can also conduct internal usability tests on team members who haven’t been as exposed to the product for a fresh set of eyes. Lastly, an open and honest feedback culture is central for continuous reflection.
But keep in mind: there are so many different ways to validate different aspects of your product before you implement it, but you can never be 100% sure – you also need to have some intuition and conviction about what you’re building.
4. Implement and iterate
As Monika emphasizes, in phases 1-3 you want to keep the ‘big thinking’ hat on, so you might not even think of the MVP itself yet. In phase 4 you want to define the MVP scope, and you want to be really smart about how you do that.
Overall the process is never linear; you start implementing in the validation phase, keep validating during the implementation phase, and the exploration and getting to know the user never stops. Primer’s success hasn’t come from following a by-the-book process, but from having intuition and conviction about a big vision, and certain values you never compromise on. For Primer these values were extensive market understanding and customer focus, open-minded and creative approach, and moving at high speeds.
How do you define the scope of your MVP?
From phase 4 we get to the question of how you determine the scope of your MVP. In our interview Monika shared her insights.
#1: Know what you’re measuring
There is no secret formula. It may seem rudimentary, but the most important thing is to know what you are measuring.
“You need to make a decision of where you cut, or make a compromise in all areas. No aspect is going to be perfect. Scope it in a way that you know what you’re testing. The MVP is going to be so far from what you actually want to build; be aware of the things that you’re compromising on, and if it doesn’t work, you will know why. Be aware of what it is that you’ve shipped, and what you have not shipped and not included.”
#2: Scale down the amount of things you test to add clarity
Don’t launch something just because that is what you have at the present moment – scale down if you need to, if that makes the scope of what you’re testing more clear.
“The worst thing you can do is to not know what to reflect on, not knowing whether you are testing the UI, or the value proposition, or the interactivity, or what the community is like. This doesn’t allow you to actually evaluate what you’ve launched. It might simply be better to even further scale down, and rather be very precise in what you’re testing.”
With Primer’s MVP, the team knew that they were testing the value proposition, and the understanding of the UI when they carried out the view-only version.
“Merchants were still using our checkout and our payments API, but they weren’t actually able to edit their workflows themselves. So we knew that we were testing the value proposition, and the understanding of the UI when we did the view-only version. Later when we added editing capabilities, we were testing the interactivity.”
#3: If you don’t know what should be included, get in touch with the users
Obviously, it’s a difficult balance to strike; if your product is something that simply doesn’t work without a set of certain features, they have to be included in the MVP.
“It’s very different depending on who the product is for, B2C and B2B and in different verticals; some products are just not going to work until you have a set of features that actually work and are well designed. Otherwise, there’s no point in shipping it.”
If you don’t know whether a certain feature should be included in the MVP, be open about it. Keep adding things to the list by being in touch with the users and finding out what they really need. Explore this in every phase of product development; remember, the process isn’t linear.
#4: Don’t compromise on the design (at least too much)
Every time you launch a product or a new iteration, there will be a compromise. Design will be just as much as a compromise as the engineering side of things or the product value proposition. As an advocate of the design perspective, Monika insists that it has to be there from the beginning.
“The truth is, you miss out on so much when you try to incorporate design in the last step to ‘make things pretty’. Product design is really something that starts at the very beginning. It’s part of coming in and understanding the problem from a design perspective. You never have the trade-off of, ‘do we launch something undesigned versus something that has been designed’ – the design is always present.”
Design offers a wholly different way of looking at the product that can reveal what’s not working.
“Designers might be in a better position than anyone else to look at other tools and see why things are not working. You might be able to find issues in the design, which is not just the UI, but also how the flow, interactions, and components are impacting the user experience.”
…and it is key to functionality.
“It doesn’t matter if the product actually does what you want it to do if you’re unable to find a button that does the thing, right? Design is very much about making something needed into something usable, enjoyable, and loveable.”