Every profession has the same discipline:

To consistently identify, specify, design and deliver the right product at the right price.

Featured: Consistency, Identify, Specify, Design

1. Consistency

How often do you turn into the wrong drive-way when you go home?  How often do you forget your income tax?

We don't make these mistakes often because we have some kind of procedure to make sure we do the right things at the right time.  read more.

2. Identify

What is today's biggest question?  Are you who you say you are?  We all want accurate identification.  In Technical Writing accurate identification is about How, Who, What, When, Where, Why.

To deliver the right product at the right price, we have to ask a lot of questions.  read more

3. Specify

What is "quality"?  For most people there are as many answers as there are people to ask.  The practical answer is: the item satisfies my needs.  read more

4. Design

If this is a "standard" documentation task – meaning you have a template (because the design of the document is the same as last time), you're done.

Almost.  read more

 

Featured: Deliver, Right Product, Right Price

5. Deliver

We lie!  It is produce and deliver.  read more

6. The Right Product

The Right (documentation) Product comes out of the Identify, Specify and Design procedures.  read more

7. The Right Price

The Right Price comes out of the Identify and Specify procedures. And sometimes out of the Design procedure if the Design leads to Identify and Specify revisions.  read more

8. Professional Development: not for everyone?

The very young, the very old and other similar categories probably don't need to think about professional development.  But everyone else should.

Why?  read more

Details
Last Updated: 09 January 2014 09 January 2014
Hits: 9047 9047

Deliver

We lie.  It is really produce and Deliver.

The produce part of the procedure is easy: create > proof >  edit > review > revise.  

Create because our documentation product may not be a written document.  We keep going around this loop as often as the project plan allows.  Deliver follows after that. 

  To deliver we need to know (and should already know):

  • To whom?
  • What is the handover process"
  • What support is needed?
  • When is the next version due?

 What is the most important project document "delivery" that is seldom delivered?

A Lessons Learned Report.

If we take the time to ask ourselves a few important questions and keep the answers, we will learn from our history:

  • Was our duration estimate right or wrong?  Why?
  • Was our degree of difficulty estimate right or wrong?  Why?
  • What was our average time/page?
  • What went well?  Why?
  • What went badly?  Why?
  • What method or procedure changes could we make?  Why?

Reconstruction notice

This site is (slowly) being re-constructed.

If you click on a page and find no content -- don't worry, it will be there soon!

The menus give you an idea of what is coming to the site.

Thank you for your patience.

In the meantime you are welcome to contact me:

email-graphic

 

 

 

Joomlashack