design-template: Design proposals are argumentative essays.
State this explicitly in the guidelines. The Grammarly blog post is
excellent and well worth the read.
Change-Id: I06ef86fab5601e3ad0e8b5b2fefd85aec25a6015
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
diff --git a/designs/design-template.md b/designs/design-template.md
index ee2841e..19be719 100644
--- a/designs/design-template.md
+++ b/designs/design-template.md
@@ -5,8 +5,16 @@
* Not all new features need a design document. If a feature can be
contributed in a single reasonably small patchset that has little impact
to any other areas, it doesn't need a design discussion and documentation.
-* The focus of the design is to define the problem we need to solve and how it
- will be implemented.
+
+* The focus of the document is to define the problem we need to solve and
+ analyse the trade-offs of different solutions. You should concentrate on
+ interactions between components, though analysing the trade-offs often
+ requires you to explore how each might be implemented.
+
+* Write this document as an [argumentative essay][argumentative-essay]. Good
+ design proposals compel the reviewers agree with the proposal's conclusions.
+
+[argumentative-essay]: https://www.grammarly.com/blog/argumentative-essay/
* This is not intended to be extensive documentation for a new feature.