forked from San-Francisco-Write-The-Docs/lone-writers-guide
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathTechnicalProductSummary
21 lines (15 loc) · 945 Bytes
/
TechnicalProductSummary
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
<!-- https://docs.google.com/document/d/16Fg8KHOcr1LwF7fV3qUsPaKvEI3MvKlW1Pzx-GeITbk/edit#heading=h.m52rdgevmfw1 -->
*************************
Technical product summary
*************************
=================================================================
How to swim in the deep water - A lone writer’s guide to survival
=================================================================
Starting notes:
---------------
* Create a Technical Product Summary.If one does not exist. Check with Marketing / Sales.
* Create a *concise* technical summary that identifies key terms, key components, and key concepts.
* The language can be "marketing-friendly" but the target audience is the technical readership in a prospect or customer organization.
* The summary provides both external and internal readers with a "road map" of the product's architecture and high-level operational features.
Hack-a-thon content:
--------------------