13/1/20 ^^^Let's talk about documentation

I am going out for a late lunch.  So I'll make this real quick.

Start the documentation before even the organization starts:

• Best Practices
• Standard tools and methodologies
• Employees handbook
• Frequently asked questions
• Resources Portal
• Learning Management System
• Culture and Norms

This is part of Organizational Development with Human Resource being the subset.

Make them like Winning!!! format and *ma[d]e [] (them) available in the web or blogs.  Use my blog writing style with text, graphic and audio.

*  Fantastic Sarah.  You anticipated this huh?

Then end each topic with a 3 questions pop quiz.  They need to answer the quizzes before they can proceed to the next topic.  Therefore comprehension are measure[s] (measured) instantaneously. 

I am rusty in this department.  I left HR Consulting 20 years ago.  Consult with an LMS expert.

Information + Application = Learning

My material is ASTD standard.  If you enjoy learning from me the past 3 years, then use the same andragogy approach.

No need to reinvent the wheel.  Just ride on the present one and kaizen from there. 

Be mindful that we are training the Fringes and Bees, Borgs and Gayshas.  It should be as easy a[re] (as) taking a driver's licence in the USA.

Think that at best most of them are WhatsApp proficient.

The blog is a good engine.  I like it very much.

Then the hard copies follow Richard Templar's format but keep the book small and simple like these:

The style is technical writing but make it conversational with tables, graphs and pictures.

I think if you just follow my Buyers Beware!  tha[n] (that) is the gist of it.

My company is Simple Concept.  I make difficult things simple.  Not the other way around LOL.

Righto, from you response I think you are pretty excited about this little project.  You can be the Head of PMO here.  That way you have a say on the content and creativity part of the deliverable.

Documentation is a huge project.  Do it like an assembly line.  That way you have a sequence of roles working in a tag team.  For example Creative team may start, followed by Content Developer, followed by *Write[], followed by Graphic Artist and finally followed by the Editor.

* I see, you want to be one of the writer.  Jolly good Sarah.  That will be your legacy then.

This is a Skunkworks with 7 assembly lines.  Hence it could be the same resources working on one line after another or parallel lines working simultaneously.  Make s[o]re (sure) nothing more than the size of Al Araf 7:7.

The rationale is if I can manage the whole operation with the 36, that means that is an optimum number.  Otherwise chunk the project into small bites.

Gosh... I can go on and on with this project but I AM DAMN HUNGRY LOL.  I better go.  I think I covered the fundamentals.

Final word.  Don't make things complex.  If for example our values and beliefs can be presented in 3 slides (Sharudin Seven, Primal Blueprint 10 Laws and Musashi's 9 Precepts), then keep it that way.

Remember KEEP IT SIMPLE SARAH.

I gotta go baby, I am beginning to have a hard on talking about documentation. 

Later baby...

--------------------