In this talk, the speaker argues that faster iteration is the key to gaining market advantage, and the most critical handoff in software development is the transition from design to engineering. He outlines a concrete workflow used in multiple startups: designers work in Figma on two boards—'Concept Designs' for exploratory work and 'Ready for Engineering' for polished, dated iterations. Each item on the Ready board is copied as a deep‑link and pasted into the corresponding Jira ticket, which engineers then pick up, develop, pass to QA, receive product approval, and ship. By executing this loop daily—design, engineer, QA, product review, release—the team can continuously gather market feedback, update designs, and ship improvements, thereby accelerating learning and outpacing competitors.
Chapters
Good morning. This whole ballgame is about increasing iteration speed so you can increase your learning time and execute faster than your competitors in the marketplace and capture more of the market and help people at the end of the day. So what's one way to do that? Well, if you're in the software industry, it's about handoffs, which we've talked about in terms of organizational design before. And what's the handoff that really matters? One is from product to design and design to engineering and engineering to out the door, QA, et cetera. So let's talk about this design to engineering handoff. We've used this process in the past over a couple different startups and it's worked really, really well. And it's essentially this. So you're iterating in Figma, right? So you have 2 boards. One is concept designs and the other one is Ready for Engineering. Within the Concept Design board, it can be messy. It's owned by the design team, and it's just where you do concepts and play around. The Ready for Engineering board is structured a little bit more formally from top to bottom. It's almost like a feed. Every item is listed with a date. Every iteration is listed with a date. It's a copy and paste of the prior version, plus updates with callouts of those updates. You right-click, you copy the deep link, and you paste that into the Jira engineering ticket that represents that unit of work. That work then gets picked up by engineering, it gets executed against, then it shifts to QA, product approval, go/no-go, then it's out the door. And if you can execute on that on a daily basis in real time, you're iterating. Getting feedback from the market, updating a design, executing it in engineering, putting it out into the world, reviewing the metrics, and then doing that over and over again. That engine of iteration will help you win, period. That's it. That's the whole ballgame. Iteration speed. Let's go, everybody. All right. Have a great day.
