"Before writing on virtual paper, I usually think about what I want to write, usually I start to imagine phrases and ideas a few days ago, most often happening when I go to bed in the morning or commute. It's really time. "
"It is somewhat similar to writing a letter to a friend, I want people to look at my sentences to feel that their attention is drawing attention so I will think from their perspective."
In 2016, I read about the "Sprint" process. That's all about solving the problem. I was fascinated by Jake Knapp, John Zeratsky and Mr. Braden Kowitz "Sprint: How to solve big problems and try new ideas in 5 days" and proposed to put them into practice. Group Innovation Workshop The basic concepts are 1) problem definition, 2) personal brainstorming solution, 3) solution to test, 4) prototype creation and solution testing. Spend a few hours in meetings and groups, or talk about problems (whatever it is) and group brainstorming solutions (for whatever reason they are always stopped and not implemented during brainstorming) Finally, I have a real impact And found a model that appealed to me to make a real change. The seminar is going well, I know what we are doing.
It is a pleasure to get an initial copy of Sprint on how to solve the big problem in 5 minutes and test new ideas by three design partners of Google Ventures, Jake Knapp, John Zeratsky, and Braden Kowitz. A couple of years ago, Jake developed a sprint that can quickly answer important questions through design, prototyping, and customer testing ideas. In many respects it is the greatest achievement in business strategy, innovation, behavioral science, design thinking, etc. - a proven process that is organized in every team. This is a process that cooperates with GV Portfolio such as Slack, Blue Bottle Coffee, Foundation Medicine. Now they have put all the way into one book so that teams around the world can start their own sprints.
Before reading Sprint of Jake Knapp, John Zeratsky, Braden Kowitz, I knew well about the sprint process. This includes solving major problems and trying out new ideas in 5 days. But I do not understand much about the complexity and the exercises needed to make the sprint successful. Fortunately, Sprint was very happy opening his eyes. There are multiple exercises every day, such as identifying and investigating problems, determining and prototyping potential solutions, and working with actual users to obtain qualitative feedback on problems and solutions. This process is designed to compress the traditional product development process (weeks or months) to one week, providing better learning and faster iteration. After practicing this, I am a big fan