Innowacyjność pomaga budować pozycję rynkową firmy. Słowo to nie oznacza jedynie oferowania nowych produktów i usług, ale dotyczy również organizacji działania. Niestety, realizacja zasady ciągłego doskonalenia się najczęściej napotyka opory. Ludzie nie lubią zmian sposobu myślenia i niechętnie akceptują konieczność innego podejścia. Tymczasem dla wielu podmiotów, szczególnie tych z nowoczesnych branż, umiejętność szybkiej zmiany jest kluczem do sukcesu.
Niniejsza książka prezentuje koncepcję sprintów projektowania produktu. Jest to nowe podejście do projektowania produktów, szczególnie zalecane firmom stawiającym na innowacyjność. Dzięki tej metodzie nowe pomysły dużo szybciej i skuteczniej przeradzają się w prototyp, który z kolei staje się gotowym rozwiązaniem. Powstaje produkt o wysokiej jakości. Co istotne, realizacja zadań w sprintach przebiega szybciej i jest bardziej wydajna. W zależności od specyfiki przedsiębiorstwa sprint projektowania może trwać od kilku godzin do kilku dni, w wyjątkowych przypadkach � kilka tygodni.
W książce omówiono: koncepcję sprintu projektowania, jego zalety i wady sposoby planowania sprintu etapy sprintu projektowania i ich przebieg sposoby wykorzystania wyników przeprowadzonego sprintu Sprintem do sukcesu!
Richard Banfield � prezes zarządu i współzałożyciel firmy Fresh Tilled Soil, agencji zajmującej się badaniem doświadczeń użytkownika.
C. Todd Lombardo � architekt do spraw innowacji w Small Business InnoLoft w firmie Constant Contact.
Trace Wax � dyrektor w firmie thoughtbot, w której zorganizował i poprowadził wiele sprintów projektowania produktu.
There's a lot of evidence to suggest the book wasn't even proofed before it was published. There are spelling mistakes all over it and even an entire paragraph repeated on pages 158 and 162.
It's a short book padded out with irrelevant or uselessly vague anecdotes and photos that don't relate to the topic under discussion. For example page 168 discusses how to use a 2x2 matrix. The text says 'draw a Cartesian coordinate "+" on a board. A what? How big? Frustratingly there's a large image on the opposite page... But it's not a 2x2 matrix. I don't know what it is, it seems to be random scribbling. It has nothing to do with the text and anyone who has never seen a 2x2 matrix or knows what a Cartesian coordinate + is, will not be enlightened. Opportunity missed.
It could have been much better - 'show don't tell' is one of the key lessons we get drummed into us at school and if the authors had followed that advice this would have been a fantastic book. As it is it's frustrating. The ideas are good. The suggested agendas are useful. The execution is poor.
A particular issue is that the book is clearly focused on digital design. But that clarity is only apparent when you start reading it. This makes it even more frustrating for anyone designing communications, services or other things - there's a lot of translation needed to make it useful. I want to recommend this book as it's potentially beneficial. But it's a good example of what's missing in the literature on design sprints than a long-lasting contribution to it.
Useful, but slightly boring. This is largely a collection of exercises, most of which should be familiar to designers with some experience. The value is in the 'framework' of the design sprint which ties it all together. I can see myself selling this to clients as a design consultant. And I can also see myself suggesting it as a kick-off for a new larger project. But I expect to do some serious tailoring in all cases.
Really useful book for anyone interested in the design sprint as a technique. PMs, designers, CEOs could all benefit from using design sprints and reading this book when planning new products, features... It is written in the easy to digest language with practical toolkit in the end.
Pretty good write-up on what I think of (perhaps incorrectly) as the Constant Contact version of Design Sprints (as opposed to Google).
If you want to formalize methodology around up front design, with customer feedback in the loop, this is a reasonable run at it.
You can tell it predates COVID due to the aggressively colocated strategy, most teams looking into this will need to virtualize it, but that's what we've been doing with everything else over the last few years, so this won't be a stretch.
If you know nothing about a design sprint, then this books takes you from 0 to 10. But that's what it is and that's what it does. It doesn't teach you any more or less, and that can be boring or interesting depending on your intention for reading it. I knew nothing about a design sprint, so I was happy to learn about the process. But as a designer, I didn't have a place to apply it. But if i did want to, I guess I could reference it.
This is a great book for anybody involved into a digital project design process. It covers the whole process from the discovery of opportunities/issues to quick prototyping and validation of the project premises. This framework is lean and agile, allowing to check the validity of the project at a minimum cost and come up with most effective solutions in a short period of time.
I first read Jake Knapp's book which takes more of a storytelling approach. This one offers more of the practical guidance I was looking for, but it feels rushed and incohesive.
To be honest, one might be better off going through the GV website and looking up individual exercises on Medium.
This book teaches about how to start in a very good way a product discovery cycle. It explain very well a lot of artefacts and very valuable tips. However it doesn't has an applied example from the beginning to the finish.
If you want to include your cross-functional team in innovative product development this is an excellent read. Very good step-by-step guide with practical tools on how to conduct a design sprint.
A lot of practical exercises that you should know if you plan to run Product Design Sprints. It makes you more prepared to adapt to different sprint scenarios.
Tbh, I was expecting a little bit more theoretical approach. The book is 90% practical on how to perform a design sprint. However, you will find from time to time some useful knowledge i.e. what are the flaws of the focus groups, dotmocracy is broken, why you should not always listen to the HiPPOs in the organization, and so on.
Meh. Molto polistirolo a riempire il vuoto, scrittura sciatta, capoversi di capoversi di banalità, ripetizione. Sembra scritto in fretta da persone senza gran esperienza. Arrivo alla fine perché ha un'impostazione pratica, ha le checklist, dice niente di nuovo ma mette in fila punti da ricordare quando provi a mettere in piedi qualcosa nello spirito di un design sprint («a cathartic timeboxed design cycle driven by assumptions and bookended with customer input and feedback») e dà qualche buon consiglio («Resist answering questions about the product or business until after the interview or turn these back into questions: e.g., “Does this feature allow uploading photos directly from my phone?� can be answered with “Do you think it should allow that?”�).
Very practical approach to validating an idea in a very short period of time. It's a structured approach, but the presentation is not dogmatic as so much of the books in this genre can be. Perhaps I was biased after attending a panel of the smart and down-to-earth authors that was refreshingly light on theory.
A useful, practical approach to doing one or many design sprints.
As someone who uses this technique, it was good to see a combination of validation of my work, new ideas, and clues as to where I'm not getting it right.