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: Dealing with a vague document request From:Tony Chung <tonyc -at- tonychung -dot- ca> To:Gene Kim-Eng <techwr -at- genek -dot- com> Date:Thu, 23 May 2019 15:04:51 -0700
On Thu, May 23, 2019 at 14:15 Gene Kim-Eng <techwr -at- genek -dot- com> wrote:
> Respond to a vague request with a clear and detailed plan based on your
> interpretation of the request. Then the people who made the vague
> request can tell you what in the plan doesn't fit what they vaguely have
> in mind.
> Gene Kim-Eng
Visit TechWhirl for the latest on content technology, content strategy and content development | https://techwhirl.com