SlideShare a Scribd company logo
TECHNCAL 
WRITING 
All rights reserved. ‘CrimsonLogic’ and the Shell Device are trade marks of CrimsonLogicPte Ltd. All information contained in this presentation is disclosed to you on the basis of a 
prospective business relationship and is proprietary to CrimsonLogic Pte Ltd and may not be used, disclosed or reproduced without the prior written consent of CrimsonLogic. 
CrimsonLogic Copyright 2013 Private & Confidential 
1
Agenda 
CrimsonLogic Copyright 2013 Private & Confidential 
2 
What is Technical Writing 
What Tech Writers Do 
Documentation Process 
Writing in Process 
Types of Technical Documents 
Software Tools used by Tech Writers 
Points to Ponder
What Tech Writers Do 
Tech Writers understand complex information and make it easy 
for people to use the product. A technical writer's job is to allow 
others to be relaxed and comfortable. 
Technical writer bridges the gap between the developers and 
the end users. They make sure that all the necessary information 
about a product or service is communicated in a clear, concise, 
accurate way for internal and external audiences. 
Technical writing is quite different from all other responsibilities in 
an IT company. It is not about the skill, technology expertise or 
the job responsibility. It is something [i]different[/i]. 
CrimsonLogic Copyright 2013 Private & Confidential 4
Documentation Process 
Document Development Life Cycle (DDLC) is considered as the complete life cycle of a documentation 
task. Software documentation requires a well-defined methodology for the successful completion. DDLC 
should encompass and go along with Software Development Life Cycle (SDLC) because both are 
parallel as well as intertwined. 
CrimsonLogic Copyright 2013 Private & Confidential 5
Writing in Process 
Good writing doesn’t happen overnight; it requires 
planning, drafting, rereading, revising, and editing.. 
Learning and improvement requires self-review, peer-review, 
subject-matter expert feedback, and practice. 
There are no shortcuts; practice makes perfect! 
CrimsonLogic Copyright 2013 Private & Confidential 6
Types of Technical Documents 
Technical writers mainly create documents for end users. 
1. Technical ( hardware and software) products. 
User manuals for computer programs, 
 online help, 
white papers, 
Release notes, 
Admin manuals, 
Installation guides 
Troubleshooting guides 
'frequently asked questions' (also known as FAQ) pages to help technical staff, 
consumers and other users. 
2. Marketing communication- These documents are for general audience. 
Product catalogs, 
white papers, 
brochures, 
training materials. 
The various fields where technical writers serve are Aeronautics, Robotics, Finance, 
Consumer Electronics. 
CrimsonLogic Copyright 2013 Private & Confidential 7
Tools and Techniques 
How is the information communicated? There are many methods used, such as online, in a cloud, via an 
intranet or company network, in print, multimedia presentations, video or using various media devices. 
The following types of tools are typically used to author and present technical documents: 
1. Desktop Publishing Tools or Word Processors are used to produce printed manuals or digital 
documents in print format. Microsoft Word and Adobe Frame Maker are two tools commonly 
used by technical writers. 
2. Help Authoring Tools are used to create online help systems, which are either packaged with 
software products, delivered through a web browser or provided as files the user can view on 
their computer. Adobe RoboHelp, Madcap Flare, Author-it and HelpNDoc are commonly used 
tools. 
3. Image capturing tools – SnagIt, Capturewiz. 
CrimsonLogic Copyright 2013 Private & Confidential 8
Points to Ponder 
1. Use the Page layout as Portrait and not landscape for writing documents 
2. Use the template for documenting any user guides which is kept in tech writing repository 
3. Always make use of the styles in the template don’t use generic styles 
4. Use the Track changes or comment option to comments on the user guides 
5. Remove the Draft watermark before sending the final copy 
6. Let us know earlier if the client wants the user guide 
7. Involve the Tech Comm team from the beginning of the project as it would be easier for the tech 
writer to understand about the product and can start doc based on understanding instead on relying 
on the developers very often 
8. Keep updating on the changes made to the user guide or the application 
9. Do not send the guides without technical reviews to the clients 
10.We have a Visio installed if any diagrams needed for any project let us know 
CrimsonLogic Copyright 2013 Private & Confidential 9
THANK YOU 
CrimsonLogic Copyright 2013 Private & Confidential 
10 
Laxmi & Jaisree.D.B (UAV Team) 
laxmism@crimsonlogic.co.in 
jaisreedb@crrimsonlogic.co.in

More Related Content

Similar to Technical writing training 2013 14 (2)

Maximizing Potential - Hiring and Managing Dedicated Software Developers.pdf
Maximizing Potential - Hiring and Managing Dedicated Software Developers.pdfMaximizing Potential - Hiring and Managing Dedicated Software Developers.pdf
Maximizing Potential - Hiring and Managing Dedicated Software Developers.pdf
JamesEddie2
 
IT Fundamentals
IT FundamentalsIT Fundamentals
How to Hire Flutter Developers in India Quick Guide.pdf
How to Hire Flutter Developers in India Quick Guide.pdfHow to Hire Flutter Developers in India Quick Guide.pdf
How to Hire Flutter Developers in India Quick Guide.pdf
Laura Miller
 
chapter3 Technical Skills Software Skills.ppt
chapter3  Technical Skills Software Skills.pptchapter3  Technical Skills Software Skills.ppt
chapter3 Technical Skills Software Skills.ppt
MemMem25
 
How to Overcome the Challenges of Cloud Application
How to Overcome the Challenges of Cloud ApplicationHow to Overcome the Challenges of Cloud Application
How to Overcome the Challenges of Cloud Application
Embitel Technologies (I) PVT LTD
 
Soc biz to improve stakeholder comms (devdays13)
Soc biz to improve stakeholder comms (devdays13)Soc biz to improve stakeholder comms (devdays13)
Soc biz to improve stakeholder comms (devdays13)
Thorsten Gau
 
Best Practices for API Adoption - WIP Factory presentation for AnyPresence we...
Best Practices for API Adoption - WIP Factory presentation for AnyPresence we...Best Practices for API Adoption - WIP Factory presentation for AnyPresence we...
Best Practices for API Adoption - WIP Factory presentation for AnyPresence we...
Carlo Longino
 
The Product and Process(1).pdf
The Product and Process(1).pdfThe Product and Process(1).pdf
The Product and Process(1).pdf
ShivareddyGangam
 
Building products people actually can use – why all developers need to unders...
Building products people actually can use – why all developers need to unders...Building products people actually can use – why all developers need to unders...
Building products people actually can use – why all developers need to unders...
Cyber-Duck
 
SE 18CS35 Module 1.pdf
SE 18CS35 Module 1.pdfSE 18CS35 Module 1.pdf
SE 18CS35 Module 1.pdf
balaji984829
 
Product Management Essentials
Product Management EssentialsProduct Management Essentials
Product Management Essentials
Ömer Demir
 
Best Practices for API Adoption
Best Practices for API AdoptionBest Practices for API Adoption
Best Practices for API Adoption
AnyPresence
 
The Software Development Life Cycle’s Five Stages Are Described
The Software Development Life Cycle’s Five Stages Are DescribedThe Software Development Life Cycle’s Five Stages Are Described
The Software Development Life Cycle’s Five Stages Are Described
BMN Infotech
 
Software engineering introduction
Software engineering introductionSoftware engineering introduction
Software engineering introduction
Vishal Singh
 
Roadmap to Become Experts.pptx
Roadmap to Become Experts.pptxRoadmap to Become Experts.pptx
Roadmap to Become Experts.pptx
dscwidyatamanew
 
Introduction to technical writing
Introduction to technical writingIntroduction to technical writing
Introduction to technical writing
Anil Menon
 
4.Three Hot Career Paths in Tech You Must Know.pdf
4.Three Hot Career Paths in Tech You Must Know.pdf4.Three Hot Career Paths in Tech You Must Know.pdf
4.Three Hot Career Paths in Tech You Must Know.pdf
Belayet Hossain
 
Software Engineering Unit-1
Software Engineering Unit-1Software Engineering Unit-1
Software Engineering Unit-1
Samura Daniel
 
How to become a Software Engineer Carrier Path for Software Developer
How to become a Software Engineer Carrier Path for Software DeveloperHow to become a Software Engineer Carrier Path for Software Developer
How to become a Software Engineer Carrier Path for Software Developer
jeetendra mandal
 

Similar to Technical writing training 2013 14 (2) (20)

Maximizing Potential - Hiring and Managing Dedicated Software Developers.pdf
Maximizing Potential - Hiring and Managing Dedicated Software Developers.pdfMaximizing Potential - Hiring and Managing Dedicated Software Developers.pdf
Maximizing Potential - Hiring and Managing Dedicated Software Developers.pdf
 
IT Fundamentals
IT FundamentalsIT Fundamentals
IT Fundamentals
 
How to Hire Flutter Developers in India Quick Guide.pdf
How to Hire Flutter Developers in India Quick Guide.pdfHow to Hire Flutter Developers in India Quick Guide.pdf
How to Hire Flutter Developers in India Quick Guide.pdf
 
chapter3 Technical Skills Software Skills.ppt
chapter3  Technical Skills Software Skills.pptchapter3  Technical Skills Software Skills.ppt
chapter3 Technical Skills Software Skills.ppt
 
How to Overcome the Challenges of Cloud Application
How to Overcome the Challenges of Cloud ApplicationHow to Overcome the Challenges of Cloud Application
How to Overcome the Challenges of Cloud Application
 
Soc biz to improve stakeholder comms (devdays13)
Soc biz to improve stakeholder comms (devdays13)Soc biz to improve stakeholder comms (devdays13)
Soc biz to improve stakeholder comms (devdays13)
 
Best Practices for API Adoption - WIP Factory presentation for AnyPresence we...
Best Practices for API Adoption - WIP Factory presentation for AnyPresence we...Best Practices for API Adoption - WIP Factory presentation for AnyPresence we...
Best Practices for API Adoption - WIP Factory presentation for AnyPresence we...
 
The Product and Process(1).pdf
The Product and Process(1).pdfThe Product and Process(1).pdf
The Product and Process(1).pdf
 
Building products people actually can use – why all developers need to unders...
Building products people actually can use – why all developers need to unders...Building products people actually can use – why all developers need to unders...
Building products people actually can use – why all developers need to unders...
 
SE 18CS35 Module 1.pdf
SE 18CS35 Module 1.pdfSE 18CS35 Module 1.pdf
SE 18CS35 Module 1.pdf
 
Product Management Essentials
Product Management EssentialsProduct Management Essentials
Product Management Essentials
 
Best Practices for API Adoption
Best Practices for API AdoptionBest Practices for API Adoption
Best Practices for API Adoption
 
The Software Development Life Cycle’s Five Stages Are Described
The Software Development Life Cycle’s Five Stages Are DescribedThe Software Development Life Cycle’s Five Stages Are Described
The Software Development Life Cycle’s Five Stages Are Described
 
Software engineering introduction
Software engineering introductionSoftware engineering introduction
Software engineering introduction
 
Roadmap to Become Experts.pptx
Roadmap to Become Experts.pptxRoadmap to Become Experts.pptx
Roadmap to Become Experts.pptx
 
Introduction to technical writing
Introduction to technical writingIntroduction to technical writing
Introduction to technical writing
 
Chapter 01
Chapter 01Chapter 01
Chapter 01
 
4.Three Hot Career Paths in Tech You Must Know.pdf
4.Three Hot Career Paths in Tech You Must Know.pdf4.Three Hot Career Paths in Tech You Must Know.pdf
4.Three Hot Career Paths in Tech You Must Know.pdf
 
Software Engineering Unit-1
Software Engineering Unit-1Software Engineering Unit-1
Software Engineering Unit-1
 
How to become a Software Engineer Carrier Path for Software Developer
How to become a Software Engineer Carrier Path for Software DeveloperHow to become a Software Engineer Carrier Path for Software Developer
How to become a Software Engineer Carrier Path for Software Developer
 

Technical writing training 2013 14 (2)

  • 1. TECHNCAL WRITING All rights reserved. ‘CrimsonLogic’ and the Shell Device are trade marks of CrimsonLogicPte Ltd. All information contained in this presentation is disclosed to you on the basis of a prospective business relationship and is proprietary to CrimsonLogic Pte Ltd and may not be used, disclosed or reproduced without the prior written consent of CrimsonLogic. CrimsonLogic Copyright 2013 Private & Confidential 1
  • 2. Agenda CrimsonLogic Copyright 2013 Private & Confidential 2 What is Technical Writing What Tech Writers Do Documentation Process Writing in Process Types of Technical Documents Software Tools used by Tech Writers Points to Ponder
  • 3. What Tech Writers Do Tech Writers understand complex information and make it easy for people to use the product. A technical writer's job is to allow others to be relaxed and comfortable. Technical writer bridges the gap between the developers and the end users. They make sure that all the necessary information about a product or service is communicated in a clear, concise, accurate way for internal and external audiences. Technical writing is quite different from all other responsibilities in an IT company. It is not about the skill, technology expertise or the job responsibility. It is something [i]different[/i]. CrimsonLogic Copyright 2013 Private & Confidential 4
  • 4. Documentation Process Document Development Life Cycle (DDLC) is considered as the complete life cycle of a documentation task. Software documentation requires a well-defined methodology for the successful completion. DDLC should encompass and go along with Software Development Life Cycle (SDLC) because both are parallel as well as intertwined. CrimsonLogic Copyright 2013 Private & Confidential 5
  • 5. Writing in Process Good writing doesn’t happen overnight; it requires planning, drafting, rereading, revising, and editing.. Learning and improvement requires self-review, peer-review, subject-matter expert feedback, and practice. There are no shortcuts; practice makes perfect! CrimsonLogic Copyright 2013 Private & Confidential 6
  • 6. Types of Technical Documents Technical writers mainly create documents for end users. 1. Technical ( hardware and software) products. User manuals for computer programs,  online help, white papers, Release notes, Admin manuals, Installation guides Troubleshooting guides 'frequently asked questions' (also known as FAQ) pages to help technical staff, consumers and other users. 2. Marketing communication- These documents are for general audience. Product catalogs, white papers, brochures, training materials. The various fields where technical writers serve are Aeronautics, Robotics, Finance, Consumer Electronics. CrimsonLogic Copyright 2013 Private & Confidential 7
  • 7. Tools and Techniques How is the information communicated? There are many methods used, such as online, in a cloud, via an intranet or company network, in print, multimedia presentations, video or using various media devices. The following types of tools are typically used to author and present technical documents: 1. Desktop Publishing Tools or Word Processors are used to produce printed manuals or digital documents in print format. Microsoft Word and Adobe Frame Maker are two tools commonly used by technical writers. 2. Help Authoring Tools are used to create online help systems, which are either packaged with software products, delivered through a web browser or provided as files the user can view on their computer. Adobe RoboHelp, Madcap Flare, Author-it and HelpNDoc are commonly used tools. 3. Image capturing tools – SnagIt, Capturewiz. CrimsonLogic Copyright 2013 Private & Confidential 8
  • 8. Points to Ponder 1. Use the Page layout as Portrait and not landscape for writing documents 2. Use the template for documenting any user guides which is kept in tech writing repository 3. Always make use of the styles in the template don’t use generic styles 4. Use the Track changes or comment option to comments on the user guides 5. Remove the Draft watermark before sending the final copy 6. Let us know earlier if the client wants the user guide 7. Involve the Tech Comm team from the beginning of the project as it would be easier for the tech writer to understand about the product and can start doc based on understanding instead on relying on the developers very often 8. Keep updating on the changes made to the user guide or the application 9. Do not send the guides without technical reviews to the clients 10.We have a Visio installed if any diagrams needed for any project let us know CrimsonLogic Copyright 2013 Private & Confidential 9
  • 9. THANK YOU CrimsonLogic Copyright 2013 Private & Confidential 10 Laxmi & Jaisree.D.B (UAV Team) laxmism@crimsonlogic.co.in jaisreedb@crrimsonlogic.co.in