Thursday, July 31, 2014

Drive quality and reduce waste with Plain English



I encourage people on my teams to use Plain English in all forms of communications.  This is especially  helpful in email but also in test plans, test cases, and defect records.  I include that advice in defect management and test case management guidelines.  Plain English works because it makes communication clear, accurate, and easy to understand.  This in turn improves decision support, business velocity, and  reduces faults.  It also reduces waste in the form of reading/re-reading and clarifying.  Plain English is not always easy but it is always worth it.  Make it a habit to help improve quality in your organization.

From the PlainEnglish.org How-to guide:
• Keep your sentences short
• Prefer active verbs
• Use 'you' and 'we'
• Use words that are appropriate for the reader
• Don't be afraid to give instructions
• Avoid nominalisations (i.e., adding suffixes to nouns.  Example: gearhead, Parrothead, Deadhead).
• Use lists where appropriate

Advantages:
• it is faster to write;
• it is faster to read; and
• you get your message across more often, more easily and in a friendlier way.

Saturday, July 26, 2014

The Art of Quality


Quality Minute: 5S

​5S is a method of creating a clean and orderly work environment that makes waste and faults visible.
5S originated as a Just In Time manufacturing technique.  It can also be applied to knowledge oriented work such as in the software industry.  Google "5S"​​ to learn more.
The 5S's translate as follows:
  • Seiri;           Sort
  • Seiton;        Straighten, Simplify
  • Seiso;         Shine, Scrub
  • Seiketsu;     Standardize, stabilize
  • Shitsuke;     Sustain, self discipline

Quality Minute

Some years ago, we were discussing how to raise basic quality knowledge at our organization.  We wanted to make it super easy for people.  Our prototype was a collection of short email messages called the Quality Minute.  One Quality Minute was sent per week and could be read in about a minute.  The prototype was a hit.  Proof of its value came unexpectedly one day from Marketing.  In a new feature planning session, a Marketing Manager asked if the new feature would contribute to technical debt as described in a recent Quality Minute.
I lost those emails somewhere along the line.  They're easy to reproduce though and this blog is a good place to capture and share.