There's this general advice of "keeping people in the loop", and I like the advice proposed at the bottom of the article, but I do think there's potential for m

There's this general advice of "keeping people in the loop", and I like the advice proposed at the bottom of the article, but I do think there's potential for more guidance on this topic, as teams work differently depending on the overall workstyle or the specific circumstances of a project. If your team is all a bit allergic to endless design doc discussion, dropping one of those in Slack might not work too great. But maybe pair programming with one or two others on the feature to help get feedback could! Others do like to plan things out, so having the running Google Doc, or "one-page design docs" with recurring check-ins with a core group of people can do wonders. There's the Amazon-style "write the marketing pitch", or internal-facing API documentation. And for some people iterative can mean shipping your API in layers, whereas for others it means shipping features bit-by-bit. There are a lot of options, and I would love to see a huge compendium about it!