service/documentation.md

@@ -340,10 +340,16 @@ exhaustive procedure might look something like this:
     make sure you have a good title that summarizes everything in a
     single line
 
- 6. **send document for approval**: this will vary wildly depending on
-    the affected users, but now you should send your document and hope
-    for the best. make it clear it's a proposal and that you welcome
-    changes, ideas, or dissent. give plenty of time for discussion
+ 6. **send document for approval**: bring up the proposal in a meeting
+    with the people that should be *consulted* for the proposal,
+    typically your team, but can include other stakeholders. this is
+    *not* the same as your affected users! it's a strict subset and,
+    in fact, can be a single person (e.g. your team lead). for smaller
+    decisions, this can be done by email, or, in some case, can be
+    both: you can present a draft at a meeting, get feedback, and then
+    send a final proposal by email.
+    
+    either way, a decision will have a deadline for discussion
     (typically not more than two weeks) and grant extensions, if
     requested and possible. make it clear who makes the call
     ("decision-makers" field) and who can be involved ("consulted"