Post History
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...
#9: Post edited
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
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
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
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
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
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
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
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?