The video walks through a three‑week product sprint that a design consultancy runs with a startup client to define a Minimum Viable Product (MVP). In week 1 the team conducts workshops with the founders to map the product’s context: vision, target audience, problems, core features, goals, monetisation, competitors, and success metrics. They create a board that captures user personas (needs, motivations, fears, triggers), user story maps, and assumption maps covering desirability, viability, and feasibility. Week 2 brings the full sprint team together for alignment, idea generation, and solution selection. Participants review competitor solutions, sketch concepts on paper, vote on ideas, and build a storyboard that outlines the critical user flow for the MVP. A rapid, clickable prototype is produced in 1–1.5 days and tested with five real customers. Feedback is recorded, categorized, and synthesized into actionable insights. After the sprint, the consultancy delivers a comprehensive summary document, polished UI designs for mobile and desktop, and a design system ready for development. The presentation is instructional, showing the process, artifacts, and outcomes, and invites further questions.
Chapters
Hi, this is a walkthrough of one of our latest projects to give you an overview of our process, the outcomes, how we usually work with our clients. In this particular case, it was a product sprint that we ran for 3 weeks with our client in order to define the MVP, create a prototype, test it with their customers, iterate on it, and then create all the design assets necessary for development. The first week is It's all about understanding the context. For this, we run a series of workshops with the product leaders, in our case, the founders, to map all their insights and know-how. We usually start all our projects with the board that you can see on the screen, which gives us a good overview of the critical building blocks of any product. During this phase, we discuss about what's the product, who is our target audience, what problems do we want to solve for them, Why should they care? Why we actually care about this? What are the core features? Challenges and blockers that might occur? Advantages or opportunities that can be exploited for growth? What was tried so far? And eventually, what were the outcomes for that? Goals and visions. Where do we see this company in like 2, 5 years? How we measure success? How we plan to monetize? And competitors. Then we want to see how this product is different, what kind of unique value it will bring for the customer. Also, we want to see the competitors, what's already out there and what the landscape looks like. We then map the user persona and we are extra focused on the boxes in red: needs and goals, motivations, fears, frustrations, major pain points, habits and anxieties, and triggering events. We also added the job statement section to put the founders in the right mindset and understand that in the end, what they want to build, it's a tool in the customer's hand. User story mapping gave us a good overview of the journey of the customer with the current setup, from buying the workshop, consuming the content, up until the end of the workshop, and see what's happening at each stage. This was a good starting point for defining the MVP, which you can see towards the bottom of the board. Then we've done assumption mapping to see what assumptions we have regarding desirability, viability, and feasibility. With all the notes on the board, it was quite easy to see what are those important assumptions that has no evidence so far, and we should see how we can tackle them. Besides all the exercises that are happening in the workshops, There are a couple of things that we do after that. One thing is we revisit the expert interview board and take some notes. You can see them on the How Might We section. And also there are a couple of personal notes that I put on the right side. These are things that we will reuse in the second part of the workshop. Another asset that I worked on was the customer journey map. This gives us a good overview of what's already happening during the journey of the customer. And what are the main touchpoints so we can see how they switch context and what challenges they might have. After this first week, we had a good overview of the context of the product and the business, and we had the key insights for the second part of the workshop with the whole team. During the second week of the workshop, we gathered the whole sprint team, so it's not just the founders anymore, and we'll have 3 workshops together moving from alignment to creating solutions and deciding on what should be in the prototype that we will test with the customers. So as I was mentioning, the first part, it's about alignment. Here the founders will present the challenges, the insights, and all the knowledge they have back to the team. Also, it's a good place to ask questions. During this phase, each team member takes notes. Here actually, we gather some of the notes from the first week of the workshop. In order to have a good starting point. Once we have all these notes, we categorize them and vote on them. Then we make sure we align regarding the goal, where we see the company in 2 years. And also we want to see what kind of challenges might occur that could stop us getting there. We end the day revisiting the journey of the customer, putting the How Might We notes from the first exercise here, and also picking the area that we want to focus on for the rest of the workshop. In our case, it was regarding the MVP that we want to build. While we move slowly towards creating solutions, the first step is to get some inspiration. Each team member will take some time to see how others tried to solve similar challenges. This is a good place to revisit those competitors that we mapped, but we also encourage the people to look outside of their specific domain and see what other tools and apps are out there. Then we will revisit all the insights and know-how that we mapped so far. We take some notes, we move towards what will be the highlight of the workshop, creating the concept or a solution that we think will solve our challenge. Each team member will have time to create their own pen and paper sketch or concept that they think it will solve the challenge that we have. Again, in our case, it was to create an MVP for a community to consume the workshops. You can see the submitted concepts here. This will be also the place where we will decide in which direction we want to move. So we will pick a concept, then we will map out the critical steps that we want our customers to go through to see if they understand the value and they can navigate the MVP. Then we will define the prototype using a storyboard. Here we will define how each page should look like and what should be on them. So we'll use cutouts from the concepts that were submitted. And also a sticky just to note down each element that should be on that specific page. This helps tremendously when you have 1, 1.5 days to create a prototype because you don't have to second-guess or go back and forth with different people. The next step was to create a prototype that will be tested with the customers. You can see it here on the screen, you can click on the buttons and it's interactive, so we can test the whole flow. And the last day of the second week was about testing the prototype with customers. We had 5 customers that went through the whole prototype and gave us feedback. You can see all the feedback here on the screen. On the left side, we have the feedback collected during the calls. On the right side is the same feedback categorized so we can summarize all the insights and present it back to the founders. Once we went through these 2 weeks of the product sprint, we create this summary document. Here you can see all of the important aspects regarding the workshops. So we have an overview regarding the insights that were discussed in the first week. Also the assets that were created, the user persona, the user story mapping. And we also talk about the assumptions that were tested during the second week of the workshop. Then we go through a summary of the second week. What happened at each day. Here is the map, the concepts, the storyboard, and we talk a bit about the prototype. The most important part is definitely the insights gathered during the user interview. So here you can see the big takeaways. What were the things that worked? What were the things that should be improved? Suggestions regarding on what should be improved and how. We go through all this stuff with the founders and agree on next steps. Starting from the prototype that we created and the insights gathered through user testing, we move forward to polish the designs. Here you can see the polished designs for the mobile screens and also the desktop screens. And after that, we created a design system with all the elements necessary for development. This is it. Let me know what you think, and if you have questions, feel free to reach out.
