4/7/2023 0 Comments Gregg brune system designer![]() ![]() Just like when you’re presenting mockups for feedback, it’s not enough to just present your work on screen and expect instant alignment. Now you just need to get everyone on board. So inevitably you reach the point where you think you have something you’re happy with. “You need to create the scaffolding for how you want your stakeholders to interrogate the system design” You want to figure all that out at the very start. You don’t want to realize you’ve all been singing from different hymn sheets several months into building something, and then take on an expensive course correction. The goal is to hammer out these differences early on, while doing so is still cheap. It’s difficult because it forces you to resolve ambiguity, ferret out unknown unknowns, get super-specific about how the system will work, and agree on it all. All of the things that make a canonical system design difficult to nail down are the reasons it’s worth doing. Herein lies the very point of doing this work. Once people start thinking in systems, they see how everything’s connected, which naturally leads them to add more and more scope “because, like, everything’s connected, man!” *exhales, coughs*
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |