{"id":4249894,"date":"2020-07-07T13:13:00","date_gmt":"2020-07-07T11:13:00","guid":{"rendered":"https:\/\/www.deptagency.com\/insight\/bringing-digital-products-to-life-with-design-sprints\/"},"modified":"2020-07-07T13:13:00","modified_gmt":"2020-07-07T11:13:00","slug":"bringing-digital-products-to-life-with-design-sprints","status":"publish","type":"article","link":"https:\/\/www.deptagency.com\/en-nl\/insight\/bringing-digital-products-to-life-with-design-sprints\/","title":{"rendered":"Bringing digital products to life with design sprints"},"content":{"rendered":"
\n\t\n\t<\/svg>\n\t\t\t\n\t\t\tBack to all articles\t\t<\/span>\n\t\n<\/a>\n\t\tBringing digital products to life with design sprints\t<\/h1>\n\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t\t\n\t\t<\/picture>\n\t\n\t<\/div>
\n\t\t\t\n\t\n\t
\n\t\tBrian Robinson\t\t
\n\t\tManaging Director UK\n\t\t\t<\/div>\n<\/div>\n\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\tDate\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t7 July 2020\t\t\t\t<\/div>\n\t\t\t<\/div>\n\t\t\t\t<\/div>\n<\/div>\n\n
\n\t
\n\t\t\n\t\t\t\t\t
\n\t\t\t\t\n\n\t\tLaunching new digital products or refreshing existing ones is a huge undertaking for companies of all sizes. And in many ways, it should be. Bringing a new or updated product to market should not be rushed or taken lightly. But in many cases, the speed of innovation is drastically reduced because of an endless debate cycle between product and engineering, or competing internal priorities that make it difficult to move any ideas forward. This is an ongoing challenge for companies of all sizes, but especially for large brands.\t<\/h2>\n\n\n\t\tThere is a counter-intuitive phenomenon that happens to large companies who have existing successful products. Instead of their experience leading them to knowing exactly what to build next, they have so many ideas coming at them from all directions that it becomes harder to know what to build. Or, for some companies it can be difficult to unlearn old assumptions, or relearn new ones as their customers\u2019 wants and needs evolve, so they end up building products that ultimately don\u2019t meet their customers\u2019 needs.

To help facilitate a quicker and more informed path to bringing new products to life,\u00a0Jake Knapp and Google Ventures<\/a>\u00a0introduced a methodology called design sprints in 2010. Basically, this means that companies can better validate a specific product vision and get valuable customer feedback before committing engineering resources to fully build it out. This is because teams can build a realistic prototype without any engineering code, compressing a process that typically takes months into just a few days. This is important because it can be easy for product and engineering teams to get really excited about a product idea and get too far down the path before they even understand if their assumptions about the product were valid and supported by actual customers.

Since then, companies like DEPT\u00ae have used design sprints to good effect, but we\u2019ve also built out the methodology further and learned how to make a sprint flexible enough to change for a project\u2019s specific needs and goals. We\u2019ve gone far beyond the original, five day sprint concept and now regularly conduct sprints of longer duration for clients. We\u2019ve also found design sprints to be highly beneficial when kicking off new client engagements.\t<\/p>\n\t\t\t<\/div>\n\t\t\t<\/div>\n\n\t\n\t