Creator
Design and development thrive on very different workflows. Development works well with the Scrum and Kanban approaches. Design doesn't. Forcing design into a two-week rhythm leads to bad UX. But why must there be a winner and a loser? Why not create a system to allow a design-centric methodology to interface with Agile?
I have implemented progressive design workflows at several companies, and each company has unique needs, but the core format is that design occurs well ahead of development. Strategic design goals are identified based on research, design problems are scored by difficulty and work is prioritized accordingly. The approach emphasizes low fidelity designs to stay Agile.
Progressive design workflows were one part of my solution to the work bottleneck at VideoShops. I also used progressive design workflows at Prose to get the company out of development hell and meet a seemingly impossible launch deadline on a very limited budget, having eliminated the wasteful design efforts that were ongoing.
This project was done for a startup that had no design process, and specifically requested a process be created for them. This company prioritizes innovative design and does not want rigid development schedules to constrain innovation. Progressive design workflows are the ideal fit.
