arrow-flex-shortarrow-flexarrow arrowsbinocularsbsichartcogsflex-icongeargithubglobeheadphoneslightnings linkedinlock newsletter-chartDvelp_Newsletterplantscalestarget triangle-icon twitter

Why Design Sprints Work

April 25, 2017

Emerging from the experimental, agile playground of Silicon Valley, the Design Sprint was codified by Google Ventures and has since seen increasing adoption in startups and corporates around the world.

Our journey with the Design Sprint started organically. As bespoke software developers connected with London’s business community, we are regularly approached by would-be founders launching their startup or companies looking to innovate via a new product. With increasing frequency we found ourselves constructively challenging the concepts. Are all of those features really necessary? What is their Minimum Viable Product (MVP)? Would an off the shelf solution offer better value? Do they even need a product at all?

As firm believers that the best line of code is no code at all, we challenge our clients to develop a clear understanding of what they really need before diving headfirst into the long-term commitment of building an in-house software product. It is hard to get this level of depth from a tender document or coffee chat, so we adopted the Design Sprint.

Over 5 intense days filled with messy brainstorming, sharp prioritisation, prototyping and end-user engagement we tease out the answers to those questions, building a shared understanding of the product. Sometimes this prototype forms the basis of an awesome product we build together and sometimes we learn that a bespoke solution is not right, but we save the client a world of hurt paying for something they don’t need.

We’ve found we can build better products more efficiently off the back of a Design Sprint and clients love the insight they gain into their own business. Stay tuned for our coming services page for more detail on how we run Design Sprints.


By using this website you agree to our cookie policy