29 August 2019Comments are off for this post.

From Branding to UX & UI Design – Chop Chop case study

We want to show you how the design process of our app prototype - Chop Chop - looked! As there are a lot of misunderstandings and myths around design during the software development process, we want to explain how we came up with the idea of Chop Chop, and how our Design Team approached this project.

This will give you an insight into how our team works on any given project and how valuable all stages of the design are to make a successful digital product.

How it all started

As Chop Chop (you will learn how we came up with this name later on!) was our internal project, we had a Product Owner* on board. Our Partnership & Growth Manager Ashmeet was an initiator of the project and he took the role of Product Owner. He was responsible for the preliminary research that helped to give our idea a more coherent form. And what exactly was our idea?

Product Owner is a scrum development role for a person who represents the business or user community and is responsible for working with the user group to determine what features will be in the product release.

Our goal was to create a recipe app for Millennials and Generation X with easy-to-follow and personalized recipes. We know that recipe books are good, but they are not always accessible. We wanted to give recipe creators a modern platform to share their recipes with their followers.

Brand Design

To kick off the design process of our app, we started with a brand creation stage. Comprehensive, consistent and high-quality branding is crucial when it comes to the success of a digital project. As Will Rogers said, “you never get a second chance to make a great first impression.” This rule works with apps and digital projects, as well as with people.

As you can see on the graph below, the average app loses 77% of its DAUs (daily active users) within the first 3 days after the install. Lousy branding and poor visual identification can play a big role in this negative process. If your app is visually unappealing or the stylescape of the app doesn’t fit the project, your users might be more inclined to uninstall your app.

Graph: Average Retention Curve for Android Apps

For our app’s branding, we started from the very beginning following the research we mentioned earlier, we knew what kind of project we wanted to build but we didn’t have a name for it! That’s when our Senior Graphic Designer and Branding Specialist Michał stepped in.

The first step for Michał was to meet with the Product Owner for an interview, during which he tried to gain as much information as possible about the project, its purpose, target group, business goals, etc. Ashmeet explained in detail the whole idea of the project, as well as the results of the research.

Name creation workshops

The next step for creating a brand identity was a brainstorming workshop to create a name for our app. A lot of the time, people choose the name for their project randomly, not paying enough attention to this important step. At Setapp, we understand the importance of a great name for a digital project. There are few elements that you always need to remember while creating a name for your app:

  • Try to create a brand name that connects with a product. Obviously, it’s not a must but a name that automatically connects with the app’s purpose makes it much easier to sell. Doesn’t Chop Chop immediately bring the vibe of a culinary experience?
  • Keep in mind the language of your users. If you’re creating an app solely for Chinese market, consult a native Chinese speaker whether the name sounds right. It’s best to come up with a name that sounds right to anyone, no matter age or native language. That’s what Chop Chop does. No matter if you’re young or old, your native language is English or Japanese, Chop Chop immediately makes you think about cutting and cooking something delicious. Perfect for a cooking app!
  • Make it easy to remember. A perfect name stays in your mind after hearing it just once. That’s why the name should be short and easy to pronounce.
  • Originality is a must. The branding specialist who carries out the brainstorming workshops has to make sure that the name you decide on is new and original. You don’t want your project to be mistaken with any other and if your brand name is not original enough, you could find yourself having difficulties with various registrations and even possible litigation from existing brands.

With all those rules in mind, our Branding Specialist Michał carried out a brainstorming workshop for our project. He invited several people, based not only on their creative skills, but also on their proximity to the target group. Our branding workshops consist mainly of team based tasks but there is also some individual effort. By the end of the day, all the members of the group had decided that Chop Chop was clearly the best name that meets all the requirements of our project.

As the name was now ready, Michał was able to start working on the logo and the visual identification of the project. It is important to note that the results of his work had a huge impact on UI (User Interface) creation that happened later.

Chop Chop’s logo, in a similar manner to the name, immediately sends a message out about the scope of the project. The invisible knife works great with the name Chop Chop and it’s also very flexible when it comes to animated visuals.

Chop Chop - cooking app logo

With the whole branding ready, our UX Designer Agnieszka was able to step up and work on the User Experience of our project.

User Experience Design

After the successful brand creation process, it was time to build the User Experience (UX) for Chop Chop. Our UX Designer Agnieszka started her work by conducting an in-depth analysis of the project, its target personas, business goals and the competition analysis. Some of those things were done by the Product Owner at the beginning of the whole process but it was necessary to make significant refinements and in-depth analysis solely for the purpose of UX Design.

To prepare a high quality User Experience, it was essential to clearly define target personas of the project, its business goal and its value for the final consumer. It was also very important to go through the benchmarking process and analysis of the competition.

Another crucial part of the whole process were the interviews with a carefully selected group that resembled the target personas decided earlier on. We try to not work on assumptions - it’s important to do things based on facts, data and the results of analysis, rather than our gut feelings. Key insights from the interviews were:

  • Users usually use Google search to find recipes. Therefore, a search feature within the app is a must-have.
  • Some of them use tags (e.g. ‘vegetarian’ or a certain ingredient e.g. ‘tomato’) on websites to filter the recipes. Hence, filters are a must-have.
  • All users pay a lot of attention to images, they click on the recipes which present photos of ‘mouthwatering meals.’ Therefore, high-quality pictures would be a welcome addition.
  • Users look for recipes on the Internet when they want to be inspired, want to prepare something delicious for guests or they have some ingredients which they want to use to prepare a meal.
  • As users want to be inspired, a recommendation section would be highly appreciated.
  • One user said that he makes multiple portions of the meal (not to waste opened ingredient packs). This means we should add some kind of calculator.
  • Users usually cook using written recipes.
  • Users often browse the comment sections to see other people’s opinions and genuine pictures of the food they made. Hence, we should provide users the possibility to add comments and to rate the recipes.

UX Interviews gave us a lot of very important feedback. It was crucial to understand the problems that amateur cooks have, their action flow while cooking and what they’re looking for in a cooking app. We got a lot of feedback that truly changed our perspective and had an impact on the scope of our project.

For example, one of our interviewees said that one of her worst cooking experiences was making a crème brûlée. She had all the ingredients ready and started cooking but when she was almost done, she realized that she didn’t have a blowtorch to finish off the dessert. She was mad that her cookbook didn’t clearly state the unusual equipment required at the beginning of the recipe. That’s why, that apart from the ingredient list, we decided every recipe in Chop Chop will also have an equipment list clearly visible.

User stories and User Flow

After finishing up the interview process, our UX Designer Agnieszka was ready to create user stories. Not going into details, User Stories for UX Designers are short sentences that look like this: “As a user I want to … [basic user goal].” Based on those stories, designers get to know exactly what the potential users of your app want to accomplish. As you might guess, every project has multiple user stories.

Once Agnieszka was done with gathering all the User Stories, it was time to create a User Flow. It is an essential part of a UX Designer’s work. It covers all of the actions that might be done by the user throughout the app and it connects them all in a logical manner. A UX Designer’s job is to make the User Flow as intuitive as possible, while covering all of the possible ways to interact with the app.

Chop Chop - cooking app user flow

Agnieszka always kept in mind the creativity of the users and their tendency to choose the most unpredictable ways of using the app. A digital product needs to be ready even for the most demanding clients.

It is also crucial to make the app responsive in all scenarios, even when things go wrong. A lot can happen with the device that can have an impact on how your product works. Your app needs to be ready for every scenario. If it crashes (every app crashes from time to time), you want it to go back to the last page opened when you open it again. That’s why a UX Designer’s job is so important - it outlines how the app works and interacts, once the development work is done.

Chop Chop - cooking app UX wireframes

When Agnieszka finished with her UX work, she passed the torch to Paweł - our User Interface (UI) Designer. But it was not the end of her work. She kept consulting Pawel all the way to the finish line to make sure that the UI reflects the needs of the prepared UX. That’s why it’s so important to have a team that works well together - just like ours!

User Interface Design

User Interface design was the last part of our design process with Chop Chop. Paweł, our UI Designer, worked closely with Michał who prepared branding of the product, and Agnieszka, UX Designer, who made an extensive User Flow. We had to align all of those elements to make sure that the results of our work are satisfying to all sides of the project.

While a black design of Chop Chop is in line with the current design trends (dark mode), the trends were not the only thing that guided Paweł. He purposely used black theme to make the pictures of food stand out and look as juicy as possible!

As you may have noticed - Chop Chop has an exceptionally big pictures for a mobile app. Again, it was a deliberate move by Paweł to make every recipe to look as attractive as possible.

Chop Chop - cooking app design

Fun fact: our UI Designer Paweł is also a professional cook! He knows best how to make a delicious looking food - it clearly shows in Chop Chop!

User Interface of Chop Chop is also controllable by voice commands. Isn’t it annoying when you need to clean your hands and stop what you’re doing, just to check the next step of the recipe? That’s when voice commands come real handy!

But for those who actually like to click through their app while they're cooking - Chop Chop’s UI consists of large buttons and clickable elements so it’s easy to click on the right thing, even if your hands are dirty.

You can check the results of Paweł’s UI work in the video below. Chop Chop got a modern, stylish look that doesn’t steal the attention from what matters the most in cooking apps - the pictures of food and recipes! Don’t you all love it?

Summary

Chop Chop gives you a proper idea of how design process looks like at Setapp. We have incredible, experienced specialists on board who take any project through the design process to deliver amazing results.

What is crucial to point out is that while every member of the Design Team has his or her own area of expertise, it also takes a lot of teamwork to deliver great designs. All stages of the project must be aligned with each other to create a coherent and high-value design experience!

Impressed by our Design Team's work?

Take a look at our team's portfolios and feel free to contact them! They'd be more than happy to talk about the design process at Setapp.

Looking for an excellent Design Team?
Start with Design Sprint and create your digital project with us!

26 February 2019Comments are off for this post.

How to save money & reduce risks with Design Sprint

Before we begin we need to clarify the naming issue. You can find many different names of the same thing circulating all over the internet - Design Sprint, Product Discovery Workshops, Service Design Workshops, Product Design Sprint, Innovative Workshops, Google Sprint etc.

We decided to stick to the original name - Design Sprint. If you’re more familiar with a different name - don’t worry, we’re talking about the same thing!

In 2010 Jake Knapp, a Design Partner at Google Ventures, created a time-constrained process that uses design thinking with the aim of reducing the risk when bringing a new product, service or a feature to the market. In those 9 quick years, Design Sprints have taken the world by storm.

At Setapp, we are always trying to use the latest innovations - be it the new technologies or up-to-date processes. We’re constantly looking for ways to be better at what we do. Conducting high-quality Design Sprints is no different. But it’s not a ‘copy & paste’ process for us - while we’re familiar with the original ideas of Jake Knapp, we have taken them and made them our own.

Our Design Sprints are based on Design Sprint 2.0 - a new and improved version of the original idea. Design Sprint 2.0 idea was developed by AJ&Smart to wrap the whole process up in 4 intensive days of creativity and cooperation.

What is a Design Sprint?

So what exactly is a Design Sprint? It’s essentially a 4-day intensive process to develop a working prototype, get feedback from users, build a plan for next steps and understand the full potential of a project.

The whole process is split into two parts. During the first half, we work with a client at our HQ. After that, our designers get back to their rooms to deliver a working prototype, tested on real users. Our clients can then relax and wait for the results of our work.

 

Design Sprint Peter

 
Who takes part in the Design Sprint?

You might ask yourself - who exactly takes part in a Design Sprint? From our side you can usually expect a UX Designer, Software Developer and Scrum Master. Keep in mind though that this composition is flexible. We adjust it to the specific needs of every single client.

From the client’s side, we expect at least three people. It’s up to the client to choose the people best fitted for their project. We recommend picking people most engaged in it, as they will be the source of information for our experts. Usually, CCOs (Chief customer officer), CTOs, Product Owners or Sales Managers are good picks.

It’s also very important to keep in mind that there’s no Setapp Team and Clients’ Team during the Design Sprint. We are one team and we work together towards the common goal. To help us all achieve that, there’s also one additional (yet extremely important) person in the team from our side - the facilitator. He guides everyone through the process, keeps everything in line and makes the whole thing smooth, effective and enjoyable.

 

Design Sprint Group

 
Who should be interested in Design Sprints?

You might be asking yourself - is a Design Sprint for me? Can it resolve my concerns and problems? Does it fit the needs of my project?

Design Sprints are not created to solve all kinds of problems. If your issues are relatively basic, there are other ways to validate them - Design Sprints might be excessive. The same goes with the risks involved with the project. If they’re low and your project is fairly safe to deliver - don’t bother with a Design Sprint.

In general - if you’re very confident that your proposed solutions will be successful and everything is set, then you can spend your time on something different than a Design Sprint. But we know that a lot of your problems are not low risk, simple issues and it’s increasingly harder to be confident in your solutions with no working, tested prototypes.

There are tons of reasons to run a Design Sprint on your project. It’s impossible to include them all here, but we can highlight the ones that are most common:

  • You need a prototype of a project to get funding.
    We are aware that getting funding is a major issue for a lot of startups. Design Sprints are a perfect tool to achieve that - there are not a lot of things that help to sell your project better than a working, tested prototype.
  • You don't want to waste months to start a project.
    As Shirley Temple once said: "Time is money. Wasted time means wasted money means trouble". Not a lot of entrepreneurs can wait for months to see the fruits of their labor. Design Sprints allow us to deliver results after just one week of hard work.
  • You get stuck with some kind of barrier and don't know what to do next.
    We’ve seen it many times when great projects were stopped by one issue because the team didn’t know how to overcome it. What’s even worse - we’ve seen teams ignoring the most burning issues because it was the easiest thing to do. Design Sprints can help you overcome even the hardest and most challenging issues you face.
  • You want to reduce risks by creating a working prototype.
    There are so many risks facing every project - financial, technical, external etc. Having a tested working prototype significantly lowers all kinds of risks and boosts your project efficiency.
  • You have a big project but want to check part of it before going full steam ahead.
    Huge projects are rarely delivered all at once. It’s way too risky, it makes no sense financially and it’s really complicated. That’s why it’s important to test and deliver the most important parts of the project separately. That’s when a Design Sprint comes in handy. It’s much easier to deliver the rest of your idea, when you know that the core of it is tested.
  • Your team seems to be out of creative solutions.
    We know that a traditional, lengthy development process is not the perfect environment for creativity. That’s why Design Sprints are so great - because of their condensed program, people involved in them don’t get tired and bored with a process. It’s rare to see so many great ideas in such a short span of time. That’s what we call a culture of innovation.

 

Design Sprint Wall

 
What is the outcome of a Design Sprint?

The outcome of our Design Sprint is an interactive prototype, verified by real users and with a coherent recommendation of what should be your next steps. A Design Sprint's outcome is definitely not some kind of paper prototype or blueprint. You get an interactive prototype that feels and looks like a real product.

You also get a clear vision of what your next steps can look like. It all depends on your project, but if you’re ready for development, you can easily move on from a Design Sprint into an Agile Sprint. That’s when we start coding, engineering and designing to build a final product (or MVP).

What is the most important outcome of the Design Sprint is a validation of your idea. Validation, combined with a tested, working prototype, can give you the confidence that your project is set for success.

 

Design Sprint Desk

 
Recap

A Design Sprint is a great way to kick off a project. It can truly change the client’s perspective, it boosts creativity in a way that normal development can’t and it significantly reduces risks. Obviously, it’s not a solution for everyone. But if your problems are complex, broad, difficult and they’re critical to the success of your project - we can’t recommend Design Sprints enough!

Also check our next article where we discuss in details the whole process of Design Sprints! You will learn how every single day of Design Sprint unfolds and what are the values of each stage.

Crystallise your product vision
With Design Sprint get an interactive prototype in one week

5 September 2018Comments are off for this post.

The 3 most common misconceptions about design in IT product development

”Well, design in product development will take too much time and money. At the end of the design process, all I’m going to have are a few mockups and still no product. Why should I waste time and money, if I could just start the agile product development process right away?”

If you’ve ever thought about skipping the design phase to save some time, then this article will give you insights that prove the opposite. In the following paragraphs, I am going to tell you how easy it is to fall for some common misconceptions about design, how and why you should push away those thoughts, and last but not least, I am going to tell you why design should be at the forefront of your development process. Let me start with a short story of how I got introduced to the world of design.

We all are designers. Are we not?

7 years ago, when I was building my first CRM I wondered how to approach it best. I had a business and tech background but had no relevant experience in design, which allowed me to approach the design aspect of this project without biases.

That’s how I “invented” user personas and user journeys. I spent 2 weeks interviewing the sales department and other stakeholders. I created mockups that demonstrated step by step real jobs-to-be-done and real activities of sales representatives and their managers. All cool but these tools and knowledge had already been there for years. I could have used them earlier. Why didn’t I?

Around that time, people were caught up in the information pollution, and design had become a buzzword and lost its true meaning. There was a time when to me design was synonymous with a fancy awkward chair. I had zero curiosity about design - I thought that learning more about Design was a waste of time. However, with time, I learned about service design and design thinking, and I found a missing link between idea and execution.

Misconceptions about Design in IT

When design became a “thing”, people started to use the word design (as a noun) more often for describing the end result of designing (verb). Most of them had an opinion about designs (noun) but they were lacking the context and the purpose for which it was designed. They saw a distorted picture of what design really is.

During my years as an entrepreneur, I learned that these are the most common misconceptions about design in product development (from my experience in the IT industry):

1. Design is about making products look beautiful.

Sure it is. People buy with their eyes. But it’s just one part of the truth. Design in this context is about great interactions with the product and the look is just one final layer of product.

Most importantly, it is about translating business, market and tech insights into a usable product that people will buy.

2. The Design Process is unmanageable and chaotic. 

Not true. For example, brainstorming without a clear goal can be unpredictable but for professional designers that’s not the case. Design tools and activities are organized in a well-defined process.

In general, there are 4-5 stages, each with different objectives, inputs, activities, and outcomes. They can vary between different approaches, frameworks and methodologies (Service Design, Design Thinking, Design Sprint, ect.), but generally, the rules or framework are very similar.

3. Design with all those post-its doesn’t look professional.

From a distance, it may look that way. But once you’re fully immersed in the project you’ll see that you are tackling really important questions and critical issues. Businesses want innovation but real innovation doesn’t look like innovation, it looks like an inside joke that nobody gets. “Electric supercar? Yeah, right”. “Phone for $599? Yeah, sure”.

So what’s Design really about?

Let’s keep it simple- design is...

  • about profitability, feasibility, and usability
  • manageable and measurable
  • bout the effects on the users and the business

But let’s go deeper into the topic because I think there’s much more to understand about design and it has nothing to do with beautiful and aesthetic deliverables. Keep reading!

Unknown risks and opportunities

Most products fail because we try to invent the wheel. (Here, wheel = the framework for problem-solving, design and development that design is a big part of) Instead, we can use tools, an approach and a mindset that was defined and tested out over the last few decades.

Without this framework and guides, design in product development (especially in the IT . industry) is blind and based on guessing and invalidated assumptions.


If you would like to learn more about Design Sprints - a known and tested Design Framework - head over to our introduction of this 5-day framework. You'll learn all about the benefits of running a Design Sprint Workshop at your company.

The main benefits of design in product development

Design could be called a mindset rather than an activity or any specific approach, toolbox or methodology. This mindset arranges different tools, processes, and frameworks to solve product development challenges. Here are a few benefits that this mindset can bring to your project:

1) Clear vision: 

It helps to set a clear vision in the presence of a dozen stakeholders with different agendas. Design and collaboration go hand in hand. Design workshops are an opportunity for a team to untangle a problem together by going through a series of exercises designed to get to a specific outcome.

2) Clear roadmap:

It helps to define a clear roadmap in the presence of hundreds of requirements and assumptions. Design is a neat framework that organizes requirements and solves complex business/technology/market problems. When you consider the determinants of a successful product, you can divide them into dozens of categories:

It’s almost impossible to take into consideration all of the dimensions of information without a proper framework!

3) Manageable risk: 

It helps to test assumptions, manage what's known or defined and helps to uncover unknown risks and challengesWhen the product domain is explored it’s much easier to identify key factors that can impact your product. These risks are turned into assumptions and tested.

Also, design reduces risks of exceeding the budget or creating something that nobody wants. I can’t tell you the exact number but from my experience working at several software houses, I have never seen a project over $25k that went well without any design process at all.


In case you're already familiar with the Design Sprint Framework, read our article about what you can expect during a Design Sprint, where you'll get a glimpse at the 5 Design Phases + handy tips to run the workshop yourself.

Key takeaways

Less waste 

Many times design is as underestimated as a backup file. You understand the value of backups once you lose all your precious data. And you will value design once you lose 3+ months of work and still have a useless product that nobody wants to buy. This is no exaggeration 😀

Buyable products

Design is very important because otherwise, you’ll end up building something nobody wants and your product will fail.  Remember that there is a huge gap between what we think people want and what they really want. That’s why design emphasizes on the customer so much and starts with the discovery phase.

Less risky journey

When the product scope is explored, it’s much easier to spot risks that can impact your product. These risks are turned into assumptions and tested. Design reduces risks of exceeding the budget or creating something that nobody wants. From my experience working at several software houses, I have never seen a project over $25k that went well without any design process.

Mindset for growth

As I wrote earlier, design is more of a kind of a mindset so the purpose of this article is not to convince you to use some specific tools or processes but to give you the taste of how this mindset works and how it can help not only your products but your entire business.


I hope this article shed some light on some mistaken notions about design and why design in product development is critical. If you are struggling about how to implement design in your software development process or you simply want to discuss which frameworks would suit your company better, send us a message - we would be happy to help you!

7 August 2018Comments are off for this post.

Test and validate your product within 5 days using Design Sprints

Imagine that you’ve just had an epiphany and found the solution to an unanswered problem. “This makes a great business idea. I need to build it!”. Wouldn’t you want to fast-forward to the future and see your finished product and how it interacts with its users? The Design Sprint will give you that superpower.

With this framework, you don’t even have to make any costly commitments. To explain it more thoroughly, I will go through it step-by-step. Firstly, I want to give you an idea of:

  • how the DS came to be
  • what it is
  • what are the benefits of implementing it
  • why it should matter to you

In the next articles, I will address the process (day-by-day), the activities that help unleash a team’s creativity, and lastly, what our process at Setapp looks like. So if you like the idea of cutting to the chase, to end useless debate cycles and compress months of time into a single week, then keep reading!

And btw, if you want to learn how to use Design Sprints to jumpstart your product, let me know and we can have a chat.

The birth of the Design Sprint

‘Efficiency’ and ‘quick results’ became part of our daily vocabulary as businesses and technology started to move faster. Many teams realized that they needed to abandon the traditional non-software inspired waterfall process if they wanted to keep up with new tech and emerging products. As a result, businesses shifted to iterative development methodologies like Scrum to implement measurable quick iterative cycles of development - also called ‘sprints’.

Then around 2010 in Google, Jake Snapp, created the first version of Design Sprints when he was looking for a quicker process to design and launch products rapidly. His framework soon became the ‘de facto’ means of testing & building products throughout Google’s teams which enabled them to launch products in weeks - not months or years!

In 2012, Jake and his colleagues started running the Design Sprints with the portfolio startups of Google Ventures to help them make daring, data-driven, and user-focused decisions. By 2016, their legendary Sprint book came out, and companies like Uber, Slack, Airbnb, Lego, and Medium have used DSs to improve their products and make their businesses more profitable.

So what is a Design Sprint*?

*People often refer to it using different names: Product Discovery Workshops, Service Design Workshops, Product Design Sprint, Innovative Workshops, Google Sprint, and others. For the sake of this article, I’ll refer to it as Design Sprints - it’s original name.

“A Design Sprint is a five-phase framework that helps teams to answer critical business questions through rapid prototyping and user testing”

Based on Design Thinking** methodologies and (Agile) Sprints, the primary goal of a Design Sprint is to reduce the risk of bringing a new product or a new feature of an existing product to the market by building & testing a prototype in only 5 days (Monday to Friday).

** Note that Design Thinking and Design sprints are two different things, while DT is the foundation, philosophy, and a toolkit for innovation, Design Sprints are a specific step-by-step system for producing and testing new products or ideas.

During those 5 days, the Sprint team will go through various phases such as:

  • understanding
  • ideating
  • deciding
  • prototyping
  • testing

 

design sprint 5 days

I will go through this process and phases in detail in my next article.

Who can participate?

The Design Sprint framework is for big companies, startups, individual teams or anyone that needs to generate new (innovative) ideas. It will replace the traditional brainstorming meetings with an idea-generation machine consisting of a multidisciplinary team.

The Sprint team should consist of 7 or fewer members and people from different disciplines is invited. Be it a marketing or customer service representative, Head of Software Development, CEO, and designers… all experts can participate in the 5-day Sprint sessions. This way, the team of experts - and the decision-maker - can solve problems together more smartly and effectively.

design sprint

Why run a Design Sprint?

If at this moment you - as an entrepreneur, Product Manager, CEO, or Customer Service Leader, etc. - have….

  • An idea for a product or service
  • A problem that you can’t find a viable solution for
  • An MVP that needs it’s solutions to be validated
  • A product that doesn’t engage users
  • A product that requires new features to keep up with competitors

Then Design Sprints are perfect for tackling any of those! Of course, there are many different reasons for teams to run a Design Sprint. It’s important to note that based on their intentions and goals the methods used in the Sprint should be personalized to each case and team. You will get more information on this in my next articles.

Do you share these challenges? Book a call and discover how design sprint can help you achieve your goals

Here are some of the benefits of running a Design Sprint:

1. You save tons of time.

Remember it’s 5 days, and you’ll get the results of the equivalent of 5 months worth of meetings, emails exchanges, and consultations. The smooth collaboration between members of different disciplines and with different skill sets can (and will) spark creativity. As a result, in a very short time frame you will:

  • get real solutions to problems
  • to speed up product discovery
  • help the team to gain crucial knowledge and learnings

2. You save money.

More often than not, many teams build a product that will have to be re-built months later. With DSs, anyone can spot opportunities and risks in those 5 days that will save the team from horror nights. The faster you know what solutions or problems you need and can solve, the quicker you’ll create your prototypes.

3. You take user-centered decisions.

You’ll be working with people from different disciplines and a facilitator, who will oblige everyone to work with respect, empathy, and openness. The team's structure will make everyone to be aware of the customer’s needs, motivations, problems, and expectations at all times. Also, the tools and activities are built around the end-customer, and therefore, during those 5 days the team will try to listen, trust and develop meaningful relationships with them.

4. You get deliverables.

At the end of the Sprint you will not get estimations, speculations or RFPs, but real user-validated prototypes. Moreover, you’ll be part of the whole process: ideation, sketching, prototyping, and testing!

Design Sprints are built in a way where the creativity of every team member will be unleashed.  It doesn't matter if you are not good with sketching, coding, or with numbers. Every team member’s skills will be used to its best and in an effective way. Remember that it’s only a prototype!

Key Takeaways

Design Sprints are not the answer to all your product development problems. You also don’t want to be running Sprints for every single idea, doubt or new feature you want to have. That’s not the point.

You want to use DS when you have encountered an obstacle or/and a complex problem that it’s a critical business opportunity or challenge.  For example, launching your product to a new market, targeting a new customer segment or introducing a feature that will fundamentally change the whole UX of your product.

Also, I want to stress again some of the reasons why Design Sprints would be an excellent addition to your product development efforts. You will:

  • Solve the most complex problems
  • Make your product/feature user-centered
  • Increase your team’s speed and effectiveness to take critical decisions
  • Find the potential risks and opportunities of a product/feature fast
  • Reduce bureaucracy
  • Effectively gather and collaborate within departments
  • Test an idea and prototype quick

In my next article, I am going to go through each day of the design sprint to show you how it all works. Stay tuned!


At Setapp, we have our version of Design Sprints. Our team has mostly used it to help our clients to design and kickstart new products or features. We have seen the value, certainty and excellent results that it brings to our clients.

If you want to find out how you can run a design sprint in your company, send us an email and we'll be happy to tell you more.

 

Book a Design Sprint

OUR OFFICE

Wojskowa 6, 60-792 Poznań, Poland
+48 506 798 998
office@setapp.pl

OUR OFFICES

POL: Wojskowa 6, 60-792 Poznań, Poland
+48 506 798 998
office@setapp.pl

ISR: 220 Hertzel Street, 7630003 Israel

COMPANY DATA

Setapp Sp. z o.o.
VAT ID: PL7781465185
REGON: 301183743
KRS: 0000334616

PRIVACY POLICY

OUR OFFICES

PL: Wojskowa 6, 60-792 Poznań, Poland
+48 506 798 998
office@setapp.pl

ISR: 220 Hertzel Street, 7630003 Israel

COMPANY DATA

Setapp Sp. z o.o.

VAT ID: PL7781465185
REGON: 301183743
KRS: 0000334616

PRIVACY POLICY

OUR OFFICE

Wojskowa 6, 60-792 Poznań, Poland
+48 506 798 998
office@setapp.pl

COMPANY DATA

Setapp Sp. z o.o.

VAT ID: PL7781465185
REGON: 301183743
KRS: 0000334616

PRIVACY POLICY

 COMPANY DATA

Setapp Sp. z o.o.
VAT ID: PL7781465185
REGON: 301183743
KRS: 0000334616

PRIVACY POLICY

OUR OFFICES

POL: Wojskowa 6, 60-792 Poznań, Poland
+48 506 798 998
office@setapp.pl

ISR: 220 Hertzel Street, 7630003 Israel

COMPANY DATA

Setapp Sp. z o.o.
VAT ID: PL7781465185
REGON: 301183743
KRS: 0000334616

PRIVACY POLICY

OUR OFFICES

PL: Wojskowa 6, 60-792 Poznań, Poland
+48 506 798 998
office@setapp.pl

ISR: 220 Hertzel Street, 7630003 Israel

COMPANY DATA

Setapp Sp. z o.o.

VAT ID: PL7781465185
REGON: 301183743
KRS: 0000334616

PRIVACY POLICY

OUR OFFICE

Wojskowa 6, 60-792 Poznań, Poland
+48 506 798 998
office@setapp.pl

COMPANY DATA

Setapp Sp. z o.o.

VAT ID: PL7781465185
REGON: 301183743
KRS: 0000334616

PRIVACY POLICY

klacz
Clutch award badge
topdizajn
svg-image
svg-image
svg-image
svg-image
Instagram Icon
svg-image
svg-image
smart-growth
european-union

©2020 Setapp. All rights reserved.