How to Make Unicorn Teams, Instead of Waiting for Unicorns

Designers, Engineers and Product Managers all want to do the right thing: to deliver value. This looks different depending on what lens you come from: design, engineering or product. We often all end up upset at the end of process. Why does this happen? All of these “forced trade-offs” are consequences of waterfall discovery (while delivery is agile, the process of deciding what we do—discovery—is often still waterfall.) This approach is critique-last, and waits for a whole bunch of work to be done before we determine if it’s feasible or not. And that leads to compromised deliverables. With the help of an interactive puzzle-game: we’ll look at how a collaborative-first approach combined with patterns-thinking allows us to work as a cross-functional team during solutions discovery to drive outcomes and solve a problem without painful compromises or disappointments, without large inter-dependent deliverables, and without needing to see designs for what you need to build when you start estimating.