TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:RE: more formal title - technical teaser ? From:"Elissa K. Miller" <emiller -at- doubleknot -dot- com> To:"'TechWR-L'" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 16 Oct 2013 13:04:36 -0700
I like Gene's suggestion of "Preview." I'm whimsy-averse when it comes to technical communications, even in marketing-oriented documents, since it's usually a big departure from the existing company voice, so "teaser" feels like a problem unless your company is already whimsical.
You could also try something like "Proposed Solution Overview" which is wordy but accurate--the company is proposing a solution and here is the overview. Or, just "Solution Proposal," or "Proposed Solution," or other titles in that vein. That solves the potential issue of a client thinking "Hey, it's a preview of something that's going to be available! Yay!" when in fact it's a proposal for something that they will have to fund if they want it.
SAP used to call documents that described features that didn't exist "Roadmaps," although they did intend to build that road without additional funding from their customers. "Proposed Roadmap" might work? "Solution Roadmap?"
I guess "You Want It? You Fund It!" is right out of the question.
Oh, this is so much more interesting than proofreading.
--Elissa Miller
-----Original Message-----
From: techwr-l-bounces+emiller=doubleknot -dot- com -at- lists -dot- techwr-l -dot- com [mailto:techwr-l-bounces+emiller=doubleknot -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf Of Gene Kim-Eng
Sent: Wednesday, October 16, 2013 12:26 PM
To: Monique Semp; TechWR-L
Subject: Re: more formal title - technical teaser ?
I think the suitability of "overview" depends on whether the company can provide the solution now, or whether it's something they would want to be paid to develop. If it's not something that's currently available for delivery, then "teaser" or "preview" might be the best description.
Gene Kim-Eng
On 10/16/2013 10:01 AM, Monique Semp wrote:
>
> See below for details, but so far my best choice is âSolution Overviewâ.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.
