The relevance of Design Thinking as research method for Business Design is based on two very important aspects of the method. First of all, Design Thinking introduces "Empathy" into the equation. Empathy is the ability of the entrepreneur to see things through the eyes of the customer. Secondly, Design Thinking introduces "Creativity" into the equation. It is not enough that you can analyse the problem, you should also be able to come up with a solution to that problem and actually test the acceptance by your customers of that solution.
The outcome of a Design Sprint is not an end result, but rather a starting point. The goal of a Design Sprint is not to end up with a perfect solution after just one week, but to get feedback on one or two possible solutions. What we usually see is that the direction is so big (because your problem is big), you need to further split your solutions into chewable chucks to for prioritization and phasing. So don’t focus too much on building exactly what you come up with in the Sprint, the result of a successful Design Sprint is better understanding of the problem, better alignment within the team and feedback on potential solutions you can further research and design on.
The word sprint comes from the world of Agile, and it describes a short period of time, typically 1–4 weeks, set aside to accomplish a focused goal. The design sprint is no different. It uses the original concept of the sprint to describe a period of time dedicated to working on the necessary design thinking. This time-bounded paradigm is critical to the success of the design sprint. Timeboxing, as it’s sometimes called, is essential to driving the right types of behavior from the participants. In addition to speeding up the product design and development process, it also takes advantage of core parts of our human nature: energy economy and social collaboration.
Transforming concept into business: transforming the prototype into a business stream, is not only a question of product industrialization, it’s also a matter of distribution channels, customer relationship, resources, partnerships, profitable model, all things that often require the engagement of parent business unit within the company. This transformation process where your innovative concept creates an opportunity for your partner business unit is a delicate scale-up to handle.
Sprint facilitator is a hard job. Another advice to better facilitate is find a partner: to bounce off ideas, help facilitate and bridge the gap of knowledge. If you don’t personally work with the team who participants in the Sprint, then find a partner in the team who understand the problem space; If you are too familiar with the team or problem, then find a partner to help bring the team back to focus while rat holing, or simply do time management if you are uncomfortable doing so.
You’re the product person in your organization. You may have no one reporting to you. You might have 50 people in your product group. You might be responsible for the entire product. Maybe the design team doesn’t report to you, nor do the developers or marketing and sales teams. Maybe you’re in a startup without all those defined roles, and you wear a lot of hats. Maybe you’re in a large enterprise organization that has each one defined to the nth degree. Maybe you are a product design freelancer. You might work in an agency as a consultant. You probably have read a blog post about this process. Maybe you even tried one yourself. You’re very likely wondering how your unique needs will work with design sprints and are seeking more information than you can find in a few blog posts.
Ah, Tuesday morning. A leisurely stroll around the gallery of concept sketches, coffee cup in hand, taking it all in. We spend the whole morning deciding what to prototype, starting with the Heat Map, where people place multiple votes on inspiring parts of sketches so that clusters can form. These clusters are then highlighted in the solution presentations, where the moderator walks the room through each individual sketch, followed by the straw poll (where everybody puts one vote on the one solution they want to push forward). The morning is rounded off with the Decider’s vote, where they pick one or two concepts that they want to prototype.
A great morning spent @Google London, focussing on ‘Design Sprints for Change’. 400 applications for the event, 100 in the room – it is a movement. It was fascinating to see how other big and small businesses are employing the same approach as RGAX to help their business grow by helping others. It was also nice to reconnect with John Vetan and Dana Vetan @designsprintacademy who showed us the way to identify real problems worth solving and create solutions you can test – all in 5 days!
In Design Thinking Peter Rowe provides a systematic account of the process ofdesigning in architecture and urban planning. He examines multiple and often dissimilar theoreticalpositions whether they prescribe forms or simply provide procedures for solving problems - asparticular manifestations of an underlying structure of inquiry common to all designing. Over 100illustrations and a number of detailed observations of designers in action support Rowe'sthesis.Peter G. Rowe is Raymond Garbe Professor of Architecture and Urban Design at HarvardUniversity and Chairman of the Department of Urban Planning and Design at the Harvard GraduateSchool of Design, Harvard University.
After a career in user experience design and research at companies like Microsoft and Nuance, Trace then became a developer at Pivotal Labs, and is now a Managing Director at thoughtbot. He has facilitated numerous product design sprints, and is an author and maintainer of thoughtbot's design sprint methodology repository. He's brought Lean and Agile methodology to many large companies and small startups, helping teams to focus, prioritize, and become happy and productive.
What I Find Noteworthy: Well-known MOOC provider partnering with one of the world’s most respected design sprint firms, to deliver a crash course on design sprints. I’ve strongly considered taking this class as I already enjoy watching AJ&Smart’s videos on YouTube. In addition to providing a good baseline knowledge of design sprints, the class seems like a great way to get in some “practice reps” before attempting to facilitate an actual sprint.
“For most organizations, doing some prototypes and a small beta test would be a good example of Design Thinking, but for a company with the heft of Google, they can absolutely afford to ‘launch’ something and see how it does without putting themselves at risk,” Rose wrote. “The amount of info that they learned from developing and launching it was incredible.”
Jake Knapp describes Design Sprints as a greatest hits of productivity, decision making, innovation, creativity, and design — and I think that’s true. But I recently took part in a sprint which modified this “greatest hits” formula heavily. My gut feeling was that these modifications were not beneficial, but since I was unfortunately not in a position to change the process, I chose to view it as an opportunity to gather data, and do a comparative analysis between this sprint, and the GV process outlined in the book — to learn, and to be more prepared for the next time around. https://i1.wp.com/s3.amazonaws.com/production-wordpress-assets/blog/wp-content/uploads/2016/11/23155646/RAD.png?fit
In employing design thinking, you’re pulling together what’s desirable from a human point of view with what is technologically feasible and economically viable. It also allows those who aren't trained as designers to use creative tools to address a vast range of challenges. The process starts with taking action and understanding the right questions. It’s about embracing simple mindset shifts and tackling problems from a new direction.
As a Sprint facilitator, it is very easy to focus too much on the “How” while planning a Sprint: When is the date? What is the room situation? What are the activities and agenda for each day? Those are questions that are important but not critical. Before getting into the logistics, there are two important things to focus on to ensure the success of a Design Sprint.
With more than 500 new apps entering the market every day, what does it take to build a successful digital product? You can greatly reduce your risk of failure with design sprints, a process that enables your team to prototype and test a digital product idea within a week. This practical guide shows you exactly what a design sprint involves and how you can incorporate the process into your organization. https://res.cloudinary.com/practicaldev/image/fetch/s--MOjiyoD1--/c_fill,f_auto,fl_progressive,h_50,q_auto,w_50/https://thepracticaldev.s3.amazonaws.com/uploads/user/profile_image/25530/7ab56374-e563-4ba2-8f3b-6b200253f875.png
You will receive a Sprint Master toolkit containing all the canvases you need to run your own Design Sprints. The kit also includes two Sprint Master's guidebooks you will use to set up the perfect sprinting pace and never get lost when facilitating a Design Sprint. The Blue Book covers the GV model and The Black Book the MVS model. These hands-on manuals and canvases are a treasure you will only find in this program. They come full of tips and hacks giving you the confidence you need to run your own Design Sprints.
The Sprint method allowed the team to start prototyping quickly, collect immediate user feedback, and make small mistakes early. We conducted multiple design sprints in quick loops—folding the learning from week one into the structure of week two, and so on. We learned a lot in the process. Here are a few quick tips we picked up for running successful and energizing design sprints.
A great morning spent @Google London, focussing on ‘Design Sprints for Change’. 400 applications for the event, 100 in the room – it is a movement. It was fascinating to see how other big and small businesses are employing the same approach as RGAX to help their business grow by helping others. It was also nice to reconnect with John Vetan and Dana Vetan @designsprintacademy who showed us the way to identify real problems worth solving and create solutions you can test – all in 5 days! https://www.tatvasoft.com/blog/wp-content/uploads/2015/12/agile_software_development_methodology.jpg
Page 203 - ... unjustified and erroneous, so that they inevitably distort the truth. In fact, the historicity of our existence entails that prejudices, in the literal sense of the word, constitute the initial directedness of our whole ability to experience. Prejudices are biases of our openness to the world. They are simply conditions whereby we experience something — whereby what we encounter says something to us.