Migrating to my other blog

I will continue blogging, but on another platform: Free the Random Thoughts.

I have been running the two blogs in parallel with different themes:

• This blog: Technical Commuication
• The other blog: Life in Taipei + personal interests

At first it looked like the two could safely co-exist. But then I realized most of my interests are concentrated in either technology or communication (including miscommunication). The difference between the two blogs quickly became blurry.

Despite being a technical writer for several years, I haven't much thought about blogging on technical communication area, until I had started this blog. Probably it was because of my fixed idea that writing about one's job is boring. But talking about one's job (boring, end of discussion) and writing about it are two different issues and I have found the latter to be highly fulfilling, both for myself and hopefully my readers.

Since I spend at least eight hours during weekdays doing or thinking technical communication-related stuff, I found that my personal life (= life outside my workplace) already revolved around the big two concept: technology and communication. I decided to shift my blogging to more technical communication oriented style.

Also, I found that writing at the intersection of two seemingly separated concept (such as advertisement and technology) is more interesting than sticking inside one. I decided to fuse my interest under one umbrella topic (technical communication in Asia) to see what chemical reaction will occur in my blog.

Then why move to the other blog, not the other way around? The simple answer is that the other blog has been running for years with a small but (hopefully) growing number of readers. As a blogger, I am also interested in establishing my personal branding, if that is possible.

I would like to express sincere gratitude to people who have been reading this blog. Like I mentioned above, the blogging continues and will even be enhanced, adding a twist of cultural (mis)understanding and more humor, if possible.

All existing content in this blog will remain as they are. From now on, see you at Free the Random Thoughts.

We are all becoming editors - really?

Liz Danzico at Interactions Magazine says we are all becoming editors.

As the Information Age barrels forward, a new role has emerged. While new platforms-from Facebook to Twitter to Tumblr-have turned consumers into creators, they’ve given way to more writers, more content, and (as we painfully know) more choices. But there’s something else. Content creators are not passing content through traditional editorial channels, nor should they be. The cost of filtering content has passed from the pocket of the publisher way downstream to the pocket of the consumer. As a result, we as consumers are left in the position of having to decide what is worth our time. Whom should we pay attention to? Whom should we ignore? Who decides which content is exceptional and what to tune out?

Whether we like it or not, we’ve been given a new role. This promotion came about without warning, without training, without org charts or manuals. In addition to our current positions, let’s face it, now we’re all “editors.”

I have always thought information overload is making us harsher critics because we are constantly exposed to the best in any area of expertise, which explains why we do not feel any better about ourselves by knowing more. Even when we think of something totally mundane like making a gun using redundant rubber bands, a quick search on Youtube reveals something like this:


I agree with the idea of ourselves taking the editor's role, if it means "screening others." Filtering out redundant information, or picking up the essential part, is the first thing we do when we meet a new source of information. That is why almost everybody encourages writing "scannable" resumé and using tags for web pages to make sure a piece of information stands out.

But are we getting any better at editing in a broader context, which is editing ourselves? Or to rephrase it, becoming a better critic of our own work? Penelope Trunk (again) lists the reason why she works with an editor for whatever she writes in public:

• Start strong - cut boring introduction
• Be short - and be brave
• Have a genuine connection - write stuff that matters to the readers
• Be passionate - write stuff that matters to you
• Have one good piece of research - back your idea up

They have one thing in common: difficult to do on our own. Even the "be passionate" advice tend to be ignored under the pressure to write something, or mistaking blog as a substitute of diary. I do not think the onslaught of information helps; it teaches us to be hard on others but it doesn't force ourselves to be more disciplined. I might even think that we are getting sloppy at editing ourselves because everything is becoming easier. For example, I do believe we will be more careful and disciplined if we are forced to write on a typewriter.

Therefore my take on the editing issue is that we all need editors, or editing skills, more than ever. Getting better at judging others doesn't mean we know more about ourselves.

Google is going to own total user experience?

MG Siegler disses Google for announcing its own Android phone merely a couple months later Motorola brought the Droid phone out, saying Google is undermining their reputation and killing each other inside its ecosystem rather than shooting iPhone off the top spot. But he still thinks in the end Google had made the right decision. Why?

The single biggest reason that the iPhone is great is because Apple is in nearly complete control of it. In fact, the only thing they’re not in control of, AT&T’s network, is its greatest weakness. Before the iPhone, no device manufacturer, let alone software manufacturer, had anywhere near the type of control that Apple does over a mobile device. With Nexus One, Google is moving in that direction too. And that’s the right call.

We have seen outrageous success stories of companies having complete control of their device's hardware and software.

• Nintendo has created Wii with its revolutionary motion control but everybody agrees that they couldn't have pulled off the game so brilliantly without the bundled killer title, Wii Sports. 
• Amazon is enjoying a great success with its Kindle e-reader. Again, they own the hardware, software, and even the network - downloading is allowed only through Amazon's proprietary channel.
  

On the other hand, we have seen companies which made fantastical flops even with total control. What the following two companies have in common: bureaucratized corporate structure and inconsistent decision making.

• Microsoft creating Zune
• Sony creating Playstation 3 (compared to Wii and Playstation 2)

Drawing lessons from the above-mentioned examples, it looks like the shortcut to having a revolutionary hardware is to:

1. Have control on both hardware and software.
2. Have integrity in what you do.

Google has it both. Although they are technically not in charge of the hardware (HTC is), the two have worked closely from the dawn of the Android OS (HTC Dream was the world's first Android smartphone). In addition, there are only three decision makers in Google - Schmidt, Larry, Sergey - with two of them (the founders) having greater power to veto decisions made against their will.

Therefore my verdict is that the new Googlephone will not suck, in fact it should be great, and I will be having one as soon as it comes out legally or illegally. Sometimes it really sucks that the latest mobile phones do not always reach Taiwan immediately, even though they are likely manufactured by a Taiwanese company.

No one reads manual

In the thoughtful blog I'd Rather Be Writing, Tom Johnson says:

Not many (technical) writers consider the positive aspects of users not reading the manual. If you do a lousy job on the manual, or if some SME (Subject Matter Expert) discovers typos and inaccuracies, you can just laugh it off by saying no one really reads the manual anyway.

But consider the opposite scenario where everyone reads the manual. Is this a scenario you want? No. Because if everyone has to read the manual to figure out the product, it means the product is so unintuitive and user hostile it’s probably going to tank on the market and you’ll soon be out of a job anyway.

Also, if so many people are consulting the help, you probably aren’t contributing enough on the design/usability side of your technical writing role. Remember that you’re part of a team building a solution to a problem. You want the user interface to be simple and intuitive enough to not require a manual. So if only 10 percent have to consult the manual to figure out the product, that’s a good thing.

It is an eternal dilemma for technical writers. The better we are at our job, we have less to show as the result of our work. How? Let's take a look at the process of writing a user manual for example.

1. Start writing.
2. See potential pitfalls users might fall into.
3. Write about how to avoid them.
   
   That's it, if our job is to "write", it ends here. It's probably 90% of the cases. But as Tom says above, we are part of a team trying to present better "solutions" to the users, right? So if we really care about our goal and users, we should continue our work like this.
   
   
4. Go tell the developer that the product sucks can transform into the next iPhone and you know how.
5. Work with him to fix the product.
6. Product becomes one step closer to iPhone, users have thinner manual, less dead tree consumed.
   

(In reality things go differently, especially when we use the deleted word which is also 90% of the cases, but that's the subject for another entry.)

Sounds like a win-win situation for everybody, except for technical writers. Like any other writers, we want our works to be read. Just look for the technical writer in your office (yes, that grumpy guy that you tried not to notice subconsciously) and tell him that you think he writes really well. You just got a loyal buddy (though it might be a creepy one-way affair, it won't hurt to get one).
Note: yours truly does not fall into this category :) But I appreciate encouragement.

Good technical writers switch their mindset/career so that they become "solution providers" than mere writers - as long as the users are happy, they are happy. Some funnel their creative energy into another media (such as a blog on technical communication :). Some solace themselves by looking up to fellow martyrs; look at the cops, what they try to achieve is a society that does not need them. We constantly battle this internal conflict: no one wants to read what we write, including ourselves.

If there is someone reading this entry considering technical writer as a writing gig, especially a creative one, be ware: you need to redefine your idea of creativity--providing better solution is nothing but creative work, for example. If you think otherwise, name any instruction manual that won a Pulitzer. There are award-winning books that have been used as instruction manuals, such as From Beirut to Jerusalem by Thomas Friedman. But it's not going to work the other way around.

Social media harassment from Scheduletwitterposts.com and Twitter scheduling service

I signed up for scheduletwitterposts, a Twitter update service, and paid a minor but very irritating price for it. Without letting me know, they tweeted a post advertising themselves under my name (see the below post). I forbid them from accessing my Twitter account, and issued a statement telling my friends that the last post was a hoax (see the top post).*

* I made a mistake of including their URL again - any public relation is a good public relation, especially to a budding startup. Also, in their marketing pitch "Now I can tweet even I am asleep, so awesome!!!" there are three too many exclamation marks. And the word awesome is redundant. And all the rest.

Now that "create once, broadcast multiple times" is getting much easier thanks to these aggregation services, we need to be careful of being over-generous with our account name and password. This entire blog entry is for warning everybody of scheduletwitterposts and nasty tactics (+ my own stupidity).

That problematic company allow us to schedule Twitter postings, as its name suggests. That function itself worked fine (though you cannot edit a queued Twitter posting). But if you want a scheduled broadcasting, I recommend using Hootsuite instead. I am kicking myself over why I did not use Hootsuite in the first place. Hootsuite's benefit includes:

• Editable queued Twitter posts
• Create once, broadcast in multiple formats including Twitter, Facebook, and Linkedin
• Tabbed screen works also for Twitter/Facebook update viewing application
• Absolutely free and web-based
• URL shortening service included (you can use it for other places!)
  

Re-releasing books online

Kevin Kelly has been releasing contents of his book written a decade ago on his website as a series of blog postings.

The book itself has always been available online as free, so he is not offering it ( = paid content) free on the web for the first time. The difference between the past online offerings (PDF, website...) and this case is that as a blog, he is encouraging readers to participate in making it better.

There are many places in New Rules that I know could be updated with more current examples: I'll leave those to you, the collective readers, to do -- as I say in the book, no one is as smart as everyone.

Kevin Kelly is expecting more of an update rather than error corrections, as he says that the original book, written 10 years ago (a lifetime in the age of Internet), is "as pertinent today as a decade ago." I am wondering, what if an author, especially non-fiction writer, posts his earlier works on the web and let everybody scrutinize their contents? Did his message stood the test of time? Or if the author has changed his mind, found better ideas, admitted his mistakes, he can post them too alongside his readers.

Most authors won't touch that subject (that's why some of them keep churning out the book version of the X-men films), but I am thinking maybe that is the only way to let a book live its life for more than a couple of years. Sadly, nowadays whenever I buy any book dealing with current affairs, the first thing I do is to check the last publication date.

• 2009: Certified fresh. Might be sour.
  
• 2008: Ripe.
• 2007: Getting dry, but sometimes that's not a bad taste either.
• 2006: Need to check the smell before trying it out. (Won't buy it unless the Search Inside! option is not available in Amazon)
  
• 2005 and before: Certified rotten.

I think I am not going to change my habit, like, forever. We have electronic readers and online subscriptions: why not go one more step and allow live-update publications with user inputs? It's not just about data corrections. One of my favorite books of the past decade is What Should I Do With My Life? by Po Bronson. It is a fantastic collection of stories from people who were trying to find a path when they were lost without direction in their lives. The first thing I thought when I finished reading the book, and what I still do, is "I want to read more." If an "update" service becomes standard, my wishes might be met more easily from help both by the author and the readers who themselves have stories to tell.*

* There is a famous author who is already trying the "update" approach, although still based on printed publication: it is Thomas L. Friedman with his recent two books.

• The World Is Flat
• Hot, Flat, and Crowded
  

Microsoft's lost decade

CrunchGear published the biggest product flops of the decade (according to them). Unsurprisingly, Windows Vista OS won the cup. I am actually feeling sorry for Vista and its development team after so many bashing they have had to suffer. So here is my message to those hard-working people. Go to hell, then you'll be able to rest in peace.

The article has kinder words about Microsoft itself:

Microsoft has had a hard decade. They made billions, sure, but they haven’t led in mindshare since Windows NT. Geeks flocked to Linux in the early aughts and LAMP now rules the roost when it comes to web servers. Their mobile offerings are roundly and regularly panned and their incremental fixes to products have frustrated users.

They definitely had the worst decade in their entire history. There is a good news, though; at the end of 2019, the first decade of the 21st century would be regarded as one of the better era for them -- compared to this decade which has just started. One of my favorite bloggers, Dan Kogai, shares similar sentiment (in Japanese) that Microsoft did suck great in the past year, if not ten. His idea is that it was about their marketing mindset, not necessarily about their products.

(Translated from the original website) Considering how they are marketing, not how they developed, Windows 7 (such as preparing the totally redundant 32bit version), I cannot say Microsoft really understands what fundamentally is wrong with them. It reminds me of the Japanese society in the 90s, the so-called "lost decade." Worried people just stood by, watching the ongoing crisis pretending things would go back to "normal" soon. I hope Microsoft will not fall into the same trap as Japan did.

I think Microsoft has already accomplished its mission: to bring computers to every household. The problem is that they are still clinging to the same mission, trying to believe they are the challengers broadening the technological horizon for the masses. We are already enlightened, Microsoft. We do owe you a big deal, but we live in a different world. Why don't you go look for something else?

Note: This banner is on the Official Windows Vista Home Page. Who said Microsoft doesn't have a sense of humor?

From private to public

Eric Schonfeld declares in TechCruch that now we online-nomads live celebrity public life, revealing our private and social life to the public's eye, and denying that fact has no point at all. He is spot-on.

It takes some getting used to the idea of living in public. As I discussed several hours ago with Andrew Keen, in public on Twitter, instead of making the private public, we will make the public private.” When public is the default, you deliberately select what to keep private instead of the other way around.

It’s not that privacy disappears. But it becomes more a matter of emphasis and a conscious decision.

Now it is getting more clear to me why folks in Facebook decided to take a gamble by making all user information public by default. They knew we as users were already accustomed to the public life. Some people understandably got infuriated, but I think this time Facebook will win. After all, they created Facebook in the first place, so they must be running ahead of most of us when it comes to understanding what social media and its trend are about.

I also see others signs of this "from privacy to public" trend affecting our life--we are getting used to it.

• A famous blogger describes her private life in her blog as-a-matter-of-factly and readers (including myself) admire her because of, not in spite of
  
• Keeping in touch with your ex-spouse-girlfriend-colleagues on Facebook, but not on offline, is getting norm
• Twitter, of course, makes everything we say public by default

There were days that we had to work our ass off to show part of ourselves to the world. No more. What needs work from now is to keep our privacy. Another TechCrunch article suggested a gimmick that perfectly suits this trend: Web2.0 Suicide Machine. It's job is to eliminate your profile from social media, notably Facebook and Twitter.

The interesting fact, according to the Web2.0 Suicide Machine team, is that it takes nearly 10 hours to delete yourself from the public's eyes. Which is a great amount of work that will never be complete, since Facebook is notorious for keeping its user data to themselves.

Considering our amazing adaptability, we might eventually (or already) find a way to live as public figures. Will the celebrity tabloid go away, because they are no more different than us? Will we be having better/worse online dating because the "screening" process works much better thanks to the past history records?

Apple tablet: more than a tablet

No more than a week passes without seeing rumors of the coming Apple tablet device. Some say it is going to save the media from the doldrums they are in, some say Amazon Kindle and its competitors will all be doomed, realizing they were just frogs in slow-boiling water along the way. And yet some say it's yet another tablet device, nothing more.

I agree with this TechCrunch article.

Conventional wisdom suggests that Apple will not be able to succeed where so many others have failed. But Apple makes billions defying conventional wisdom.

 As for me, I vowed I will stick with Thinkpad through the rest of my life, until a couple of years ago. And here I am typing this entry on my new MacBook Pro. I love it as much as my first Thinkpad, 535. It's not that Thinkpad had lost its appeal (it did a bit, though) nor Windows OS is sucking everybody down. Apple makes awesome products, that's it.

So what will the new tablet be? My prediction is that Apple will come with a big trick or two, especially in the application area. It's not the CPU horsepower or battery time (which even the latest MacBook sucks). It's the usage.

iPod taught us that we can bring the entire jukebox on the road. iPhone finally showed what that PDA/Palm potential was about. The tablet might not be the "third revolution", but that's pointless - it's about making us realize a new way of re-framing our digital life. Even the supposedly failed Apple TV showed the glimpse of life without traditional TV (another TechCrunch article says it will do that, after all).

We are waiting for Apple to make the world "tablet" sexy for the first time in history, free from being associated with Charlton Heston. Apple's supposedly competitors are doing that too, I guess.

How to be a better blogger

Penelope Trunk, one of my favorite bloggers, held a webinar (web + seminar) on her 3rd startup, Brazen Careerist. becoming a better blogger. The following five points were the key messages, followed by her summary and my comments.


Have a topic.
Penelope: Topic is a contract between readers. Surprise them sometimes, but keep the promise as much as you can.

I reluctantly agree with Penelope. Although I like my aimless writing style, I am also learning that it does not bring me too far as a writer. I have two blogs: this, and a Typepad blog. This blog has a topic: technical communication. The other one doesn't. But it is the other blog I have more fun writing. It is a mashup of everything that stimulated my curiosity in my life. And yet the word "everything" suggests that I cannot describe what that blog is about. It is more of an excuse for not having a topic.
I don't think we should force ourselves to limit the blogging topic to one or two categories. Rather, we can re-read what we have written to find an underlying theme that constantly emerges, and make a topic out of it.


Write at the edge of the topic.
Penelope: Don't write the obvious (such as 5 ways to screw your design). Write something about the intersection between topics you are familiar with. Whatever is mainstream, it is already done.

Learn.
Penelope: No one likes know-at-all. Write what you have discovered. If you don't, it gets boring.

"Write what you know" used to be the mantra back in our school days and in our worklife. It does not work anymore, at least in blogging, because no one cares about what we already know (even us) - it's all there in Wikipedia. The act of writing is for the author, but the manuscript ultimately belongs to the readers. We cannot bore them.
The new mantra should be "Write what only you can." It is not about making things up: it is about pushing ourselves out of our comfort zone and write about something new as we explore a new territory, such as urban life + gardening. Or Geisha + Steampunk. I don't know.



Be interesting and short.
Penelope: Anything more than 600 words is over-indulgent.

I checked the word count; it has already surpassed 700. Over-indulgent. I dodge this accusation by pretending that the Q&A list tucked behind the main text body should be treated as a pseudo-separate entry. It's optional. How is that?

You have to care.
Penelope: About your topic/community. Write with the community in your mind. Remember, a blog is a conversation.

Am I caring? Am I engaged in a conversation? No. So far, my blog consists mainly of my monologue. If the subject is aptly defined, that works.


 -------------- The Q&A session --------------------

Q: What about Pioneer Woman? Boing Boing? They don't seem to have topic.
A: Pioneer Woman is HOUSEWIFE PORN. (Isn't that a topic?) Many topicless blog started at the early age of blogging. Nowadays you won't get traction being topicless.

Q: What if I cannot find a good topic?
A: Write what you are curious about. You will naturally hit a topic.

Q: Isn't topic limiting?
A: No. Look at how much stuff I, Boing Boing, TechCrunch can put in.

Q: What is the hook to keep people coming?
A: Be honest. Trust who you are (no matter how messy your life looks) and write about things that are bothering you.

Q: How can I avoid being boring?
A: Think of what you say at a cocktail party.

Q: How can you learn while showing yourself as know-it-all?
A: Nobody cares what you know.

Q: How should I promote my blog?
A: (Ryan Paugh) You really need to reach out to other people on the blog. Get involved in a community. We have seen great writers who did not reach out to many people thus did not gain many readers, but saw that situation change when they started being involved in Brazen Careerist.

Q: How do I know I am doing well?
A: Don't use the traffic as the sign. Good signs are: Do you keep going? Did you get a job?

Q: What if you hit a wall?
A: Write! Be an adult, get up every day, do it! Force yourself to sit down!

Q: What if I want to take back what I have written?
A: Why would you do so? Learn from your own stupidity!

Q: Can I write stream of conscience?
A: No, you need to edit heavily. I edit several times to make it a "good" stream of conscience.

Reflections on my growth as a blogger

It has been almost three months since I have started this Technical Communication blog. I have been wondering what exactly I am supposed to write here, thinking while writing all along. I would like to take a moment of reflection through having a small Q&A session with myself. To view the evolution of this blog from the visual design point of view, see this entry.

Each question starts with: "Does each of my blog entries..."

Has interesting title which attracts readers?

I don't think so. For most of the entries, titles are something that is slapped at the very beginning of the drafting process. And I admit it is the most inappropriate time to name an article - the first rule of blogging is to name the title at the end. The second rule of blogging is to name the title at the END.
I checked the title of this entry, "Reflections on my growth as a blogger" which was of course there from the beginning. Not particularly interesting, but should be fine for readers looking for a lifehack-type entries.

Follows standards of professional English?

Being a technical writer with four years of experience under my belt, I proudly answer: I have been doing what I could do ( = No. Obviously). The built-in spell checker in Blogger has been my single best ally (and archenemy) so far. I haven't paid enough attention to the rewriting/editing process, which is supposed to be the real writing stage following the brainstorming stage under the name of first drafting.

Addresses all the criteria of the given topic?

Again, no. I tend to focus on the subject which interests me most, not paying enough attention to the criteria outside that narrow scope. I have found that I can be focused when the topic is presented beforehand in small chunks (like in this entry). Probably from now on, I should list all the criteria beforehand and make them as a list or subheadings.

Incorporates hyperlinks to additional sources appropriately?

Finally a question that I can answer yes came in. I believe I have kept a reasonable record of incorporating hyperlinks for both related entries in this blog and web pages in general. I think I can site additional sources more often than I had done, not to make my entries more "authentic" (though I cannot deny it) but to force myself to learn more about the topic by looking for those information.

Uses images appropriately to illustrate and add visual design appeal?

The design appeal...I haven't paid much attention to this area. As previously mentioned, much of my design work consisted of selecting different template for the blog and embedding images and videos in the entries. Advanced visual editing such as adding visual elements and modifying CSS was nonexistent.
Does visual design matters for a blog which is supposed to be the outlet for my voice? Absolutely yes. A blog is the place to express my whole self, not just texts; ignoring visual aspects of it is like walking blindsighted.

Gives consideration to the (copy)rights attached to any images used?

For this blog, I have been careful not to violate any terms of usage for copyrighted images. I used my own images (photos and screen snapshots) whenever possible, and for copyrighted photos I always mentioned clearly where they were from. For my other (casual) blog, not so much...

Shows evidence of my application of information learned from my readings?

My answer to this question is similar to that for the "criteria" question above; yes, for subjects I was interested in. I am not sure if I should show my application of information which I did not digest enough. While organizing and writing entries this blog belongs to me; however, once an entry is published, it belongs to the readers. I think I can safely omit half-baked applications from the final draft.

Includes references (via quotes or hyperlinks) to additional information?

Yes, I have tried to include quotes whenever I found a good passage. Hyperlinks are better for leading the readers to explore other materials on his own, but if it is appropriate to stay him attached to this blog or to point out the most important part in the additional information, quotes have worked better. No I didn't use quotes to jack up the amount of texts. At least not all the time.

Includes original thought?

This is the area where I aspired to be good, if not great. I have always tried to find my own point of view for a given topic and express it clearly and succintly. But I must admit that probably the person who most benefited from this attitude is myself. By following the weak but almost tangible thread of thinking, I have understood far more about my thinking and interest than I had expected. Adding another layer of self-knowledge has an addictive effect.


Additional thoughts...

Writing is almost equal to (self) discovery and this blog has taught me more about that simple truth than my other blog, probably because I had to write longer and more in-depth articles. Pushing myself to think hard was painful at times, but the result was well worth it. A blog, especially a technical blog like this one, is always a part of the author's portfolio not because the blog teaches the readers about specific subjects but because the blog reveals who the author is.
One of my favorite bloggers, Penelope Trunk at Brazen Careerist says blogging is one of the most important tool one can master as a professional. I wholeheartedly agree.

Proposal for defero: consulting on new media

I have done a consulting project for a media company, defero (small d, yes). I will chronicle how the project started and proceeded in today's entry. Here is the outline.

1. Understanding what defero is about and its objectives
2. Defining the platform for delivering the project
3. Defining the suggestions
4. Building the platform
5. Filling the suggestions
6. Afterthought
   

Understanding what defero is about and its objectives

defero is a startup communications firm made up of individuals from "old media" (journalism, TV, publishing...) who are looking to use their skills in the 2.0 world to which they are digital immigrants. In fact, all they have at this moment is the company name. They do not have corporate identity, not even a website yet.

Defero needed a proposal for how they can launch their new company in mid-2010 and utilize a wide range of social media - from the obvious (a website) to wikis, podcasts, blogs - and perhaps even into less established platforms such as social networks.

What I needed to do was creating a convincing strategies for them to "win" the bloody 2.0 media wars by using the very same tools that drove their old industries to near-extinction.

Defining the platform for delivering the project

I was supposed to have a variety of choice for the method of delivery for the strategic planning, but in this case there was only one option in my head: to use a Web2.0 armored website. What is the point of encouraging people on the fence to jump on the new technology bandwagon without using the very "new technology" as the delivery medium?

In the old world (or old media for my client) the consultant and the client sat facing each other, being in the same environment but living in different worlds. We no longer live in that era. The consultant and the client sit side by side, using the same tools and watching over each others' shoulder.

Members of defero needed to learn the Web2.0 ropes from the scratch. Accessing the strategies in a modern website would be the beginning. Therefore, I decided to create a website (almost) dedicated to the defero project. My existing websites comprised of blogs and portfolios; not exactly suitable for convincing defero.

To create an effective website without wasting spending too much time in DreamWeaver, I picked up a free web-hosting framework, Google Sites. I had already created a website on that platform and it worked flawlessly (functionally, not necessary aesthetically). Its development process was also documented here.

Defining the suggestions

So, what would the suggestions be? Simply teach them the tricks of using Web2.0 tools (Twitter, Youtube, Facebook...) in exchange for a hefty (in my imaginations) consultation fee? After all, isn't that what everybody is doing these days? Teach the clients How, but never Why, because the consultants do not know any better.

That would have been acceptable, but never effective. I could do little more than making Wikipedia entries visually noisy. Something more than that, something that goes beyond Web 2.0 was necessary. This was also an issue that was bugging me whenever I thought about the whole Web 2.0 promise and its real effect on our economy and culture. Where should we go from there?

I remembered writing my opinions about the post-2.0 era and looked it up. A paragraph hooked my attention: I wrote this paragraph not only as my observation but also as a question to myself.

Free is the beginning and the end: What happened to the "how to make money" discussion? None of the social networks are charging money to users who only access to basic functionality. They charge money to users who want to do something extra; in other words, the "collect money from everybody (eventually)" mantra has been replaced by "collect money from heavy users (encourage everybody to become them, eventually)."

I decided to expand my suggestions for defero from the monetizing point. We all blindly accept that things will remain free for the foreseeable future. Is that so? We can do better than that (after all, we still need to pay for our living expenses). I myself particularly do not support paying scheme (my news subscription always occurs on Google News free of charge) but wanted to explore the possibilities.

Building the platform

Building the website nowadays starts from selecting online templates rather than holding a pencil and an open sketchpad. I know it is a cop-out, but for this project what mattered was effectiveness, not originality...

The Google Site had several business-like templates including the Professional Site Template which I eventually chose. It had a classic sidebar structure with various "widgets" for me to play with: testimonials, recent updates, calendar, search, RSS sindication, and download corner.

Visually, I stripped most of its color variations which was grabbing too much attention for my taste. I added my own banner and tweaked some of the fonts and page structure.

Then I modified the texts not directly related to the proposal for defero: company information, staff information, recent announcements, testimonials, an educational video, and calendar. The "entry" to the proposal was ready.

Filling the suggestions

Now, the meaty part. I have scribbled down my thoughts into a text file and organized them: soon it became apparent that I was delivering not only as a presentation but also a story that starts from the old media era, goes through the current situation and extends into the future. Forcing the defero members to read the entire story at once is going to be a tough ordeal, and also it was so Web 1.0. Separating the proposal into two parts was the logical conclusion: the summary and the details.

I usually outlines my thought in a presentation file. Since it looked also fine as a summary, I decided to refine it and embed it into the website as a starting point. The clients would first view the presentation file to grasp the higher level concept, and then can go down into more details described elsewhere in the web.

Fortunately, Google Site works quite well with embedded versions of Google Docs presentations, complete with playback controls (a trick I learned when building my previous website). The summary presentation, shown below, was embedded in the introduction page of the proposal.


I built the rest of the details into the subpages below the introduction. Using real-life examples and articles from the web, I focused on summarizing the concept for easy understanding rather than showcasing how to use the tools by themselves.

Afterthought

The process was hugely rewarding because I have found what I was really thinking regarding the Web 2.0 monetizing topic during the drafting stage. I hope my learning process would also be communicated to the clients. Below are other findings from this project:

• Shaping an existing template into my own taste was fun and I was quite satisfied with the result. A well-designed template works reasonably well even when it is being tweaked many times.
• Separating the proposal into two stages (summary presentation and detailed pages) also worked effectively, at least for me. For strategical theme, grasping higher concept at early stages is critical for reducing misunderstandings and I think I will be using this technique for similar projects from now.
• I could have stepped deeper into suggesting visual designs for defero. Designs are such a vital part of a company's identity, my proposal might have not been taken by them but it should have shown them one possibility of their future. Although getting into too much details has the risk of losing the overall perspective, having a concrete example might have worked well for further discussions and inspirations.
  

Project Collaboration: Using Google Wave

My Grad School classmate Lauren Rodan thought of collaboratively writing on Google Wave, and I jumped the wagon. The result is embedded at the bottom of this entry. Unfortunately you must have a Google Wave account to view it properly and there aren't too many people with a Wave account now, so please view the pasted transcript and imagine what it looks like.

When I started to use Google Wave (less than a week ago) I felt like I was using a glorified chat. But once we started the collaboration writing, it worked more like a face-to-face conversation than a cramped thread of aimless thoughts. What is shown below is an edited version so the real interaction went a bit more chaotically - the original colored thread looked like a piece of lego building rather than layered conversation we see here. But I believe we did generate a coherent piece of thought.

So, is Wave an effective tool for collaboration? Yes. And probably not only for collaboration. We could express ourselves freely without getting derailed from the topic. And the result I believe is greater than the sum of our individual thoughts. Both of us found interesting and refreshing perspectives in each other. Of course, proper initiative (Lauren) and mutual respect made the process successful but what made Wave special was that it stayed in the background all the time, never interrupting the writing process. Google Wave might be a revolutionary tool but no matter how big its potential is, it is still a tool that helps us do what we want. It was an extremely useful, transparent helping hand. I am glad Google and its engineers understand this point well (as opposed to... let's say MacroHard).

The transcript:

Conversation color-coded as follows:
Lauren
Isao
PROJECT COLLABORATION

• Collaboration was not "required" as part of the assignment - Did you collaborate with anyone else on the team? Whether you did or not, why?

I did not have the chance to collaborate with anyone else on the team. I made an attempt to do so by sharing a logo, but I did not receive any comments on it. I misunderstood Lauren's intention as a pure example, not an opportunity to collaborate. I got too used to think in "solo" mode (though the professor encourged collaboration all along) I think people may have been so far along with their projects at that point that my logo did not fit into their plans. I agree on this point, and I am also thinking - maybe a majority of us work in independent work style? At least I am. Personally, I am an independent worker. But part of the reason I appreciate the program I am in so much is that it takes me out of my comfort zone. I have had to collaborate with my classmates, people I've never met, online. It is a great challenge. I regret that this project did not lend itself to that kind of collaboration. Maybe collaboration is something that can become a course on its own. It is such a huge thing. Isao, I think it should be part of every course. I think the course was built so that students can choose either or not to collaborate. To facilitate collaboration more, I think the course can even force students to work together. Unless the students know each other from past semesters, getting to know each other itself usually take some time, and one semester only has 15 weeks - a "pushing" mechanism might work. I'm not sure I agree with you on the collaboration front. I don't think we have to know each other. The thing that gets us talking and working together is the fact that we are all studying the same topics, and we more or less all have similar (or related) interests. We do have similar interests - but the working or studying style might differ a lot. I see you are more comfortable taking initiative and collaborating and I am on the opposite side of the spectrum - self-starting and prefer to complete things on my own. I see what you mean. The funny thing is I am more like you in real life - independent and prefer to work on my own. Taking a course online makes me different for some reason. The course topic unites us students all, but collaboration is about our style (or even personalities) and an encouragement can work well, otherwise we tend to fall back on our favorite learning (or working) styles.The way I feel about collaboration in distance learning is this - if I didn't want to be involved in a learning environment (which I define as one of interaction with professors and students alike), I could have just bought a load of books and not taken any classes. I think collaboration is important in higher education. I learn a lot from my classmates. As Lauren pointed out, learning materials are everywhere. The key to attend a grad school is to be with people with similar goals and interact with them. Now, if this was a non-distance learning course, the fact that students sit together naturally creates friendship and collaboration. Distance learning can take extra measures to create that natural bonding which can be the essense of higher education.

• How was the collaboration initiated?

I think we've expressed that collaboration was initiated as a bunch of false starts. I recently saw people posting logos and other collaborative efforts in Moodle. At this point, I don't think I could take anyone else's work and combine it with my own unless I did a lot of work to make it fit. If there were collaborations, they certainly occurred indirectly - for example, reading other students' comments and building on top of them, or looking at their courseworks inspired me and forced me to think in different ways. You are right, Isao. I didn't think of that. There were posts in forums that people responded to that helped me gain direction. It does not sound as much, but it is indeed deeper than merely watching "examples" online to get inspirations - the fact that the other students were looking at the same topic as I did made it more real and substantial than merely scanning the web. I could gaze into an alternative universe and see many different possibilities. Unsynchronized brainstorming, that's how I describe them. Terrific description. I like that - unsynchronized brainstorming! Then what would you call our conversation here on Wave? Synchronized brainstorming? The Wave encourages adding comments - exactly what brainstorming is about. No judgement, only contribution.

• How did it affect your own project work?

My project probably could have been better with collaboration. I know my classmates are all very talented in different ways, and my project probably could have been better had we pooled our resources. I totally agree that the classmates are all talented in different ways. For me, this course had the highest level of professionals than any other projects I have done. I must say I was intimidated at first, which probably discouraged me a bit from speaking out on collaboration. I am wondering, if we were asked to create a single project together, what might have happened? I am not merely suggesting it could have been better - it might have gone the other way. The sum of individuals can be much bigger or much smaller than expected.For the final project of a class I took last semester, students formed two groups - one to develop the core values for a company, one to develop more of a sales and marketing focus. It was intense! We had to put all of our work onto a single wiki. It was hard organizing around everyone, but I think it came out pretty well in the end. Do you think similar projects can be done in this course topic (design)? I think we might need to add some twist to make it effective if we do so here - my company excels in industrial design but there is little collaboration. The boss decides almost everything, but the result is stunning, which made me think hard - I have always believed in the power of horizontal partnerships but there are some topics that do not suit them well. The most well-known example is Apple (Steve Jobs (not a fair example - he is brilliant!) decides everything). That's an interesting and unusual perspective. I think your boss is probably really talented and intelligent. That's probably why the dictatorship (yikes!) works. I agree with you about the power of horizontal partnerships. I mean, look at all of the open source platforms that have been gaining ground. One person does not do all the work for any of those. It is the work of many people, and many other people who correct and refine the work of their predecessors. It is true - I once heard the reason why Linux and other open-source platform worked well was because the original model was incomplete - people saw there were holes, and they volunteered to fill them in. Regarding my own course work, if I have joined a joint project, I could have volunteered for the role of "patcher" - to do what's left.For myself, I would have volunteered to do a lot of the design work. I am no expert, but I love following new trends and tutorials.

The embedded version:
(Sorry I couldn't make the Wave appear inside the entry; the embedded version appears outside the main blog entry area, at the bottom of the screen. For clear view, the copy&pasted version above should be better.)

Evolution of visual design: Helping others 'get' it

This blog started in September 2009 as a base station for my technical communication-oriented thoughts and experiments. I have made some changes in visual design - admittedly within the range of Google template. I would like to look back on its evolution and see how I can move on, considering the lessons learned.

Initial Design

Theme:

The skin, shown below, was taken almost directly from a Blogger template called Snapshot, created by Dave Shea. The overall tone of the skin looked futuristic (the top banner was filled with a pseudo-landscape of buildings) without being too intrusive (the main content area was almost blank). I wanted to have a serious tone but not too barren, so that template worked well. I also secretly hoped I had avoided the "Standard Blogger" look by picking minor theme.

Visual Design:

The bright green color at the top right provided a visual "hook". The horizontal lines between the title and content for each text block guided the eyes naturally to each visual element, separated them, and created consistency. One unexpected effect was the profile image in the About Me corner. The image was larger than I had expected, therefore could have worked as the visual hook instead of the green patch at the top.

Text:

I chose the two-column layout, main text on the left (so that readers first catch the main text, not the side bar). The text width was chosen to include 60-80 characters per line, the optimum horizontal length considering the eyeball movement. If I wrote this blog in Japanese, I would have chosen to place the sidebar to the left because in Japanese context the action starts from the right and then to the left. This difference in the direction of action (West: left to right, East: right to left to roughly summarize) is a topic that can be studied more deeply.

1st Revision

I decided to have an experiment: what if I do the opposite of what I had always preferred in terms of visual design and stick with it for a while? In the end I stuck with it for too long but I did reconfirm what I disliked about document/blog design.

Theme:

I chose the most commonly used Blogger template, the default design called Minima, created by Douglas Bowman. Although I liked its minimalistic approach with no background color and no "ornament", I always considered it too traditionally looking for my taste.

Visual Design:

No visual design at all - this is largely due to my laziness I must admit. If I wanted to go against my taste, I should have filled the background with colors and added extra symbols and icons all over the place, to make it visually crowded.

Text:

To go against my taste, I stretched the main column to screen width and tucked the original sidebar content to the bottom of the page. Therefore, unless the visitor has no intention other than reading the text content, he might have a hard time figuring out what to do. I also chose a serif font instead of sans serif. The horizontally stretched paragraph would be harder to read and more formal than the initial design.

Conclusion:

After a while, I still disliked the design and had a hard time reading the blog entries myself as well. The design did, however, made the blog look like a formal report. I never thought of making the blog look like a printed report but it worked nicely. Maybe in the future if I need to make a blog printer-friendly (without falling back on providing a PDF version), the one-column design might work fine.

Bonus: I changed the background color to see how hideous it might have looked.

2nd Revision

Taking lessons from the 1st revision, I decided to go back to the previous style - simple, two-column layout. Still I wanted to make an experiment: what if I stripped off all visual design? After all, wasn't simplistic design my preference? I still liked the barrenness in the 1st revision.

Theme:

I chose a theme called Tekka created by Evhead Glish, which offered the least amount of visual elements in all templates. I found it cold and hostile; here I realized I wanted more warmth in the overall tone.

Visual Design:

Almost nothing existed here, only the texts remained. Result: I still liked not having complex image or photo, but it was too stripped. No taste at all does not lead to better design. I clearly needed a visual variety. If that came from the content I would have stuck with this template; unfortunately the entries mainly consist of text paragraphs.

Text:

I changed the layout back to the original two-column structure to provide easy navigation and also to limit the width of the paragraphs in the main area. Going back to the original style worked.

 

3rd Revision (current)

After going to the extremes, I sorted out what worked and what did not, and picked up a template that works: Rounders by Douglas Bowman.

What works (vs. what does not work):

• Two-column layout (vs. single layout with sidebar items tucked to the bottom)
  
• No complicated images (vs. photos or images)
• Plain background colors (vs. colored background)
  
• Clear separation among each visual element (vs. unified content)
• Warm tone (vs. cold and formal tone)

Shown below is the result. Still not a satisfactory design, but at least it reflects my personal taste sufficiently.

Re-designing a usability testing plan

Usability testing for a website measures how easy it is to use, how accessible it is, and how accurately it reflects the users' expectations through a series of questions and tasks, followed by a close observation. The biggest difference between the traditional questionnaire is that in usability testing, the tester carefully watches how the user actually, er, uses the website. Observing the real behavior as opposed to listening to how the user thinks he or she behaves, provides truly useful data.

Here I examine the first draft of usability testing plan for the NJIT website (a technology university based on New Jersey) and makes suggestions for the plan. The testing plan is structured in two parts: the procedure part and the question/task part. I will also examine how the testing plan can be applied to other commercial sites, such as Amazon.com.

The Procedure: Before

1. Meet participant, introduce yourself, and thank them for their participation.
2. Record demographic data.
3. Briefly explain the purpose of the session.
4. Ask participant to fill out the Participant Consent form.
5. Start the interview with general questions.
6. Ask specific questions from the NJIT Usability Testing Questions document.
7. After the last question is answered, thank the participant.
8. Escort the participant out of the testing room.

The Procedure: After

Conduct the following four tasks even before the usability test takes place.

• Introduce yourself.
• Ask participant about his demographic data.
• Ask general questions.
• Ask him to fill out the participant consent form.


1. Meet participant and thank them for their participation.
2. Ask specific questions from the NJIT Usability Testing Questions document.
3. After the last question is answered, thank the participant and escort him or her out of the testing room.

Summary of changes in the Procedure

The point of the above changes is to save time, and to make the experiment more spontaneous.
Saving time does not need explanation - we all have equally 24 hours, and spending a participant’s precious on-site time for “fixed” information is a waste - they should be completed even before the usability testing occurs, together with the consent form agreement and in the participant’s leisure time.

Making the experiment more spontaneous is to collect genuine response from the participant. If he or she spends longer pre-test time in the usability testing room filling out forms and answering questions, he or she might absorb expectations and might even have an insight about how the website is constructed. Needless to say, the most accurate responses are collected when the participant’s attention level is still high (unless the test’s purpose is to measure the website’s performance toward people with fatigue).

The testing questions: Before

Opening questions

• Feedback on the big photo image(s) on the homepage
• Feedback on the news & events shown on the homepage
• Feedback on the special-interest features
• Feedback on the general mix of content on the page
• Feedback on use of colors, and visual “balance” of design elements
• What they would expect to find behind each Primary Nav links

Tasks

• Apply online
• Find a list of available majors
• Find information about NJIT academic focus (what makes NJIT different from other schools in the region)
• Find out about the student body; would they fit in at NJIT?
• Find directions to NJIT
• Find information on student clubs 
• Schedule a visit to NJIT
• Find information on financial aid and tuition cost
• Find a list of places to go and things to do in Newark/NYC region

Closing questions

• From an internal page: How would you get back to the homepage?
• Is the breadcrumb navigation apparent? Is it clear how to use it?
• Do you have any other observations about the NJIT website?

The testing questions: After

Opening questions

• Feedback on visual appeal and design
• Feedback on the news & events
• Feedback on the special-interest features
• Feedback on the general mix of content on the page
• What they would expect to find behind each Primary Nav links
• Feedback on navigation including menu and breadcrumbs

Tasks

• Apply online
• Find a list of available majors
• Find out about the student body; would they fit in at NJIT?
• Find directions to NJIT
• Find information on student clubs 
• Schedule a visit to NJIT
• Find information on financial aid and tuition cost
• Find a list of places to go and things to do in Newark/NYC region
  

Other observations

• Do you have any other observations about the NJIT website or any other issue?

Summary of the changes in the testing questions structure

I will change the three-part structure into a two-part structure plus one closing question (Do you have any other observations?). Unless absolutely necessary, all questions should be asked at the beginning when the participant is highly alerted. The exception is the observations request, and it does not have to be limited to the website design. The participant might have some opinions about other issues such as the usability testing scheme, tester’s attitude, and university website in general. Any of these information would be useful for both the website and the usability testing.

I added a feedback on navigation and merged the breadcrumb question from the original “Closing questions” in it.

Also, I deleted the academic focus question which sounds impressive but is ultimately pointless: how many people read organization policies to find out how unique the university truly is? Instead, more attention should be paid to where the users actually go to find out their true interest.

Applying the usability test documents to a commercial site

All the previous suggestions were made for a university website, but most of the items also apply to commercial website as well. Therefore I would not change the overall structure, but will add the following items in the Tasks corner. Of course, each question or task should be modified according to the actual information in the commercial website.

• Complete a purchase of a randomly selected product
• Enter a user comment/review
• Reach customer support desk and ask imaginary questions
  

The completion of the purchase is about testing the e-commerce functionality thoroughly. Unlike university, customer are likely to complete the purchase in a single action, and when they cannot do that, they are far more likely to abandon the website and look for alternative options.

Entering a user comment/review is to test how much the website encourages collaboration  with and input from the users. Everybody say they treat users as collaborators, not just buyers, but do they live up to that hype?

Reaching customer support desk is one of the most important factors in improving customer satisfaction. Here, time is the critical factor - when observing the time, the testers should count the time the participant took to complete each transaction (this is especially true for reaching out for the support desk, where real customers likely have low tolerance). A commercial website is about helping customers get what they want as fast as possible.

Google site: How it has evolved

I have a new website built on Google sites service: free (as usual), simple, stable, and also flexible enough to allow creating surprisingly decent website. One such "example" website is Steegle - a website offering tips for building Google sites on which itself is built. The author not only contributes frequently to Google Support forum and offers free tips but also provides paid service for advanced consulting. Many features in my own websites were taken from Steegle's tips.

My website, 5-minute courses, offers insights into Asian (mainly Japanese) cultures, especially their "peculiar" aspects which baffle people who are not familiar with them.

 

The course is offered as a small presentation, with comment facilitation at the bottom. The right side bar provides site structure, search box, contact information, and RSS link. The top logo also serves as the link to the home page, and the buttons below the logo offers shortcuts to major sections. Below is the original blueprint of the website as I planned in September.

The goal of the original plan was to provide a web-based training system for an imaginary global consulting company with the following traits:

• Visual-based: non-verbal and reflective learning rather than verbal and active learning
  
• Concept-driven: theories and concepts rather than examples and linear steps
  
• Optimized for global team: can be taken anytime, anywhere

Is the current website meeting the original goals (or even exceeding them)? I will examine the effects and see what was accomplished and what is being left.

Features
Some features have stayed the same and some did not. Here are the quick summary of features, realized or not.

• Realized: Course title, Course content, Controls, User comments, Search button, What's new, Course structure
• Not realized: Login information, Ratings
  

A majority of the functions were realized. I did not include the Login function in the website and instead chose to make it more "open" to end users, by allowing anybody with Google account to comment. Originally commenting in Google sites were allowed only to "collaborators" registered by the web master, which could have worked as a pseudo-login system. The user rating function is something that wasn't realized due to lack of technical expertise or knowledge - by default Google sites does not offer such function (yet).

Design aspects

Let's take a look at each of the realized element and see how it was designed and how effective (or ineffective) it might be.

Template design

I took the Solitude: Olive template shown to the right, took the header background off, and left the green color for texts. I also changed all font into Trebuchet. I wanted a bare-bone design with minimum shades of green (nicely realized in the original template). Although the target users are visual-oriented, I eliminated the background color to let them focus more on the content - too much design element, if not placed carefully, might lead to visual noise.

Logo & Menu design

The logo and menu are clickable image texts. They are designed to match the bare-boness of the website and its color. Functional-wise they work fine, but unfortunately the image color does not exactly match the text color (see below: icon color and title color). The logo/icon font does not match the main content either, but that is intended. Other colors and textures were not added to avoid visual noise, as in the background color: future revision should add more design variations without adding noises.

The menu icon was added also to offer a quick high-level site map for the target users who prefer to have an overview of the situation before going into details.

Main content design

The presentation was created in Google Document (Presentation) because it offered (1) easy integration with Google site and (2) Came with embedded playback control and (3) modifying the original presentation gets reflected to the Google site in real time. Presentation / Video sharing sites such as Slideshare offered similar embedding function, but none could offer the (3) real-time option. Below is the close-up of the embedded control playback.
The content itself -- presentations -- are text-based, which seems not fit the visual-oriented target users, but are designed so that each presentation only contains a handful of words. The presentations are structured so that the main argument (concept) is presented first, followed by examples.

Comment design
Google sites is by default equipped by commenting function but it is not open to anyone who visits the website: the web administrator need to give permission as "collaborators" of the web. This might work well in educational usage (commenting can only be done by students) or internal training as proposed in the original plan. This time, to (1) encourage more people to comment and to (2) test an "unorthodox" comment field mechanism introduced in the aforementioned Steegle website, a more open (anybody with Google account can comment) field is embedded as a widget. As shown in the snapshot below, when a user is logged in to his or her Google account, the profile image automatically shows up, creating an instant identity field. This feature should work especially well with the target users -- visual-oriented and international -- where identifying people by photos is considered much easier than names in texts (example: it is very hard for people from U.S. to identify the sex of the Chinese name Bai Ling).

Search design

Google site by default offers a search box. I have modified the option to add a normal Google search option in addition to the default site search (see right). This is a decision that made the original design more complicated (thus less "visual-oriented") in return of increased convenience.




What's new design

Google site by default offers a page template that can be used for posting news and updates. The What's new page offers a quick overview of what is going on in the website -- it suits the target customers who prefer to grasp the "high concept" before going into the details.









(Bonus) About author design

The About corner, the author's page was also meant to experiment with page design. Instead of the default two-column, I used three-column design with equal width, and embedded a Google map showing my address. The gorilla mask was added to add a fun element for visual-oriented target users.

Images replace words

A picture is worth a thousand words. In general, images are more powerful than words when it comes to clarifying parts of our communication. Maybe ALL of our communication -- this can be the subject of another topic -- but since we have relied so much of our communication on words (spoken or written), here I will take a stance that words and images are both essential and compensate each other.

I will use two examples to illustrate how images effectively replaces words to make the whole communication shorter and clearer. One is a presentation slide from Garr Reynolds, a presentation guru and the author of the bestselling book, Presentation Zen. It shows the power of pictorial aspects of images ( = photos and illustrations). Another is an informative map from Information Architects, a Tokyo-based interaction design firm. Their informative maps show the symbolic aspects of images ( = patterned symbols and icons)

Presentation Zen
Presentation Zen is an impractical advice about making practical presentation (Sorry Garr, your advice is so sweet and motivative that it almost sounds like music, but is hard to follow to me). Nevertheless, being a guru, his presentations are highly aesthetic and easy to understand. Let's break one of his presentations down and see how images are used.

Presentation Zen

View more documents from Fabian Crabus.

Slide No.1: Seduction. Come on, it's gonna taste like a raw sushi. What does a sushi image has to do with presentation? Nothing. But it has a loose connection with the word "Zen" (both are from Japan) and anyhow, most of us love sushi, or have heard it is delicious.
Slide No.2: Example. This is how you reduce clutter. Here, a series of stones shows what it means to reduce clutter. By showing a set of stones built on fragile balance and making it more stable step by step, Reynolds effectively demonstrates both the definition of reduction and the effects behind it.
Slide No.3: Catalyst. Open up your heart, now. We all have different ideas about abstract words such as emotions, as used in this slide. What shall we do to demonstrate such words? The answer: let the audience come up with their own definitions. A beautiful image of a nature always work well for this purpose.
Slide No.4, 7, and 8: Focus. Read the words. In these slides, Reynolds uses the lack of image to guide users to focus on the texts (which is the default usage of presentation slides) but since his previous images were so effective, users also notice that something is missing, which also enhances his "less is more" philosophy (slide No. 7).
Slide No.5: Humor. I know how you feel. Reynolds shows his sense of humor and humiliation by laughing at his own expense (presentation IS boring, isn't it?). This image shows the power of visual clearance; unlike verbal humor, we don't need to think hard (sometimes) what the punchline is.
Slide No.6: Future. This is where you can apply what you have learned today. The image shows the future (or current) possibility -- where the presentation philosophy can be applied in our real life.
Slide No.9: Switch. That's it, thank you ladies and gentlemen. The image demonstrates clearly that the slide is over (we all know that it is not always that clear), with grace and appreciation. What works better than an image of a theater curtain?

Information Architects
Based in Japan but originated in Europe, the members of the design firm Information Architects organizes information (especially that related to the web) in a series of 3D-like interactive maps. Titled Web Trend Map, users not only understand the "big picture" but also dive into each of the presented website easily. The unique part? They map information on real locations. The following is such map for Infographics web sphere, mapped over geographics of Manhattan, New York. Let's see what makes this map effective, in terms of graphical symbols and wayfinding.

Icon: graphical icons makes it easier to identify the website because the real profile photos are copied from the original websites. It is not only easier than creating original icons for each website, it is also more effective.
Symbol:all information is presented according to a set of design rules (including icons). Even the title texts are presented in icon-like manner, making the whole presentation a collection of symbols. Once users get used to the rules, identifying information becomes easy because even text search turns into graphical (symbol) search which requires less brain power.
Wayfinding: I know -- even though the map is based on Manhattan, aside from landscape there is nothing that resembles the real location. Nevertheless, mapping websites onto a pseudo-location works well for wayfinding, because we are wired to memorize a particular place (in this case, a website) with regard to its surrounding markings. Isn't it easy to memorize a location when it is presented like "cross the Brooklyn bridge, turn to the left, walk two blocks"?

Bonus: Why not have a gigantic web trend map covering the whole web sphere, based on Tokyo's rail system (which is arguably as complex and 1/100th as convenient as the Internet)?