Definicja flow

Założenia są takie:

• 1 projekt

• 1 klient

• 1 analityk

• 1 programista

To definicja relacji pomiędzy dwiema stronami:

• klient-analityk

  • zebranie specyfikacji

• analityk-programista

  • wykonanie planu działania

• klient-programista

  • realizacja i monitorowanie

Współpraca z klientem poprzez narzędzia pokazującą kllientowy wygląd life i pokazujący programistom interakcje, co robi klient jak naciska, itp

Fazy

App design https://books.apple.com/de/book/einf%C3%BChrung-in-die-app-entwicklung-mit-swift/id1215105506?l=de App design ide, tynker https://apps.apple.com/de/app/tynker-learn-to-code-programming-made-easy/id805869467

What is a Product Design Sprint?

It is a 5-phase exercise which uses design thinking to develop a product or feature idea into a prototype that can be tested to help us fill our riskiest knowledge gaps, validate or invalidate our riskiest assumptions and guide future work.

Phase 1: Develop a common understanding of the working context including the problem, the business, the customer, the value proposition, and how success will be determined
Phase 2: Generate insights and potential solutions to our customer’s problems.
Phase 3: Come up with a realistic prototyping storyboard and develop an assumptions table to guide our prototyping and testing phases.
Phase 4: Build a prototype that can be tested with existing or potential customers. 
Phase 5: Test the prototype with existing or potential customers. 

What we deliver during a Product Design Sprint Early validation for your product

During the sprint we decide what to test, how we’re going to test it and then run a handful of interviews to validate our assumptions. You gain invaluable insights into the mind of your customers in a concise timeframe. Team understanding and alignment

The sprint is designed to get all team members aligned on both why and how we’re going to solve problems. We generate ideas together which fuels innovation. Because we working together, you’ll get buy-in from your whole team. A prototype and recorded interviews

You will have recordings of the interviews and the prototype that we created but the most important deliverable is the understanding you get at the end of the sprint. We’ve had several client’s use the prototype to secure funding from investors to continue to move their product forward.

My First Product Design Sprint

Last week, I had the opportunity to be part of my first product design sprint. It was an exciting, exhausting, and intense learning experience that I want to share some tidbits of.

We did the sprint together with Andreas from Promoter: A Stockholm-based startup that helps game developers and publishers track press mentions and to distribute keys and promo codes to journalists.

Andreas and I were joined by Teo and Reda. Both Teo and I are developers in our Stockholm office and Reda, who facilitated the sprint, is our design director.

The goal of the sprint was to increase the number of people trying out the service after visiting the site.

Over the week we went through many of the exercises outlined in our Product Design Sprint guide. Here are some of my favorites:

Five Whys

The Five Whys exercise is used to dig deep into the reasons of a problem to get to the very root of it. It’s done simply by writing down a problem and then asking “Why?” five times, each time writing down a new problem based on the answers.

I found it fascinating that with some added structure, asking the same question five times can provide new insights.

Crazy Eights

Crazy Eights is a short exercise to generate lots of ideas really quickly. It’s done by folding a paper in half four times to produce eight panels and then spending a maximum of five minutes filling them with really rough sketches of eight different user interaction ideas.

We did this exercise a couple of times throughout the sprint and it really helped to jump-start my creative thinking.

Silent and Group Critique

After some rounds of crazy eights we dove deeper into the details of our best deas with the Story Boarding exercise, sketching out flows through the UI.

We followed up on this with both silent and group critique. During the silent critique everyone posted their ideas on the wall. We then individually looked at all of them, putting dot stickers on parts we found interesting or had questions about; this made some of the ideas really stand out.

We went through all the parts with dot stickers as a group, asking everyone what they liked about them.

This way all voices were heard.

Summing Up

As a developer, taking part in a product design sprint was enlightening; it taught me new things about design thinking, introduced me to exercises to help channel my creativity, and showed me new ways of approaching problems.

After the first days, I also had a solid understanding of the product and the problem it was solving. I would have no trouble jumping onto the project, making informed decisions about implementation and prioritization while building out features and squashing bugs.

Having developers take part in product design sprints is also beneficial to the sprints since it diversifies the perspectives and allows for valuable feedback that can avoid wasting time testing out technically unfeasible solutions.

We think product design sprints are an effective and efficient way to learn and to validate ideas and concepts. Therefore, we’d like to do more of them in Stockholm. If you think it sounds interesting, get in touch!