Twitter Updates

Give Me Some Space (Between Words)

Sometimes just the smallest little change to an existing way of doing things can have enormous — and unexpected — positive consequences. Here's one of my favorite examples of this phenomenon.

One of the most significant but unheralded communications developments of the past 1,500 years is the adoption of spaces between words.

Notice the words you’re currently reading. They are separated by spaces, written in lower case letters, and easy to read. Prior to approximately the eighth century AD, however, Latin and Greek were written in capital letters in a “run on” fashion — that is, without spaces between the words. Here’s an example:

As you can see, this type of writing slows you down. In ancient times, though, Latin and Greek texts were almost always read out loud. (This method is known as “reading by ear.”) Ancient readers, sufficiently familiar with their own language, easily identified words by sound instead of sight, and had little difficulty. Thus, word-separating spaces were considered unnecessary.

Such familiarity wasn’t the case in later times. Eighth century AD priests, living at the periphery of the former Roman Empire, had a weaker grasp of Latin, and so couldn’t always determine where one word ended and the next one began when reading Mass. The priests solved this problem by inserting spaces between the words to serve as a recognition aid.

Over time, the addition of the spaces created an unexpected benefit: faster reading. That’s because if you can see the beginning and ending of a word, you'll recognize it more quickly; moreover, the brain can sight-read words in much less time than it takes to speak and hear them. By the twelfth century, most of the literate world had adopted spaces, and sight-reading became widespread.

Question to think about: Think of a current project you're working on. What can you do (in this project) that would be the equivalent of adding spaces? How might that make it better?

Roger - your postings on language innovation have me thinking about the invisible nature of "what if" thinking and the challenge of implementation.

Prior to reading your posts few would have thought to themselves, "look at those spaces between words! I wonder who came up with that!" Spacing is a great idea that is now invisible to modern readers.

Then I began to imagine all of the resistance to the creative solutions you've written about in language.

"Sure...anybody can read if you give them vowels. But isn't that just dumbing down language? In my day you had to figure out what word was intended by fully grasping the context! Kids today just read without thinking."

Or...

"I'm not so sure about those new fangled spaces between words. It seems like such a waste of papyri." So said the Six Sigma Scribe.

Not sure where I am headed with this comment but it is fun to imagine the grumbling that accompanied great ideas. And maybe it is is an encouragement for us to go for the same kind of creative solutions regardless of what others say.

Maybe what Mike is getting at is that it's not only enough to have an idea, brilliant that it might be. It needs to be protected from skeptics and championed all the way to extreme measures for it to see the light of day sometimes.

Jobs exist of the strength of what used to work so the people who occupy them often do their best to "hold on" to what was because that's how they're graded and rewarded. Innovation, even of the most obvious kind, is gutsy to do and often its only reward.

It didn't take me long to come up with "what in my experience is like a steady stream of words without spaces?" My RSS reader feels that way lots of the time. There is no break in the relentless supply of great ideas, articulate expressions and inspiring analogies. I've tried "mark as unread" in Bloglines but that just adds to the pressure in the steady stream of great stuff to read because the same postings are still sitting there in the reader. Last week I tried something new that 'gives me some space" between the postings. I emailed posts to myself that I want to think about some more, quote someday or link to in a future posting of mine. In my email client I set up a destination folder where these emails sit until I ponder them. After reading them, I delete or move them to a folder set up for each of my favorite bloggers. This post went into my "Roger von Oech" folder. It's a keeper. Using emails in this way gives me space to ponder slowly, delete at my own pace and find the useful ones again when I need it. It's too soon to determine if I'm "reading faster" as a result. If I am, there's a wonderful paradox in that: by giving myself the space to slow down, I sped up my blog reading.

Cam: People have been doing innovative things for many millennia. I find it inspiring to try and tease out what they may have been thinking when they tried something new.

Mike: What a great perspective: it's one thing to get the idea, and quite another to overcome the judgment and skepticism that kills many of them.

Valeria: On the other, if we went along with every new idea that came along, things would be chaotic. But you're right, most people tend to err on the side of caution.

John: Nice analogy to using this insight on the web!

Tom: What a great idea. I might try that filing system myself. It may not equate to "faster reading" but it might lead to "better comprehension." I agree with you: there is a never-ending stream of stuff coming at us in our RSS readers.

in the agile world we say taking the time to think speeds up projects.
By slowing down and think about th elast time we actually speeds up things.
Slowing down and think:
* A daily stand up: talking for 15 minutes a day with the team about
-What have I done yesterday
-What do I promisse to finish today
-Where do I need help
* a retrospective ever x weeks , when we have delivered a small piece of work.

* PairProgramming: looks like slower to deveoper something, but in reality speeds it up alot.

* doing automatic testing (TDD)
it is slower to develop, but it is actually faster because we think better about what we want to develop