66e: Choose Your RFC Audience Correctly

Not every RFC has to be shared with the whole company. Push RFCs to related people but be open to random people commenting on them.

Related Note(s):
- 32b: Communicating Organizational Changes;
- 43: The Role and Responsibility of Software Architect;
Resourced: How and Why RFCs Fail;

66d: Don't Even Try to Form A Consensus

66f: Give Enough Time for RFC Reviews (Please, Don't Rush)

This note is mentioned in:

86.

If you're unfamiliar with Zettelkasten: These notes are atomic. The aim is to have one idea in a note. The connections between notes are as important as the notes themselves.

Reply via email

or comment below.