background preloader

The product design sprint: a five-day recipe for startups

The product design sprint: a five-day recipe for startups
At Google Ventures, we do product design work with startups all the time. Since we want to move fast and they want to move fast, we’ve optimized a process that gets us predictably good results in five days or less. We call it a product design sprint, and it’s great for getting unstuck or accelerating projects that are already in motion. I’ve planned and run over 100 of these sprints, first with teams at Google and now with startups in the Google Ventures portfolio. Over the next several posts, I’ll be sharing a DIY guide for running your own design sprint. Before the sprint: Prepare Get the people and things you need. Day 1: Understand Dig into the design problem through research, competitive review, and strategy exercises. Day 2: Diverge Rapidly develop as many solutions as possible. Day 3: Decide Choose the best ideas and hammer out a user story. Day 4: Prototype Build something quick and dirty that can be shown to users. If you think you’ve heard of this model before, well, you’re right. Related:  TrabalhoResources @petermayerla

The product design sprint: setting the stage At the Google Ventures Design Studio, we have a five-day process for taking a product or feature from design through prototyping and testing. We call it a product design sprint. This is the second in a series of seven posts on running your own design sprint. Now that you know what design sprints are good for, you’ll need a few important ingredients to make yours successful. Pick a big fight The first thing you need is an important design problem, and if you work at a startup, chances are good you probably have one lying around the office. As long as it’s an important problem, it’s perfect for a design sprint. Get the right people The ideal sprint team is between four and eight people, but you can get by with more or fewer than that. Designer – If your startup doesn’t have a designer yet, try to bring in a ringer.CEO – At a small startup, the CEO is the key decision-maker and needs to participate in order to get an actionable solution out of the sprint. It’s also great to include:

The product design sprint: prototype (day 4) At the Google Ventures Design Studio, we have a five-day process for taking a product or feature from design through prototyping and testing. We call it a product design sprint. This is the sixth in a series of seven posts on running your own design sprint. On day 2 you drew concept sketches. This part of the sprint is super exciting for me as a designer. But wait a second… what should this prototype look like? What your prototype should look like Quite simply, a prototype is anything a person can look at and respond to. Make it minimally real You’ll probably be amazed at how much real feedback a user can give you on a slide deck of mockups that aren’t even pixel-perfect. They can tell you what they understand about your product — and what they don’t. You’ll also learn things that metrics alone can’t tell you, in particular why users do the things they do, rather than just what they do. Why? Keynote versus code Occasionally you’ll need to write some code for your prototype.

Sketchboards: Discover Better + Faster UX Solutions The sketchboard is a low-fi technique that makes it possible for designers to explore and evaluate a range of interaction concepts while involving both business and technology partners. Unlike the process that results from wireframe-based design, the sketchboard quickly performs iterations on many possible solutions and then singles out the best user experience to document and build upon. It’s what we do well Designers love the “breakthrough moments” in a working relationship. The ability to convey a solution pictorially Showing a solution is more vivid and far less abstract than talking or writing about it; pictures are both louder and more clear than words.The ability to presuppose new solutions Despite incomplete information about the problem, designers make instinctual leaps to offer potential solutions that would not have been arrived at through deductive logic alone. The trouble is that these moments are all too rare on normal design and development projects.

Driving Corporate Innovation: Design Thinking vs. Customer Development Startups are not smaller versions of large companies, but interestingly we see that companies are not larger versions of startups. I’ve been spending some time with large companies that are interested in using Lean methods. One of the conundrums is why does innovation take so long to happen in corporations? Previously Hank Chesbrough and I have written about some of the strategic issues that impede innovation inside large corporations here and here. Two methods, Design Thinking and Customer Development (the core of the Lean Startup) provide the tactical day-to-day process of how to turn ideas into products. While they both emphasize getting out of the building and taking to customers, they’re not the same. Urgency Drives Innovation SpeedStartups operate quickly – at a speed driven by the urgency of a proverbial gun-to-their-head called “burn rate.” In large companies, the employees are no less smart, but the organization is optimized to deliver repeatable products, revenue and profits.

How To Become a Millionaire In Three Years /* This was originally a comment made in response to a hacker news thread titled: Ask HN: How to become a millionaire in 3 years? . The comment has over 200 upvotes, which means people found it useful. I decided to add more thoughts, refine existing ones, and put it in a permanent place. This is just my own humble advice and I hope it’s useful for entrepreneurs. I move forward the only direction Cant be scared to fail in Search of perfection -Jay-Z, On To The Next One I’m going to go and replace 3 years with a “short time frame”. Market opportunity- A million dollars is not a lot in the grand scheme of things, but it certainly is a lot if the market opportunity is not large enough. Inequality of information- Find a place where you know something that many undervalue. Leverage skills you know- You can go into new fields such as say Finance, but make sure you’re leveraging something you already know such as technology and/or product. Stick with it- Don’t give up too fast.

The product design sprint: understand (day 1) At the Google Ventures Design Studio, we have a five-day process for taking a product or feature from design through prototyping and testing. We call it a product design sprint. This is the third in a series of seven posts on running your own design sprint. Now that you know when to get your team together for a sprint and how to set one up, it’s time to tackle the first day of the sprint: understanding. Chances are that everyone involved in the sprint has different perspectives on the problem — and different information that might be helpful. Use these exercises to help build understanding We use the exercises below to get a ton of information on the table and quickly build understanding. During the exercises, everyone in the sprint should be jotting down questions on sticky notes. Business opportunity — The CEO or product leader should walk the sprint team through the business opportunity and market. Lightning demos — Look at competitors’ products. Feeling overwhelmed?

User Interface Design Libraries for Keynote, PowerPoint and OpenOffice Save 10 hours on your next app design project, GUARANTEED! When you buy a bundle, you get all 9 templates for 50% off the total price, and you receive all future updates for free. Each template includes both Keynote and PowerPoint files. 100% Money Back Guarantee Try Keynotopia ABSOLUTELY RISK FREE. If for any reason, you’re unhappy with your purchase, contact us for a FULL REFUND. Free Lifetime Updates Keynotopia is updated regularly. Fast And Secure Checkout Frequently Asked Questions Can I edit/customize the components? Absolutely! I am using Adobe CS tools (Fireworks, Illustrator, Photoshop). Yes. I’ve purchased the prototypes. Which program should I use to test the prototypes on the iPad and iPhone? Use Keynotopia iPhone and iPad apps. I would like to use it on the iPad. Yes. I am done with my prototype. You can. I am using a Windows machine. Yes you can, using the Powerpoint bundle.

Prototyping in Systems Analysis Prototyping in Systems Analysis Introduction Organizations of all types do it. Microsoft, Disney, and Boeing do it. This paper will look at what prototyping is to systems analysis. Table of Contents What is Prototyping? As mentioned earlier a prototype is like a model or a simulation of a real thing. A survey of MIS managers in Fortune 1000 firms [3] suggests that there are four prototyping methodologies in use today which supplement the traditional systems development life cycle: Illustrative: produces only mockups of reports and screens. Others suggest such categorizations as evolutionary versus throw-away [10]. Another way that prototypes are classified is by the fidelity of the prototype, or the degree to which the prototype represents the appearance and interaction of the system.[4] A low-fidelity prototype is one that is quickly constructed to depict concepts, design alternatives, and screen layouts. Included in the chart above are terms used to describe other prototyping concepts.

Related:  flipped classroom