It is not uncommon for a business to be requested by customers provide them with quick, high-quality answers for their various challenges. Making the solution accessible to customers and the general public in an optimal and efficient manner is in most cases a long process. This is also usually a cumbersome process since it requires coordinating many teams, logistic challenges, availability, good communication etc.
One method used in order to speed up matters as well as enhance their efficiency in order to move matters forward is the Design Sprint (DS). The DS is a work method developed by Google and is meant to answer important business questions through design, creating prototypes and reviewing ideas together with the customers. This method involves several teams working for 2-5 intense days and quickly creating exact solutions for core problems. During the sprint teams comprised of product, UX, technology, sales and management personnel are closed in one room in which they deconstruct and reconstruct a current UX challenge or a future idea. In this type of meeting everyone contributes all of their knowledge and creativity for the shared cause, hopefully coming up with an alternative solution, a conceptual prototype tested by users as well as a clear "to-do" list for tomorrow morning.
The entire DS process consists of six stages, each possessing its individual methodology:
Understand: understanding the needs of the users, the organization and the technological abilities
Define: defining the strategic focus.
Diverge: reviewing as many ideas as possible.
Decide: choosing the best ideas.
Prototype: building a prototype which will be tested on users.
Validate: testing the ideas on IT experts and stakeholders.
The process results in a solution suitable for the customers. Nevertheless, it is important to remember that the sprint is only the first stage which is followed by another cycle of product characterization, design, reviews etc. That said, this method allows different knowledge experts to group together and quickly find the most efficient solution for the organization not having to deal with cumbersome bureaucracy and lack of coordination between teams.
I wish you success.
References:
Based on a lecture by Dana Cohen-Brown, a strategic consultant for product and user experience
コメント