Google has a reflective culture. Each year they review how they’re doing in terms of innovation and creativity with their Googlegeist surveys. They measure how their employees feel about innovation—do they have the right resources, the right team environment, and the right skills and mindsets? Based on the results, Google takes action to improve their 3 lowest scoring areas.
Day 3 sees us kick off prototyping, and we do this pretty much exactly as stated in the book, so nothing new to report here. It’s noise-cancelling-headphones-on mode for our resident Prototyper, and we’ll have a couple of huddles throughout the day to make sure we’re all on track. We’ll also update the client at the end of the day to keep them involved and show them what we’ve been doing throughout the day.
“Design Sprints proved to be a valuable tool for accelerating our early-stage, service-driven innovation initiatives. The Design Sprint School team and approach have been instrumental in helping us create the environment and the internal capacity to run our Service Design Sprints for internal Ventures and for running Co-innovation at our Cisco Innovation Centers around the world”
You might use a design sprint to start a new cycle of updates, expanding on an existing concept or exploring new ways to use an existing product. For example, we worked with a marketing data company that realized the data it gathered might be useful to other market segments. Building a prototype gave the team the validation it needed and prompted a deeper investment into that product segment, which ultimately was rewarded with a significant increase in sales.
In theory you probably could, and we’ve always been advocates for making the Design Sprint as open as possible, and our aim is to get as many people as possible using it (as long as they do it properly!) however to get all the information in a structured way, and all the toolkit and materials for free, would be really hard and would take hours of piecing bits of information together. Also, most of the information that’s readily available is on the internet (including our own) speaks to a total beginner audience, whereas the material in our course, while suitable for beginners, will give you a deep-dive into the Sprint and all the process and materials around it. The toolkit we provide as part of the course is the actual ‘live’ stuff we’re currently using with our Sprint clients, and we’ve never made it readily available, and to our knowledge, there isn’t anyone else putting this stuff out there.
The big idea with the Design Sprint is to build and test a prototype in just five days. You'll take a small team, clear the schedule for a week, and rapidly progress from problem to tested solution using a proven step-by-step checklist. It's like fast-forwarding into the future so you can see how customers react before you invest all the time and expense of building a real product.
Your sprint began with a big challenge, an excellent team—and not much else. By Friday, you’ve created promising solutions, chosen the best, and built a realistic prototype. That alone would make for an impressively productive week. But you’ll take it one step further as you interview customers and learn by watching them react to your prototype. This test makes the entire sprint worthwhile: At the end of the day, you’ll know how far you have to go, and you’ll know just what to do next.
This is Chapter 1 from “Design Sprint: A Practical Guidebook for Building Great Digital Products,” by Richard Banfield, C Todd Lombardo, and Trace Wax. Design Sprint was just recently named one of the 100 Best Product Design Books of All Time by The Book Authority (#8 for those who are counting!). NOTE: I have included links to additional, related Design Sprint resources within the post that are not part of the book chapter. These resources are denoted by a “- — -” divider.
Once we have an understanding of the foundation we all need to run a successful design sprint, we kick off by working through the sprint’s Monday exercises — setting a proper long term goal based on our sprint challenge, determining our sprint questions, creating a map, interviewing experts, connecting our personas to the map, and selecting a target.
Page 36 - ... them because of the difficulties of going back and starting afresh. From his case studies of architectural design, Rowe (1987) observed: A dominant influence is exerted by initial design ideas on subsequent problem-solving directions . . . Even when severe problems are encountered, a considerable effort is made to make the initial idea work, rather than to stand back and adopt a fresh point of departure.
Jeff Grant is responsible for innovating the retail security experience for the world's top electronics retailers. He's designed satellite hardware for NASA, invented toy and game concepts at IDEO, and transformed the customer experience at Bank of America. Jeff works to inspire and synthesize the efforts of inventors, designers, marketers, engineers, researchers, builders, and storytellers.
After a career in user experience design and research at companies like Microsoft and Nuance, Trace then became a developer at Pivotal Labs, and is now a Managing Director at thoughtbot. He has facilitated numerous product design sprints, and is an author and maintainer of thoughtbot's design sprint methodology repository. He's brought Lean and Agile methodology to many large companies and small startups, helping teams to focus, prioritize, and become happy and productive.
What if we asked as many questions as kids? Frederik highlights the imbalance between the number of questions we ask as kids versus adults. “For example, my oldest child probably asks about 180 questions a day. But as adults, we’re maybe asking 2-4 questions a day.” In his book A More Beautiful Question, Warren Berger shares a great example of this. The simple, yet powerful question that led to the creation of the Polaroid Instant Camera—why do we have to wait for the picture—came from the four-year-old daughter of the founder of Polaroid.
analysis approach architects aspects of design Atman backpack behaviour bicycle bike Brabham British Rail Chapter Christiaans city car client cognitive courtesy of WileyBlackwell Creative Design design ability design activity design concepts design problem design process Design Studies design task design team design thinking designer’s detailed domains drawing driver emerge engineering design evaluation example experience experimental expert designers exploration feature Figure function goal going Gordon Murray Grange’s High Speed Train identified industrial design innovative design interviews Ivan Ivan’s John and Kerry Juicy Salif Kenneth Grange lemon squeezer McLaren F1 Mike Burrows mockup moves Murray’s nature of design novice Philippe Starck pit stops principles problem frame product design protocol studies racing car design rack recognise role Schön seems session sewing machine situation sketches solution concept Starck strategy suggested team members teamwork there’s thing train understanding Victor Scheinman Vinod Goel Yeah
A design sprint can also be used to test a single feature or subcomponent of a product. This allows you to focus on a particular aspect of the design. For example, your team might need to know what improvements can be made to the onboarding process. Using the design sprint to discover the pros and cons of a new onboarding channel could give you granular insights into a high-return part of the product experience.
As the author for the program and lead mentor, Tenny is always present in the live edition to interact with students, challenge them, answer questions and coach the other mentors to make sure they do a great job in guiding our students through the Bootcamp experience. He is also in charge of the mentor reviewing process for the DIY program. Check his Bio below.
If I learned anything from Pixar in the last decade, it’s that life is complicated and often requires a balance of joy and sadness to make it through the tougher times (Inside Out, you get me). Whether you’re in the writing/design field, or someone who deals with customers on an ongoing basis, the key to creating memorable experiences starts with… Read More ￫
With a solid foundation in science and rationality, Design Thinking seeks to generate a holistic and empathetic understanding of the problems that people face. Design thinking tries to empathize with human beings. That involves ambiguous or inherently subjective concepts such as emotions, needs, motivations, and drivers of behaviors. The nature of generating ideas and solutions in Design Thinking means this approach is typically more sensitive to and interested in the context in which users operate and the problems and obstacles they might face when interacting with a product. The creative element of Design Thinking is found in the methods used to generate problem solutions and insights into the practices, actions, and thoughts of real users.
It takes four days instead of five. Why? Because we realized that there are countless little hacks you can do to make the process more efficient. We moved things around, changed up the order to make the flow more logical, and we also shortened a lot of the steps involved. Incredibly, we’ve also added stuff in, only to make the whole thing take less time. I know, this sounds confusing, but it’ll make sense if you keep reading…
The course is totally self-paced and you can move through the materials at a pace you’re comfortable with. It’s our aim to make you Design Sprint-facilitation-ready as quickly as possible and we don’t want to waste your time with pointless exercises and tasks that don’t contribute to you becoming a confident facilitator, so we estimate that you can complete the course and be ready to facilitate your first Sprint within 2 weekends, without stress.
Using the three basic premises of Design Thinking – Immersion, Ideation and Prototyping – and leveraging the creation of a multidisciplinary environment, Design Sprint is emerging as new way for accelerated innovation, where speed and innovation go hand in hand. Design Sprint is a smart track for fast experimentation: building on what Jeff Bezos claims -“If you double the number of experiments you do per year, you will double your ability to invent”-, Design Sprint mastering can bring a tremendous value to the company.
By Wednesday morning, you and your team will have a stack of solutions. That’s great, but it’s also a problem. You can’t prototype and test them all—you need one solid plan. In the morning, you’ll critique each solution, and decide which ones have the best chance of achieving your long-term goal. Then, in the afternoon, you’ll take the winning scenes from your sketches and weave them into a storyboard: a step-by-step plan for your prototype.
Tip: Limit the number of variables in your prototype, so you receive specific feedback on your big question. Designing a digital product? Start by designing landing pages that express each product offering, rather than the entire user flow. Testing two feature sets? Keep the branding the same and test different product features against one another.
“Sprints begin with a big challenge, an excellent team — and not much else. By Friday of your sprint week, you’ve created promising solutions, chosen the best, and built a realistic prototype. That alone would make for an impressively productive week. But Friday, you’ll take it one step further as you interview customers and learn by watching them react to your prototype. This test makes the entire sprint worthwhile: At the end of the day you’ll know how far you have to go, and you’ll know just what to do next.”
A complete Sprint process involves user testing in the last two days. Scheduling is hard and resources are limited. It’s very easy to just do half of a Sprint and fall in love with the ideas your team come up with. A successful Sprint always include research with end users or at least internal people who is not in the Sprint team to validate the ideas. I would even recommend lower the fidelity of your prototype to squeeze in time for research. Testing some sketches on paper is definitely better than having a polished interactive prototype that haven’t been validated by anyone. You always learn something from user research, so you should always, always include research in your Sprint process.
In these fun, fast-paced, hands-on events, Sprint authors Jake and JZ rapidly lead you through all five stages of the Design Sprint process. Drawing on their 10 years of experience at Google and running more than 150 sprints with companies like Slack, Nest, 23andMe, and Blue Bottle Coffee, Jake and JZ teach how and why the process works. You’ll experience a Design Sprint and build muscle memory for facilitating your own (whether it’s your first or 101st) and for incorporating these techniques into normal meetings.
We added a new exercise here that makes the storyboarding process at least 27 times easier (give or take). It’s called User Test Flow and it’s a form of Note & Vote exercise. Everyone designs the barebones of their own storyboard and then we vote on the one or two that we end up prototyping. Even though it’s an extra step, it speeds up the storyboarding process by a million miles and eliminates the “designing by committee” aspect of it. Here’s a video that explains it in detail (and there’s a Medium post on it, too).
Once everyone is BFFs, we introduce design sprints as a practice. We talk about how they fit into the bigger picture of business innovation, design thinking, and product development. We help attendees understand the work your team will need to do before the sprint, to ensure we’re connecting business value to the sprint, as well as choosing the right/best challenge.
Design for a light-touch, full-product experience. Ask yourself: What’s the smallest set of features you can design that will still solve users’ problems? Start with the simplest version of your product, get user feedback, and then add features. As your sprint loops continue, you can move from simple prototypes to robust product directions. With Swell, we focused on creating a hero page for each key interaction (landing page, sign up, and invest). This meant we were testing the functionality of the full product experience, just in a light-touch way.
Design Thinking revolves around a deep interest in developing an understanding of the people for whom we’re designing the products or services. It helps us observe and develop empathy with the target user. Design Thinking helps us in the process of questioning: questioning the problem, questioning the assumptions, and questioning the implications. Design Thinking is extremely useful in tackling problems that are ill-defined or unknown, by re-framing the problem in human-centric ways, creating many ideas in brainstorming sessions, and adopting a hands-on approach in prototyping and testing. Design Thinking also involves ongoing experimentation: sketching, prototyping, testing, and trying out concepts and ideas.
So far, since the launch of the course in May 2016, 115 professionals from 12 countries and diverse industries ranging from marketing to manufacturing and consulting to software development, have opted for this course. Notably, the course has seen a whopping 89% completion rate, contrary to popular observations that online courses see dwindling participation after the first few classes.
For our first dispatch of 2019, we’ve assembled enough Google Design goodies to put a spring in your step. Our roundup includes a big story on Waymo—exploring how the company’s designers built a brand new UX playbook to foster user trust; an artful interview with technologist John Maeda on agile leadership; and deep insights from UX Director Margaret Lee, who penned an essay on how her immigrant upbringing shaped her take on leadership. We also compiled a fresh selection of “5 Things to Love Right Now”—curated by San Francisco-based designer Shannon May. Dig in for a new bloom of insights and inspiration.Subscribe to the Google Design Newsletter
Instead of an endless debate or a watered-down group decision nobody's happy with, you'll use the five-step "Sticky Decision" method to identify the best solutions before turning the final decision over to your Decider. Then, in the afternoon, you’ll take the winning scenes from your sketches and combine them into a storyboard: a step-by-step plan for your prototype.