Rapid Prototyping 1 of 3: Sketching & Paper Prototyping

Have you ever struggled with how to get from an idea to a high fidelity prototype?

Every design has to start somewhere and even at Google we often start with low fidelity prototyping options such as sketching and paper prototyping.

After all, the fidelity of your prototype should match the fidelity of your idea, so stop worrying and start sketching.

Material design resources mentioned in this video:
- Material design color palette: https://goo.gl/NP5o44
- Elevation and shadows: https://goo.gl/OWZzCw

Rapid Prototyping 2 of 3: Digital Prototyping

Have you ever struggled to explain your idea during a pitch, while working with your team, or testing a concept with users? …


Image for post
Image for post

Validate Objectives — Let’s test with real users and get valid feedbacks.

Validate Methods

Image for post
Image for post

Finally, the validation stage.

It allows designers and engineers to test their prototype with actual users to learn what does and doesn’t work.

User Testing

  1. What do users like and dislike in the prototype?
  2. What would they like to improve?
  3. What features did they want?
  4. Does the solution meet their needs overall?
  5. How would they describe the product?
    (3 words that can help in marketing or validate decisions made.)

Then the cycle of understanding / diverging / deciding / prototyping starts all over.

How to set up Marvel with Lookback?


Image for post
Image for post

Now it is time for participants to transform their ideas into prototypes.

Prototype Objectives — You are going to create and build the wireframes, mockups, or prototype that you will actually test with real users.

Prototype Methods

Rapid Prototyping allows you to test out your ideas without investing tons of money, time or resources — and by doing so, you will know earlier on what aspects of your ideas fail and which have potential.

During this stage of the Design Sprint, participants create paper prototypes to learn more about their ideas and get feedback from one another. …


Image for post
Image for post

Decide Objectives — Deliberate about the ideas you came up with in Diverge stage, refine, and choose the best one or some combination of the ideas so that way you get a best possible product.

Decide Methods

Team review & decision on what to prototype

Image for post
Image for post

At this point, the team can discuss the best ideas and decide which ones to prototype.

“No, But…!”

Image for post
Image for post

Now is the time to be critical but no fighting among yourselves.

You can always say “No” but always end with a “But…”. No, we can’t do this but we can always try that.

Image for post
Image for post

Continue to test your assumptions to validate them. …


Image for post
Image for post

Diverge Objectives — Let’s unleash our creativity to create as many solutions as possible!

Once you have an understanding of the product, the design challenge, and your user, it is time to diverge.

The diverge phase is the sensational time when anything is possible. There will be a lot sketching to do at this stage.

Diverge Methods

“Yes, and…!”

Image for post
Image for post
“Yes, and!”

Is about accepting and building on all ideas — your own as well as others’.

Every time there’s that little voice: “no” or “it won’t work” — ignore it! Get that idea down anyway.

Or if you wonder, “I wonder if the platform supports this” — just imagine, “what if it did” and get that idea down too. …


Image for post
Image for post
Define Stage

Define Objectives — Define a key strategy and analyse what’s the best path to actually arrive at the solution.

Define Methods

User Journey

Image for post
Image for post

The define stage is about breaking down the ideas into meaningful categories and defining strategies.

One way is to create a user journey: a map that lists all the stages that someone goes through from learning about the product to becoming an expert user.

If it’s for an onboarding flow. Look at major steps someone signing up for the service.

If you’re trying to create a product, the stages begin from

  • someone learning about your product — perhaps from a…


Image for post
Image for post
Stage 1 — Understand

Understand Objectives — Clarity on the product, user needs, the market, and technical possibilities.

Before design sprint participants can build anything, you need to understand:

  1. Design principles — How is this form factor different from others?
  2. Design challenge — What problem are you trying to solve?
  3. Personas — Who are you designing for?

Understand Methods

Addressing the Gap

What is the team missing at this point that’s critical? What is the riskiest decision or hypothesis you want to test with the users?

For example, new projects lack a clearly defined target user group or user value proposition. This means you may have to focus the sprint on testing features against a few different groups and testing for the best fit. …


How many of you think you need coding skills to build a Minimum Viable Product (MVP)?

The answer is “No!”.

In fact, you shouldn’t start coding until you have validated your idea and the core features of your product/solution?

Still don’t believe me? Watch this video:

You must have heard of Design Thinking but have you heard of Design Sprint from Google Ventures?

Today we are going to show you how you can use Design Sprint to build your MVP?

Image for post
Image for post
Design Sprint by Google Ventures

Google Sprint Design is the same methodology Google uses to develop their new products and whether to invest in new startups. …

About

Design Sprint

Lefty Talents Group — Creative Digital Agency | Software Development | www.Facebook.com/LeftyTalentsGroup | www.leftygroup.com

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store