<li>Explicitly note what <b>next action</b> you propose or expect and from who.</li>
<li>There is no need for consensus, make sure that you give people that might have good insights a chance to respond (by /cc'ing them) but make a call yourself, <ahref="https://twitter.com/sama/status/585950222703992833">consensus doesn't scale</a>.</li>
<li>If you need to discuss with a team member for help please realize that probably the majority of the community also doesn't know, be sure to <b>document</b> the answer to radiate this information to the whole community.</li>
<li>If something is out for the whole community to see (eg. Something is released but needs further work), consider raditing that information to avoid confusion. If it is obvious to you, does not mean it is for everybody.</li>
<li>Be <b>specific</b> in your written communication, especially externally. Do not reply with a generalization when you can give an example.</li>
<li>All company data should be <b>sharable</b> by default. Don't use a local text file but leave comments on an issue. Create Google docs with your company Google Apps account.</li>
<li>Do not close an issue until it has been <b>reported</b> back to all parties and issue trackers involved.</li>
