Fee Download Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days, by Jake Knapp, John Zeratsky, Braden Kowitz
By downloading this soft documents e-book Sprint: How To Solve Big Problems And Test New Ideas In Just Five Days, By Jake Knapp, John Zeratsky, Braden Kowitz in the on the internet web link download, you remain in the initial step right to do. This site truly supplies you ease of ways to obtain the very best publication, from best seller to the brand-new released publication. You could discover a lot more books in this site by visiting every web link that we supply. One of the collections, Sprint: How To Solve Big Problems And Test New Ideas In Just Five Days, By Jake Knapp, John Zeratsky, Braden Kowitz is among the very best collections to market. So, the first you get it, the first you will obtain all good for this book Sprint: How To Solve Big Problems And Test New Ideas In Just Five Days, By Jake Knapp, John Zeratsky, Braden Kowitz
Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days, by Jake Knapp, John Zeratsky, Braden Kowitz
Fee Download Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days, by Jake Knapp, John Zeratsky, Braden Kowitz
Sprint: How To Solve Big Problems And Test New Ideas In Just Five Days, By Jake Knapp, John Zeratsky, Braden Kowitz. Is this your extra time? What will you do then? Having spare or free time is really incredible. You can do everything without pressure. Well, we expect you to exempt you few time to review this e-book Sprint: How To Solve Big Problems And Test New Ideas In Just Five Days, By Jake Knapp, John Zeratsky, Braden Kowitz This is a god book to accompany you in this downtime. You will certainly not be so hard to understand something from this publication Sprint: How To Solve Big Problems And Test New Ideas In Just Five Days, By Jake Knapp, John Zeratsky, Braden Kowitz More, it will certainly help you to get far better info as well as experience. Also you are having the great jobs, reading this publication Sprint: How To Solve Big Problems And Test New Ideas In Just Five Days, By Jake Knapp, John Zeratsky, Braden Kowitz will certainly not add your thoughts.
This letter might not influence you to be smarter, yet the book Sprint: How To Solve Big Problems And Test New Ideas In Just Five Days, By Jake Knapp, John Zeratsky, Braden Kowitz that we offer will certainly stimulate you to be smarter. Yeah, at the very least you'll recognize more than others who don't. This is what called as the top quality life improvisation. Why needs to this Sprint: How To Solve Big Problems And Test New Ideas In Just Five Days, By Jake Knapp, John Zeratsky, Braden Kowitz It's considering that this is your favourite style to check out. If you such as this Sprint: How To Solve Big Problems And Test New Ideas In Just Five Days, By Jake Knapp, John Zeratsky, Braden Kowitz theme about, why do not you check out the book Sprint: How To Solve Big Problems And Test New Ideas In Just Five Days, By Jake Knapp, John Zeratsky, Braden Kowitz to improve your conversation?
The here and now book Sprint: How To Solve Big Problems And Test New Ideas In Just Five Days, By Jake Knapp, John Zeratsky, Braden Kowitz we provide here is not sort of normal book. You understand, reviewing currently does not indicate to manage the printed book Sprint: How To Solve Big Problems And Test New Ideas In Just Five Days, By Jake Knapp, John Zeratsky, Braden Kowitz in your hand. You can get the soft data of Sprint: How To Solve Big Problems And Test New Ideas In Just Five Days, By Jake Knapp, John Zeratsky, Braden Kowitz in your gadget. Well, we indicate that the book that we proffer is the soft file of the book Sprint: How To Solve Big Problems And Test New Ideas In Just Five Days, By Jake Knapp, John Zeratsky, Braden Kowitz The content and all points are exact same. The difference is just the forms of the book Sprint: How To Solve Big Problems And Test New Ideas In Just Five Days, By Jake Knapp, John Zeratsky, Braden Kowitz, whereas, this problem will specifically pay.
We discuss you also the means to get this book Sprint: How To Solve Big Problems And Test New Ideas In Just Five Days, By Jake Knapp, John Zeratsky, Braden Kowitz without going to the book store. You can remain to check out the link that we give and prepared to download Sprint: How To Solve Big Problems And Test New Ideas In Just Five Days, By Jake Knapp, John Zeratsky, Braden Kowitz When many people are hectic to seek fro in guide store, you are really easy to download the Sprint: How To Solve Big Problems And Test New Ideas In Just Five Days, By Jake Knapp, John Zeratsky, Braden Kowitz right here. So, exactly what else you will opt for? Take the motivation right here! It is not only supplying the best book Sprint: How To Solve Big Problems And Test New Ideas In Just Five Days, By Jake Knapp, John Zeratsky, Braden Kowitz however additionally the appropriate book collections. Right here we consistently offer you the best as well as easiest means.
From three design partners at Google Ventures, a unique five-day process for going from problem to prototype.
The companies that Google Ventures invest in face big questions every day: Where’s the most important place to focus your effort, and how do you start? What will your ideas look like in real life? How many meetings and discussions does it take before you can be sure you have the right solution to a problem? Business owners and investors want their companies and the people who lead them to be equipped to answer these questions—and quickly. And now there’s a sure-fire way to solve their problems and test solutions: the sprint.
While working at Google, designer Jake Knapp created a unique problem-solving method that he coined a “design sprint”—a five-day process to help companies answer crucial questions. His “sprints” were used in the development of everything from Gmail to Google X to Chrome. When he moved to Google Ventures, he joined Braden Kowitz and John Zeratsky, both designers and partners there who have worked on numerous products, including the YouTube redesign. Together Knapp, Zeratsky, and Kowitz have run over 100 sprints with their portfolio companies, inside Google and in others companies or environments who have sought their help. They’ve seen firsthand how sprints can overcome challenges in all kinds of companies: healthcare, fitness, finance, retailers, and more.
A practical guide to answering business questions, Sprint is a book for groups of any size, from small startups to Fortune 100s, from teachers and PTAs to nonprofits and public institutions. It’s for anyone with a big opportunity, problem, or idea who needs to get answers today.
- Sales Rank: #949361 in Books
- Published on: 2016-03-08
- Released on: 2016-03-08
- Formats: Audiobook, CD, Unabridged
- Original language: English
- Number of items: 5
- Dimensions: 5.87" h x .70" w x 5.13" l,
- Running time: 22228 seconds
- Binding: Audio CD
Review
“Every business leader I know worries about the same thing: Are we moving fast enough? The genius of Jake Knapp’s Sprint is its step-by-step breakdown of what it takes to solve big problems and do work that matters with speed and urgency. A sprint is a cure for what ails companies in an ever faster world.”
—Beth Comstock, vice chair of GE
"The key to success, often, is building the right habits. But which habits work best? Sprint offers powerful methods for hatching ideas, solving problems, testing solutions—and finding those small, correct habits that make all the right behaviors fall in place."
– Charles Duhigg, author of The Power of Habit
"To quote one of my colleagues, “don’t get ready, get started”. Through hard won experience Jake Knapp and the team at Google Ventures have refined an efficient, hands-on approach to solving your product, service and experience design challenges. Try the book and try a Sprint."
– Tim Brown, CEO of IDEO and author of Change By Design
"Read this book and do what it says if you want to build better products faster."
– Ev Williams, founder of Medium, Blogger, and Twitter
"Sprint teaches you a novel process for solving really thorny problems in just 5 days. It's full of helpful, entertaining stories that will make it easier for you to succeed. What more, exactly, would you demand from a book? I wish all business books were this useful."
– Dan Heath, co-author of Made to Stick, Switch, and Decisive
About the Author
Jake Knapp created the Google Ventures sprint process and has run more than a hundred sprints with startups such as 23andme, Slack, Nest, and Foundation Medicine. Previously, Jake worked at Google, leading sprints for everything from Gmail to Google X. He is currently among the world’s tallest designers.
John Zeratsky has designed mobile apps, medical reports, and a daily newspaper (among other things). Before joining Google Ventures, he was a design lead at YouTube and an early employee of FeedBurner, which Google acquired in 2007. John writes about design and productivity for Wall Street Journal, Fast Company, and Wired. He studied journalism at the University of Wisconsin.
Braden Kowitz founded the Google Ventures design team in 2009 and pioneered the role of “design partner” at a venture capital firm. He has advised close to two hundred startups on product design, hiring, and team culture. Before joining Google Ventures, Braden led design for several Google products, including Gmail, Google Apps for Business, Google Spreadsheets, and Google Trends.
Excerpt. � Reprinted by permission. All rights reserved.
Sprint 1 Challenge
In 2002, a clarinet player named James Freeman quit his job as a professional musician and founded�.�.�. a coffee cart.
James was obsessed with freshly roasted coffee. In those days in the San Francisco area, it was nearly impossible to find coffee beans with a roast date printed on the bag. So James decided to do it himself. He carefully roasted beans in a potting shed at home, then drove to farmers’ markets in Berkeley and Oakland, California, where he brewed and sold coffee by the cup. His manner was polite and accommodating, and the coffee was delicious.
Soon James and his cart, called Blue Bottle Coffee, developed a following. In 2005, he established a permanent Blue Bottle location in a friend’s San Francisco garage. Over the next few years, as the business grew, he slowly opened more caf�s. By 2012, Blue Bottle had locations in San Francisco, Oakland, Manhattan, and Brooklyn. It was a business that many would have considered perfect. The coffee was ranked among the best nationwide. The baristas were friendly and knowledgeable. Even the interior design of the caf�s was perfect: wooden shelves, tasteful ceramic tiles, and an understated logo in the perfect shade of sky blue.
But James didn’t consider the business perfect, or complete. He was still just as passionate about coffee and hospitality, and he wanted to bring the Blue Bottle experience to even more coffee lovers. He wanted to open more caf�s. He wanted to deliver freshly roasted coffee to people’s homes, even if they didn’t live anywhere near a Blue Bottle location. If that coffee cart had been Sputnik, the next phase would be more like a moon shot.
So in October 2012, Blue Bottle Coffee raised $20 million from a group of Silicon Valley investors, including GV. James had many plans for that money, but one of the most obvious was building a better online store for selling fresh coffee beans. But Blue Bottle wasn’t a tech company and James was no expert at online retail. How could he translate the magic of his caf�s to smartphones and laptops?
Several weeks later, on a bright December afternoon, Braden Kowitz and John Zeratsky met up with James. They sat around a counter, drank coffee, and discussed the challenge. The online store was important to the company. It would take time and money to get it right, and it was difficult to know where to start. In other words, it sounded like a perfect candidate for a sprint. James agreed.
They talked about who should be in the sprint. An obvious choice was the programmer who would be responsible for building Blue Bottle’s online store. But James also included Blue Bottle’s chief operating officer, chief finance officer, and communications manager. He included the customer service lead who handled questions and complaints. He even included the company’s executive chairman: Bryan Meehan, a retail expert who started a chain of organic grocery stores in the UK. And, of course, James himself would be in the room.
The online store was essentially a software project—something our team at GV was very familiar with. But this group looked almost nothing like a traditional software team. These were busy people, who would be missing a full week of important work. Would the sprint be worth their time?
•��•��•
On Monday morning of our sprint week, the Blue Bottle team gathered in a conference room at GV’s office in San Francisco. We made a diagram on the whiteboard showing how coffee buyers might move through the online store. The Blue Bottle team targeted a new customer purchasing coffee beans. James wanted to focus the sprint on this scenario because it was so difficult. If they could establish credibility and create a great experience for someone who had never heard of Blue Bottle, let alone visited their caf�s or tasted their coffee, then every other situation should be easy by comparison.
We ran into a big question: How should we organize the coffee? The shopper in this scenario would be choosing between a dozen or so varieties of bean, each in a nearly identical bag. And—unlike in Blue Bottle’s caf�s—there would be no barista there to help choose.
At first, the answer seemed obvious. From boutique coffee roasters to mainstream giants like Starbucks, retailers tend to organize coffee by the geographic region where it was grown. Africa, Latin America, the Pacific. Honduran coffee vs. Ethiopian coffee. It would be logical for Blue Bottle to categorize their beans the same way.
“I have to admit something,” Braden announced. Everyone turned. “I’m into coffee, okay? I have a scale at home and everything.” Electronic scales are the hallmark of a true coffee freak. Owning a scale meant Braden weighed the water and coffee beans so that he could experiment and adjust ratios as he brewed. We’re talking science here. Coffee scales are accurate to a fraction of a gram.
Braden smiled and held his hands palm up. “I don’t know what the regions mean.” There was silence. We avoided looking at James. After all, Braden’s brave admission might be seen as heresy.
“That’s okay,” said James. The floodgate opened. John and Jake didn’t know the difference between coffee regions, and neither did Daniel Burka. We drank coffee together constantly, but none of us had ever admitted to our lack of sophistication.
Then Serah Giarusso, Blue Bottle’s customer service lead, snapped her fingers. “What do we do in the caf�s?” she asked. After all, she went on, The Braden Situation must happen to baristas all the time: a customer comes in for coffee beans, but isn’t sure which kind to buy.
James is a slow and thoughtful speaker. He paused for a moment before he answered. “The brew method is very important,” he said. “So we train the baristas to ask the customer a simple question: ‘How do you make coffee at home?’ ” James explained that, depending on whether the customer used a Chemex, or a French press, or a Mr. Coffee, or whatever, the baristas could recommend a bean to match.
“ ‘How do you make coffee at home�.�.�.�?’ ” Braden repeated. Everyone jotted notes. James had started the sprint by explaining his vision: that the online store should match the hospitality of the caf�s. It felt as if we were onto something.
The team spent the following day sketching ideas for the store. On Wednesday morning we had fifteen different solutions. That’s too many to test with customers, so the team voted on their favorites as a way to narrow it down. Then James, the decision-maker, made the final pick of three sketches to test.
The first sketch showed a literal approach to making the website match the caf�s: It looked like the inside of a Blue Bottle caf�, complete with wooden shelves. The second sketch included lots of text, to mirror the conversations baristas often have with customers. Finally, James chose a third sketch that organized coffee by brew method, bringing the “How do you make coffee at home?” question right onto the computer screen.
James had chosen three competing ideas. So which one should we prototype and test? The idea of a website that looked like the caf� was the most appealing. Blue Bottle’s aesthetic is celebrated, and a matching website would look different from anything else in the market. We had to try that idea, and it wasn’t compatible with the other solutions. But those other solutions were also really intriguing. We couldn’t quite decide.
So we decided to prototype all three. After all, we didn’t need a functioning website. To appear real in our test, each fake online store only required a few key screens. Working together with the Blue Bottle team, we used Keynote presentation software to make a series of slides that looked like three real websites. With a little ingenuity, and without any computer programming at all, we stitched those screens into a prototype that our test customers could use.
On Friday, the team watched the customer interviews. One at a time, coffee drinkers shopped on several websites, with Blue Bottle’s three prototypes slipped in among the competitors. (To avoid tipping off the customers, we gave each prototype a fake name.)
Patterns emerged. The store with wooden shelves, which everyone had such high hopes for? We thought the prototype was beautiful, but customers said it was “cheesy” and “not trustworthy.” But the other two prototypes fared far better. The “How do you make coffee at home?” design worked seamlessly. And the “lots of text” design shocked us: People actually read all those words, and the extra information brought Blue Bottle’s voice and expertise to life. As one customer said, “These guys know coffee.”
James and the Blue Bottle team built confidence with their sprint. They were much closer to defining how their online store would work. What’s more, they’d done it in a way that felt true to their principles of hospitality. They believed the online store could be an authentic Blue Bottle experience.
A few months later, Blue Bottle launched their new website, and their online sales growth doubled. The next year, they acquired a coffee subscription company. With a bigger team and new technology, they expanded the web store and began experimenting with new offerings. They knew it would take years to get the online store right—but in the sprint, they started on their path.
The bigger the challenge, the better the sprint
If you’re starting a project that will take months or years—like Blue Bottle and their new online store—a sprint makes an excellent kickoff. But sprints aren’t only for long-term projects. Here are three challenging situations where sprints can help:
High Stakes
Like Blue Bottle Coffee, you’re facing a big problem and the solution will require a lot of time and money. It’s as if you’re the captain of a ship. A sprint is your chance to check the navigation charts and steer in the right direction before going full steam ahead.
Not Enough Time
You’re up against a deadline, like Savioke rushing to get their robot ready for the hotel pilot. You need good solutions, fast. As the name suggests, a sprint is built for speed.
Just Plain Stuck
Some important projects are hard to start. Others lose momentum along the way. In these situations, a sprint can be a booster rocket: a fresh approach to problem solving that helps you escape gravity’s clutches.
When we talk to startups about sprints, we encourage them to go after their most important problem. Running a sprint requires a lot of energy and focus. Don’t go for the small win, or the nice-to-have project, because people won’t bring their best efforts. They probably won’t even clear their schedules in the first place.
So how big is too big? Sure, sprints work great for websites and other software challenges. But what about really large, complicated problems?
Not long ago, Jake visited his friend David Lowe, a vice president of a company called Graco that manufactures pumps and sprayers. Graco is not a small startup. They’re a multinational company who have been in business for more than ninety years.
The company was developing a new kind of industrial pump—a machine used in assembly lines. David, the VP, wondered if a sprint might help lower the risk of the project. After all, it would take eighteen months and millions of dollars to design and manufacture the new pump. How could he be sure they were on the right track?
Jake doesn’t know anything about industrial assembly lines, but out of curiosity, he joined a meeting with the engineering team. “I’ll be honest,” Jake said. “An industrial pump sounds too complicated to prototype and test in a week.”
But the team wouldn’t give up so easily. If limited to just five days, they could prototype a brochure for the pump’s new features and try it in sales visits. That kind of test could answer questions about marketability.
But what about the pump itself? The engineers had ideas for that, too. To test ease-of-use, they could 3D print new nozzles and attach them to existing pumps. To test installation, they could bring cables and hoses to nearby manufacturing plants and get reactions from assembly line workers. These tests wouldn’t be perfect. But they would answer big questions, before the pump even existed.
Jake was wrong. The industrial pump wasn’t too complicated for a sprint. The team of engineers accepted the five-day constraint and used their domain expertise to think creatively. They sliced the challenge into important questions, and shortcuts started to appear.
The lesson? No problem is too large for a sprint. Yes, this statement sounds absurd, but there are two big reasons why it’s true. First, the sprint forces your team to focus on the most pressing questions. Second, the sprint allows you to learn from just the surface of a finished product. Blue Bottle could use a slide show to prototype the surface of a website—before they built the software and inventory processes to make it really work. Graco could use a brochure to prototype the surface of a sales conversation—before they engineered and built the product they were selling.
Solve the surface first
The surface is important. It’s where your product or service meets customers. Human beings are complex and fickle, so it’s impossible to predict how they’ll react to a brand-new solution. When our new ideas fail, it’s usually because we were overconfident about how well customers would understand and how much they would care.
Get that surface right, and you can work backward to figure out the underlying systems or technology. Focusing on the surface allows you to move fast and answer big questions before you commit to execution, which is why any challenge, no matter how large, can benefit from a sprint.
Most helpful customer reviews
60 of 65 people found the following review helpful.
A masterpiece. This is the new ’START HERE’ book I recommend to all my design students as well as CEOs I work with.
By Xander Pollock
Jake, John, and Braden have synthesized the most important design-thinking concepts of today into a book that is worth its weight in gold. Seriously — I’ve translated the ideas and checklists in this book to tens of thousands of dollars already as a design consultant.
It’s weird... even after 4 years of studying Art & Design in college and 4 years of working at a big tech company, this book was STILL a revelation to me. It helped me understand and practice design in a whole new way. I was lucky to be mentored by top-tier designers. Now you can be mentored by some of the best designers in the Silicon Valley. Listen in on how they work and think...
90% of what you need to know about designing great products is in these 257 glorious pages. The other 10% is just blood, sweat and tears.
4 of 4 people found the following review helpful.
A Better Way of Working
By Ben McMann
"It's what work should be about – working together to build something that matters to people. This is the best use of your time. This is a sprint." This was a great sentence to finish the book, and it's a great sentence to begin working in a better way.
In the preface, the author states he had his first child. When he returned to the office, he wanted his time on the job to be as meaningful as his time with his family. He took a hard look at his habits and saw that, "I wasn’t spending my effort on the most important work". He discussed how improving team processes became an obsession for him. Through his experience of working with teams to create new products at Google, and experimenting on improving the way teams work, he found that focusing on individual work, having time to prototype, and an inescapable deadline produced far better results.
Running the 5 day sprint described in the book enables a team to easily find out if they are on the right track before they commit to the risky business of building and launching their products. The sprint process however is just as applicable to teams launching internal products/solutions/services. This way of work is applicable to any company, not just startups.
The author shares how other Google Ventures team members added to the sprint process to make it better through the years. Braden Kowitz added story-centered design – which focuses on the whole customer experience instead of individual components or technologies. John Zeratsky helped to ensure that each sprint starts at the end, so the business's would be able to identify and answer their most important questions. Michael Margolis encouraged them to finish each sprint with a real world test. By putting your prototype in front of real customers/prospects, you didn't have to guess whether your solutions were good, at the end of the sprint you got answers.
Over the last 10 years, I have facilitated interactive workshops to help teams get a shared understanding of the business problem they are trying to solve, which is a precursor to a shared commitment to solve the problem. Having a solid understanding of the research behind collaborative approaches to work, and understanding the approach to use based on the problem domain you are in is critical to a successful outcome. Because of my background and real-world experience, I recognize how effective the sprint design is, and feel confident in using the process with any client I work with. The psychology behind the methods is real, the creativity of the design will engage all who participate, and you will build better products.
If you are passionate about helping teams work more effectively, if you care about making work a more engaging experience, if you have a burning desire to improve customers' lives, read this book and then USE this book to run sprints.
18 of 20 people found the following review helpful.
I look forward to testing this approach... great book!
By Mary
A very useful and enjoyable handbook that I'll be using to run student teams at the university. However, I was a little surprised to see Jake's comment in the preface about his 2009 team at Google: "... I decided to call it a design 'sprint'." Wait, what? Hasn't a five-day 'sprint', focused on delivering a working prototype, been *the* central feature of the scrum methodology of software design since 1993? That's when Jeff Sutherland and others worked together to design a structured methodology for teams that would be faster and better than 'waterfall project management'. SEE: many books, including a recent book by Sutherland's Scrum: The Art of Doing Twice the Work in Half the Time and Lacey's The Scrum Field Guide: Practical Advice for Your First Year (Agile Software Development Series). Sutherland's work was based, in turn, on the 1986 Harvard Business Review seminal article by Takeuchi and Nonaka, "The New New Product Development Game". Many industries outside of software development--- NPR, airlines, even classrooms-- have used sprints for decades; we used a 5-day sprint for museum exhibit design in 1998. IDEO has been doing something very similar for decades too.
That said, after stumbling over that initial terminology of 'same word-different meaning' and the somewhat-less-than-generous "I invented this!!" claim without a tip of the hat to all the great people who led the way, I did really enjoy the book. Jake has immense experience and has developed a beautifully structured design-build process that we can put immediately to use that is simpler to implement than a fully-featured scrum team. Thanks, Jake!
Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days, by Jake Knapp, John Zeratsky, Braden Kowitz PDF
Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days, by Jake Knapp, John Zeratsky, Braden Kowitz EPub
Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days, by Jake Knapp, John Zeratsky, Braden Kowitz Doc
Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days, by Jake Knapp, John Zeratsky, Braden Kowitz iBooks
Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days, by Jake Knapp, John Zeratsky, Braden Kowitz rtf
Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days, by Jake Knapp, John Zeratsky, Braden Kowitz Mobipocket
Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days, by Jake Knapp, John Zeratsky, Braden Kowitz Kindle
Tidak ada komentar:
Posting Komentar