Interesting idea. I can see this working with a small team of the right people, but I can also see it being counterproductive in some ways.<p>Specifically, the amount of process described in this document is massive. Printed out, it becomes 9 pages of process. Surely competent engineers can pick up on it quickly by following the guide, but what benefit does all of this process have over simply creating a Wiki page and having each team member write their discussion in their own section?<p>These things always feel fun at small companies within the teams that conceived them, but it's easy to lose track of how unwieldy these process- and tech-heavy solutions to simple communication problems are for newcomers.
I read this in earnest and think it's pretty cool. I really like Bryan Cantrill.<p>I couldn't fully grok the flow between ideation and prediscussion. I found that a little "fine grained". My understanding was hindered by the typos in the ideation section.