It seems natural that the design team, being as it is in the service of the development team, should be organized in the same way, around a 2-week sprint. Unfortunately, in practice, that rarely works well. There is a vast difference between the work required to design the product and the work required to build one. Here’s how to keep both teams happy and productive.
Nothing comes close to the negative impact on the morale and effectiveness of your designers than this one word you should ban from your office.
Someone recently asked me, “What is the most inventive thing you’ve done?” Woa. Full stop. Talk about a total brain freeze. You mean out of over 100 projects, patents, client engagements, talks, and workshops… I had to pick just one? But after only a moment’s hesitation, I realized that there was simply no debate.
“Arrogance and fear still keep you from learning the simplest and most significant lesson of all,” Ancient One tells Dr. Strange. “It’s not about you.” Let me break this down into four key lessons that this particular arrogant and fearful fool had to learn the hard way.
Make your lean UX design practice more collaborative and productive by employing these four sophisticated yet straightforward lean UX communication strategies, especially adapted for success in large, distributed organizations.
Not every UX strategy meets with instant success in complex organizations, especially at companies in a transition from traditional heavy industries, or those whose culture is dominated by engineering. The 3.5 Lean UX hacks described in this article are hands-on, practical strategies to help you make your design and research practice more collaborative and productive in a large organization, while also preserving your sanity.
Video: 30-min TED-style talk at the sold-out UX New Zealand conference. Practical Tips for successfully applying #LeanUX #DesignOps techniques in large, complex organizations traditionally dominated by engineering.