Dissecting the Design Sprint Event
Step One: Refining the Problem
The first step during a design sprint at AF CyberWorx is refining the problem. Stakeholders have an idea of what problem they want to solve. They may want to save time, streamline or automate processes, fix a system showing bad metrics, or set up a policy for a new requirement. Initial problem statements may reflect this focus, but usually lack the specifics the problem solving team needs to be effective.
Larry Marine, lead UX designer at AF CyberWorx, explains why it’s so important to re-examine the problem statement. As he states, “If you don’t know what problem you need to solve, the best you can hope to do is solve the wrong problem very well.” Just like a mission statement gives direction for a business, an accurate problem statement gives teams a solid visualization of what they need to achieve. Larry gives an example of a poor problem statement from his previous experiences: