Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Users Search
Help Dashboard Sign In Sign Up
Q&A Challenges Meta
Q&A
Posts Tags Edits
Ask Question

Post History

50%
+0 −0
Q&A Should software product release notes be in marketing voice or technical voice? (software documentation)

Typically, the voice of marketing content doesn't match the voice of technical content -- marketing is trying to persuade you that you need something; technical writing is generally instructing you...

3 answers  ·  posted 7y ago by Sharon M‭  ·  last activity 5y ago by System‭

Question software style technical-writing notes software-documentation release-notes documentation
#9: Post edited by user avatar Monica Cellio‭ · 2019-12-13T03:23:38Z (almost 5 years ago)
  • Typically, the voice of marketing content doesn't match the voice of technical content -- marketing is trying to persuade you that you need something; technical writing is generally instructing you how to use something. (I'm specifically talking about software.)
  • I have traditionally taken a techcomm approach to release notes -- describing new features and bug fixes in a straightforward manner, focused on the user. The marcomm folks often describe the features with a very different vocabulary. For most content, this distinction is clearer -- software documentation is techcomm; web sites, blogs, press releases are marcomm.
  • A case can be made for the release notes serving a marketing purpose in addition to a technical purpose -- reaching business decision makers in addition to technician-type users. How do you decide the appropriate voice for the release notes?
  • Typically, the voice of marketing content doesn't match the voice of technical content -- marketing is trying to persuade you that you need something; technical writing is generally instructing you how to use something. (I'm specifically talking about software.)
  • I have traditionally taken a techcomm (technical communication) approach to release notes -- describing new features and bug fixes in a straightforward manner, focused on the user. The marcomm (marketing communication) folks often describe the features with a very different vocabulary. For most content, this distinction is clearer -- software documentation is techcomm; web sites, blogs, press releases are marcomm.
  • A case can be made for the release notes serving a marketing purpose in addition to a technical purpose -- reaching business decision makers in addition to technician-type users. How do you decide the appropriate voice for the release notes?
#8: Post edited by user avatar Monica Cellio‭ · 2019-12-13T03:23:00Z (almost 5 years ago)
  • Typically, the voice of marketing content doesn't match the voice of technical content -- marketing is trying to persuade you that you need something; technical writing is generally instructing you how to use something. (I'm specifically talking about software.)
  • I have traditionally taken a techcomm approach to release notes -- describing new features and bug fixes in a straightforward manner, focused on the user. The marcomm folks often describe the features with a very different vocabulary. For most content, this distinction is clearer -- software documentation is techcomm; web sites, blogs, press releases are marcomm.
  • A case can be made for the release notes serving a marketing purpose in addition to a technical purpose -- reaching business decision makers in addition to technician-type users. How do you decide the appropriate voice for the release notes?
  • Typically, the voice of marketing content doesn't match the voice of technical content -- marketing is trying to persuade you that you need something; technical writing is generally instructing you how to use something. (I'm specifically talking about software.)
  • I have traditionally taken a techcomm approach to release notes -- describing new features and bug fixes in a straightforward manner, focused on the user. The marcomm folks often describe the features with a very different vocabulary. For most content, this distinction is clearer -- software documentation is techcomm; web sites, blogs, press releases are marcomm.
  • A case can be made for the release notes serving a marketing purpose in addition to a technical purpose -- reaching business decision makers in addition to technician-type users. How do you decide the appropriate voice for the release notes?
#7: Post edited by user avatar Monica Cellio‭ · 2019-12-13T03:22:48Z (almost 5 years ago)
  • Typically, the voice of marketing content doesn't match the voice of technical content -- marketing is trying to persuade you that you need something; technical writing is generally instructing you how to use something. (I'm specifically talking about software.)
  • I have traditionally taken a techcomm approach to release notes -- describing new features and bug fixes in a straightforward manner, focused on the user. The marcomm folks often describe the features with a very different vocabulary. For most content, this distinction is clearer -- software documentation is techcomm; web sites, blogs, press releases are marcomm.
  • A case can be made for the release notes serving a marketing purpose in addition to a technical purpose -- reaching business decision makers in addition to technician-type users. How do you decide the appropriate voice for the release notes?
  • Typically, the voice of marketing content doesn't match the voice of technical content -- marketing is trying to persuade you that you need something; technical writing is generally instructing you how to use something. (I'm specifically talking about software.)
  • I have traditionally taken a techcomm approach to release notes -- describing new features and bug fixes in a straightforward manner, focused on the user. The marcomm folks often describe the features with a very different vocabulary. For most content, this distinction is clearer -- software documentation is techcomm; web sites, blogs, press releases are marcomm.
  • A case can be made for the release notes serving a marketing purpose in addition to a technical purpose -- reaching business decision makers in addition to technician-type users. How do you decide the appropriate voice for the release notes?
#6: Post edited by user avatar Monica Cellio‭ · 2019-12-13T02:43:03Z (almost 5 years ago)
  • Typically, the voice of marketing content doesn't match the voice of technical content -- marketing is trying to persuade you that you need something; technical writing is generally instructing you how to use something. (I'm specifically talking about software.)
  • I have traditionally taken a techcomm approach to release notes -- describing new features and bug fixes in a straightforward manner, focused on the user. The marcomm folks often describe the features with a very different vocabulary. For most content, this distinction is clearer -- software documentation is techcomm; web sites, blogs, press releases are marcomm.
  • A case can be made for the release notes serving a marketing purpose in addition to a technical purpose -- reaching business decision makers in addition to technician-type users. How do you decide the appropriate voice for the release notes?
  • Typically, the voice of marketing content doesn't match the voice of technical content -- marketing is trying to persuade you that you need something; technical writing is generally instructing you how to use something. (I'm specifically talking about software.)
  • I have traditionally taken a techcomm approach to release notes -- describing new features and bug fixes in a straightforward manner, focused on the user. The marcomm folks often describe the features with a very different vocabulary. For most content, this distinction is clearer -- software documentation is techcomm; web sites, blogs, press releases are marcomm.
  • A case can be made for the release notes serving a marketing purpose in addition to a technical purpose -- reaching business decision makers in addition to technician-type users. How do you decide the appropriate voice for the release notes?
#5: Post edited by user avatar Monica Cellio‭ · 2019-12-13T02:42:27Z (almost 5 years ago)
  • Typically, the voice of marketing content doesn't match the voice of technical content -- marketing is trying to persuade you that you need something; technical writing is generally instructing you how to use something. (I'm specifically talking about software.)
  • I have traditionally taken a techcomm approach to release notes -- describing new features and bug fixes in a straightforward manner, focused on the user. The marcomm folks often describe the features with a very different vocabulary. For most content, this distinction is clearer -- software documentation is techcomm; web sites, blogs, press releases are marcomm.
  • A case can be made for the release notes serving a marketing purpose in addition to a technical purpose -- reaching business decision makers in addition to technician-type users. How do you decide the appropriate voice for the release notes?
  • Typically, the voice of marketing content doesn't match the voice of technical content -- marketing is trying to persuade you that you need something; technical writing is generally instructing you how to use something. (I'm specifically talking about software.)
  • I have traditionally taken a techcomm approach to release notes -- describing new features and bug fixes in a straightforward manner, focused on the user. The marcomm folks often describe the features with a very different vocabulary. For most content, this distinction is clearer -- software documentation is techcomm; web sites, blogs, press releases are marcomm.
  • A case can be made for the release notes serving a marketing purpose in addition to a technical purpose -- reaching business decision makers in addition to technician-type users. How do you decide the appropriate voice for the release notes?
#4: Post edited by user avatar Monica Cellio‭ · 2019-12-13T02:42:22Z (almost 5 years ago)
  • Typically, the voice of marketing content doesn't match the voice of technical content -- marketing is trying to persuade you that you need something; technical writing is generally instructing you how to use something. (I'm specifically talking about software.)
  • I have traditionally taken a techcomm approach to release notes -- describing new features and bug fixes in a straightforward manner, focused on the user. The marcomm folks often describe the features with a very different vocabulary. For most content, this distinction is clearer -- software documentation is techcomm; web sites, blogs, press releases are marcomm.
  • A case can be made for the release notes serving a marketing purpose in addition to a technical purpose -- reaching business decision makers in addition to technician-type users. How do you decide the appropriate voice for the release notes?
  • Typically, the voice of marketing content doesn't match the voice of technical content -- marketing is trying to persuade you that you need something; technical writing is generally instructing you how to use something. (I'm specifically talking about software.)
  • I have traditionally taken a techcomm approach to release notes -- describing new features and bug fixes in a straightforward manner, focused on the user. The marcomm folks often describe the features with a very different vocabulary. For most content, this distinction is clearer -- software documentation is techcomm; web sites, blogs, press releases are marcomm.
  • A case can be made for the release notes serving a marketing purpose in addition to a technical purpose -- reaching business decision makers in addition to technician-type users. How do you decide the appropriate voice for the release notes?
#3: Attribution notice added by user avatar System‭ · 2019-12-08T07:56:01Z (almost 5 years ago) 
Source: https://writers.stackexchange.com/q/33225
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision by user avatar Sharon M‭ · 2019-12-08T07:56:01Z (almost 5 years ago) 
Typically, the voice of marketing content doesn't match the voice of technical content -- marketing is trying to persuade you that you need something; technical writing is generally instructing you how to use something. (I'm specifically talking about software.)

I have traditionally taken a techcomm approach to release notes -- describing new features and bug fixes in a straightforward manner, focused on the user. The marcomm folks often describe the features with a very different vocabulary. For most content, this distinction is clearer -- software documentation is techcomm; web sites, blogs, press releases are marcomm.

A case can be made for the release notes serving a marketing purpose in addition to a technical purpose -- reaching business decision makers in addition to technician-type users. How do you decide the appropriate voice for the release notes?
#1: Imported from external source by user avatar System‭ · 2018-02-13T18:07:57Z (almost 7 years ago) 
Original score: 36