Lean UX was one of the first process that included applied methods and techniques to create better UX in an agile timeline. Based on Lean UX, we are aware of the terms like Prototyping, Hypothesis', MVP, HMW's or Testing assumptions. Back in the days, when Google Ventures experimented with known and new ways of efficient product design, a new comprehensive and successful framework was born to combine the necessary techniques and put them into a conceivable order to create product ideas fast and without creating waste or unread documentation. The Design Sprint was born. A one-week process for testing ideas and quickly creating a prototype to test with real users.
But as good as it was to get a fully tested prototype to work with, as problematic it was when it came to the holistic view of agile product development - where developers and product owners were incharge to take our concepts and create real product increments. The Design Sprint itself never wanted to be more as a source of inspration. But we ended up on a step, where design leads to a final concept which has to be developed in another or second step - within our sprint setup.
A description of goals we set up for this project. We can use either bullet points or a description:
- Design is often misunderstood
- Design becomes too heavy to implement
- Design and development work in different paces or as isolated teams
- Late feedback from the users
- UX is not prioritised equally in sprints
- Inconclusive results
Wouldn't be great if we had just one, holistic product design & development framework that is both User-Centred and Agile? For this reason and based on Lean UX and Design Sprint methodologies, we invented the UX Burner, a fully integrated framework that brings UX design into
Scrum development teams and activities. It combines the best of agile, lean thinking and product design into one single process. UX Burner helps teams to have a shared perspective of the problem; have ownership; work collaboratively; make effective decisions; test product hypothesis; and release minimum desirable experiences in short cycles. To better understand the idea behind these two frameworks, let's do a little comparision.
Where the Design Sprint supports a one-week (DS 2.0 not considered) to design and test prototypes, the UX Burner goes one step further by unifying Lean UX and Scrum to develop, design and test features and release product increments, which can now be validated directly on the user’s end.
Dave Werkheiser Manufacturing Engineer John Deere
“The advantage of being able to just pick up the magnetic tape and change the layout in a matter of minutes allows us to change an entire line over a weekend”
From creating a map to capture users experiences, to sketching concepts and features, to deciding on promising solutions and transferring those into Storyboards, till creation and testing of the final prototype(s) - the Design Sprint delivers a full set of activities to create and process concepts and prototypes which can be used as the basement for the further development cycle.
However, the UX Burner shows up as more versatile and scalable. Whether you need to solve problems, build your idea from scratch, improve your existing product, integrate UX design into your Scrum, integrate UX design in SAFe (Scaled Agile Framework) or give your team a creative culture then UX Burner has you covered. It includes lightweight methods for creative problem solving and productivity. Based on our experience and research, we have picked the methods that have been widely proven to produce actionable results.
The following are the UX Burner activites used in sprints:
- Burner canvas - To define problems, understand the impact, define the measure of success and map out a minimum desirable experience.
- Design workshop - To move from abstract to concrete solutions using a uniquely structured ideation session.
- Prototyping - To convert the rough sketches into a digital prototype so that we can evoke honest reactions from the users.
- Pair & Share - To establish a proactive communication. Designer & developer work on the same problem at the same time.
- User Test - To learn early and often. Regular user test will be done by the teams to test the assumptions from real users.
Conducting a Design Sprints usually or often means to sit together with your designers, product managers or contractors/partners and create prototypes based on brainstormed ideas. And getting a buy-in to have all the folks in the same room for 5 full days is really expensive. The main difference here is, that the UX Burner uses a smarter approach to include stakeholders in its activites only when it's important.
Thank you for taking your time and for interest in that topic.