| TECHNICAL
WRITING: Communicating
in plain English about technical subjects. |
| TECHNICAL
EDITING: Planning
and refining content to meet quality standards. |
|
|
|
|
|
|
I am primarily a writer, occasionally an editor. I am also a freelance professional.
|
|
|
|
|
|
| A
technical writer must... |
|
|
|
|
|
|
• |
Write
about complex subjects in a clear, concise and consistent way. |
|
• |
Organize
important information so it's easy to find. |
|
• |
Make
valuable knowledge available to readers who might be non-technical,
confused, impatient, or simply looking for the answer to a question. |
|
|
|
|
|
| Additionally,
a freelance professional must... |
|
|
|
|
|
|
• |
Ramp-up
quickly on project history and client operations. |
|
• |
Understand
and manage all time, budget and scope constraints. |
|
• |
Know
(or adapt to) the software, tools, and other technologies
required. |
|
• |
Work
effectively with project managers, developers, and other personnel. |
|
|
|
|
|
I
bring all this and more to my work. I have been especially effective
on projects that involved me after they were already in crisis
mode, where managers needed help meeting dates for deliverables that were seriously at risk.
|
|
| I
provide my services to the following kinds of teams: |
|
|
|
|
|
• |
Product
development (user guides, admin guides, deployment guides, Help) |
|
• |
Sales/marketing
(pre-sales collateral, Web content, whitepapers, reports) |
|
• |
Software
developers (SDK, design specs, functional specs, use cases) |
|
• |
Professional
services (business analysis, engagement summaries, SOWs) |
|
• |
Enterprise
IT (process flows, requirements, disaster recovery plans) |
|
|
|
|
| Overall,
my clients value my flexibility and diplomacy skills on the projects I pursue, in addition to my written
communications ability and technical grasp. |
|
|
|
|
|
|
|
|
