Tech Word

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Friday, 20 March 2009

Lessons of the Square Watermelon

Posted on 11:40 by Unknown
Someone sent me an email containing more wisdom than I gained in all of my years of schooling:

Japanese grocery stores had a problem. They are much smaller than their U.S. counterparts and therefore don’t have room to waste. Watermelons, big and round, wasted a lot of space. Most people would simply tell the grocery stores that watermelons grow round and there is nothing that can be done about it. That is how the vast majority of people would respond. But some Japanese farmers took a different approach. If the supermarkets wanted a square watermelon, they asked themselves, “How can we provide one?” It wasn’t long before they invented the square watermelon.

The solution to the problem of round watermelons wasn’t nearly as difficult to solve for those who didn’t assume the problem was impossible to begin with and simply asked how it could be done. It turns out that all you need to do is place them into a square box when they are growing and the watermelon will take on the shape of the box.

This made the grocery stores happy and had the added benefit that it was much easier and cost effective to ship the watermelons. Consumers also loved them because they took less space in their refrigerators which are much smaller than those in the US meaning that the growers could charge a premium price for them.

What does this have do with anything besides square watermelons? There are a few lessons that can you can take away from this story which help you in all parts of your life. Here are a few of them:

Don’t Assume
The major problem was that most people had always seen round watermelons so they automatically assumed that square watermelons were impossible before even thinking about the question. Things that you have been doing a certain way your entire life have taken on the aura of the round watermelon and you likely don’t even take the time to consider if there is another way to do it. Breaking yourself from assuming this way can greatly improve your overall life as you are constantly looking for new and better ways to do things.

Question Habits
The best way to tackle these assumptions is to question your habits. If you can make an effort to question the way you do things on a consistent basis, you will find that you can continually improve the way that you live your life. Forming habits when they have been well thought out is usually a positive thing, but most of us have adopted our habits from various people and places without even thinking about them. It’s a never ending process, but by doing this, you can consistently strive toward making all aspects of your life more enjoyable instead of defaulting to what you have now.

Be Creative
When faced with a problem, be creative in looking for a solution. This often requires thinking outside the box. Most people who viewed this question likely thought they were being asked how they could genetically alter water melons to grow square which would be a much more difficult process to accomplish. By looking at the question from an alternative perspective, however, the solution was quite simple. Being creative and looking at things in different ways in all portions of your live will help you find solutions to many problems where others can’t see them.

Look for a Better Way
The square watermelon question was simply seeking a better and more convenient way to do something. The stores had flagged a problem they were having and asked if a solution was possible. It’s impossible to find a better way if you are never asking the question in the first place. Get into the habit of asking yourself, “Is there a better way I could be doing this?” and you will find there often is.

Impossibilities often aren’t. If you begin with the notion that something is impossible, then it obviously will be for you. If, on the other hand, you decide to see if something is possible or not, you will find out through trial and error. Take away the lessons from the square watermelons and apply them to all areas in your life (work, finances, relationships, etc) and you will find that by consistently applying them, you will constantly be improving all aspects of your life.

* * * * *

Let's look at how each of these five principles apply to our profession:

Don’t Assume

Technical writers constantly make assumptions about:
  • the types of documents to be produced: user guides, release notes, and so on
  • the content of these documents: the actual information contained in the files
  • the production of these documents: this includes how the information is gathered from various sources and the way the documents are actually assembled
However, for any given project, it is likely that:
  • some of the documents being produced are not required
  • documents that are required are not being produced: this includes not only the type of document (for example, a quick start or troubleshooting guide) but the actual file format: online help, HTML, PDF, TXT, RTF, and so on
  • the content is incomplete, inaccurate, incomprehensible or all three
  • the methods by which the documentation are created are not optimal: this includes the exclusion of key people who have real, practical knowledge of the product, for example, technical support staff, from the development process
Question Habits
Unless you are the very first technical writer at a new company, and are starting from a blank slate, you've inherited a documentation set that represents the sum total of all the habits and choices that preceded you. Some of these may have been good, but others may have been quite dreadful. They can range from having engineers pretending to be technical writers, to not having writers review each other's work. Your job is to continually have a fresh set of eyes and question everything, including the way you've done things. This can be challenging, but all rewarding things in life are.

Be Creative
The great myth of our time is that fictional writing is warm and creative, whereas technical writing is cold and mechanical, with no room for creativity. In fact, creativity is a key skill required not just of all writers, but of anyone in business today. Examples of technical communication creativity include:
  • developing visual, user-friendly quick start guides, where before there was just dry text
  • converting a confusing block of sentences into a table, list or diagram
  • rewriting an error message that identifies the problem and how to fix it using as few words as possible
  • writing helpful, succinct, on-screen instructions
  • reworking an index to include more of the terms a user would actually be searching on
Look for a Better Way
This ties in all the previous points. If you assume nothing, question previous habits, and are creative, the result will be that you found a better way to create the documentation, and in doing so improved the quality of it.

Better ways can include:
  • using a different tool
  • streamlining the review process
  • redesigning your templates
  • actually speaking with the end users to see what it is they want
There you have it - the only four lessons you'll ever need:
  • Don’t Assume
  • Question Habits
  • Be Creative
  • Look for a Better Way
Here endeth the lessons.
Read More
Posted in business, creativity | No comments

Tuesday, 3 March 2009

Virus'd!

Posted on 13:24 by Unknown
No, this article is not about how my computer has been infected. Many younger people today may find this hard to believe, but before there were computer viruses, there were biological ones.

A virus is a machine more perfect and efficient than anything mankind could manufacture. It is a difficult beast to describe; scientists aren't even sure whether it is "alive" in any sense of the word. That's because viruses contain genes but no cell structure or metabolism, considered critical to life.

Whatever viruses are, they have a somewhat poor reputation, because they have probably killed more people than all wars and murders combined; not millions, or even tens of millions, but hundreds of millions have been slain by something the poor victims couldn't even see.

Viruses come in essentially three different flavours: the good, the bad and the ugly, and the ugliest one of all is Ebola. This monster can kill within several days, and it does it in a most horrific way: it essentially liquefies your organs from the inside. Victims bleed to death from the inside out.

What's interesting is that Ebola, like all deadly viruses, does not actually intend to kill its host. It's simply making copies of itself, because that's what it is programmed to do. Essentially, it is trying to turn its host (a person) into a giant copy of itself. In the process, it destroys the host. Hence, their nasty reputation.

But what if you could make a good virus? In fact, such viruses have been developed. Years ago it was discovered that milkmaids who had been infected with the relatively mild cowpox virus were immune to the much deadlier smallpox virus. This led to smallpox vaccination. In fact, most vaccines today contain weakened versions of viruses that protect you against the nastier ones. In genetic medicine experiments, harmless viruses carry useful genes into cells. For example, scientists have tried treating a genetic disease by letting a virus insert a crucial gene into liver cells that protects against harmful cholesterol.

Therefore, we should not always fear the virus. In fact, we can learn much from it. Earlier I said how viruses are simply trying to make their hosts into copies of themselves. That is precisely what an information developer is trying to do to the reader. A successful information developer infects the host agent (the reader) with the knowledge already contained in the information developer's mind. In doing so, the developer is creating copying the information into the reader's brain. The more efficiently and accurately the information developer can do this, the better the infection.

And the best part is, that, unlike the Ebola virus, the reader's brain won't be liquefied in the process. Unless you are a really, really poor writer. Unfortunately, there's no vaccine for that.
Read More
Posted in medicine, science | No comments
Newer Posts Older Posts Home
Subscribe to: Comments (Atom)

Popular Posts

  • Six Things That Should Be Single Sourced
    Single-sourcing, as we all know, is the art and science of using a single repository of information to produce multiple outputs. Typical ex...
  • Interviewing and Dating: A Single Source Solution
    Last month, people celebrated "Valentine's Day", a day to celebrate romance and love, a day to be extra-nice to your partner, ...
  • The Power of Words
    There's nothing like an election to illustrate how powerful words are. Politicians, pundits, and the media use words to advance their ca...
  • The Governing Dynamics of Documentation
    Game theory is a specialized field of mathematics that analyzes choices and results in strategic situations, or games , as the players try t...
  • Why info systems fail
    If you only have time to read one news article today, read this one from the Financial Post. Don't leave IT to the techies - Three probl...
  • How to update a document - NOT!
    Canadian International Co-operation Minister Bev Oda needs to work on her document management skills. She hand wrote the word 'NOT'...
  • Publishing for Pollard
    Most of you probably have never heard of Jonathan Pollard, the American who has been languishing in prison since November 21, 1985, almost 2...
  • The Dynamic Blogger
    Some of you may have noticed the new look of this blog. It's a new Blogger feature called dynamic views . You can now choose how this bl...
  • Dude, where's my document?
    Try this experiment: Think of a printed guide you worked on. Find the source document from your current location. Make a minor change to the...
  • Security breach!
    It's always entertaining to read about non-lethal lapses in security at a major event. Remember the debacle at the 2010 Winter Olympics?...

Categories

  • art
  • autism
  • bad communication
  • business
  • career
  • cloud computing
  • computers
  • creativity
  • entertainment
  • finance
  • food
  • Google
  • history
  • interviewing
  • math
  • media
  • medicine
  • misc.
  • music
  • nature
  • news
  • philosophy
  • politics
  • quantum theory
  • religion
  • resume
  • resumes
  • science
  • security
  • simplicity
  • sport
  • technology
  • usability

Blog Archive

  • ►  2012 (9)
    • ►  September (1)
    • ►  August (1)
    • ►  July (1)
    • ►  April (2)
    • ►  March (2)
    • ►  February (2)
  • ►  2011 (36)
    • ►  December (2)
    • ►  November (2)
    • ►  October (6)
    • ►  September (2)
    • ►  August (4)
    • ►  July (5)
    • ►  June (3)
    • ►  May (6)
    • ►  April (2)
    • ►  February (3)
    • ►  January (1)
  • ►  2010 (47)
    • ►  December (3)
    • ►  November (6)
    • ►  October (4)
    • ►  September (2)
    • ►  August (1)
    • ►  July (2)
    • ►  June (2)
    • ►  May (3)
    • ►  April (5)
    • ►  March (11)
    • ►  February (7)
    • ►  January (1)
  • ▼  2009 (36)
    • ►  December (11)
    • ►  November (5)
    • ►  October (4)
    • ►  September (2)
    • ►  August (2)
    • ►  July (3)
    • ►  May (1)
    • ►  April (3)
    • ▼  March (2)
      • Lessons of the Square Watermelon
      • Virus'd!
    • ►  January (3)
  • ►  2008 (24)
    • ►  December (9)
    • ►  November (1)
    • ►  October (7)
    • ►  July (1)
    • ►  June (1)
    • ►  May (1)
    • ►  April (1)
    • ►  March (1)
    • ►  February (1)
    • ►  January (1)
  • ►  2007 (10)
    • ►  December (1)
    • ►  November (2)
    • ►  October (4)
    • ►  August (1)
    • ►  March (1)
    • ►  January (1)
  • ►  2006 (4)
    • ►  September (1)
    • ►  June (1)
    • ►  April (1)
    • ►  February (1)
  • ►  2005 (10)
    • ►  December (1)
    • ►  November (1)
    • ►  October (1)
    • ►  September (1)
    • ►  June (1)
    • ►  May (1)
    • ►  April (1)
    • ►  March (1)
    • ►  February (1)
    • ►  January (1)
  • ►  2004 (9)
    • ►  December (1)
    • ►  November (1)
    • ►  September (1)
    • ►  June (1)
    • ►  May (1)
    • ►  April (1)
    • ►  March (1)
    • ►  February (1)
    • ►  January (1)
  • ►  2003 (9)
    • ►  December (1)
    • ►  November (1)
    • ►  September (1)
    • ►  June (1)
    • ►  May (1)
    • ►  March (1)
    • ►  February (1)
    • ►  January (2)
  • ►  2002 (3)
    • ►  December (1)
    • ►  November (1)
    • ►  October (1)
Powered by Blogger.

About Me

Unknown
View my complete profile