Breaking down a design

Thanks to Amy Hupe, I learned that there's such a thing as National Blog Posting Month (#NaBloPoMo for short), and it starts today. So here we go with post number 1. Yesterday I needed to help a team break down a design to get it ready for development. I enjoy this because it's quite high leverage work, can open interesting debates, and although I find it challenging, I feel confident leading it. There are certain patterns that help it go smoothly. And once it's done and the panic of 'oh gosh… where do we start?' has lifted, you can all feel really good and get cracking. So how does it tend to go, and what are those patterns that help me do it? To start with, I hope everyone on the team already knows the product outcome you're striving for, and what specific opportunity this design aims to tackle. Do this with a design that's at the right level of 'done' - enough to have a clear idea what needs to be built, but not so complete that you've wasted time on details that might get de-scoped

Thanks to Amy Hupe, I learned that there's such a thing as National Blog Posting Month (#NaBloPoMo for short), and it starts today. So here we go with post number 1. Yesterday I needed to help a team break down a design to get it ready for development. I enjoy this because it's quite high leverage work, can open interesting debates, and although I find it challenging, I feel confident leading it. There are certain patterns that help it go smoothly. And once it's done and the panic of 'oh gosh… where do we start?' has lifted, you can all feel really good and get cracking. So how does it tend to