--- title: "Kathy's Idea meet Bill's, Bill's meet Kathy's: On Idea Splicing and Attention Economics" date: 2005-12-16T01:07:05Z modified: 2005-12-16T01:07:05Z permalink: "https://redmonk.com/jgovernor/kathys-idea-meet-bills-bills-meet-kathys-on-idea-splicing-and-attention-economics/" type: post status: publish excerpt: "" wpid: 423 categories: - Uncategorized timestamp: 2005-12-16T01:07:05Z tags: - Uncategorized --- ——warning: this blog has little if anything to do with enterprise systems————— This interweb thing is pretty cool. There are, like, all these people out there talking about stuff. They don’t know each other but sometimes their ideas inform one another. It’s pretty neat. The ideas end up talking to each other, if someone makes an introduction, a link. Even if the people don’t meet, their ideas do. This is, like, better than a library. Its nearly as good as a pub. Anyway, terrible intros aside, I couldn’t help but mentally tag some associations between Kathy Sierra and Bill Scott’s blogs yesterday when I was reading though them. That is, I did some [thlinking](http://www.redmonk.com/jgovernor/archives/000555.html). What do “interest”, “UI design”, “story-boarding” and “courseware” have in common? Let’s see what I can point to. [Bill Scott](http://looksgoodworkswell.blogspot.com/2005/12/storyboarding-interesting-moments.html) is helping to build better user interfaces as an Ajax Evangelist at Yahoo. The other day he had an intriguing post, [Storyboarding Interesting Moments](http://looksgoodworkswell.blogspot.com/2005/12/storyboarding-interesting-moments.html), about the language used in web design. It’s really not so interesting talking about “event states”. So, what about an alternative? > Recently, I was at a talk where [Nate Koechley](http://nate.koechley.com/blog/) presented about the new vocabulary of user experience in the world of Rich Internet Applications. He used the term Interesting Moments (which was coined by [Eric Miraglia](http://360.yahoo.com/ericmiraglia)) to describe the event states within an interaction that are points of user engagement or interest. I love interesting moments. [Kathy Sierra](http://headrush.typepad.com/about.html) is shaking up the world of technology training by jumping in [headfirst](http://headrush.typepad.com/creating_passionate_users/2005/12/head_first_html.html). She writes one of my favourite blogs- [Creating Passionate Users](http://headrush.typepad.com/creating_passionate_users/), which is all about how to create kick ass experiences so users get jazzed about what you do for them, so they keep coming back for more, and tell everyone how great you are. Yesterday she wrote about training courses- [but is it interesting](http://headrush.typepad.com/creating_passionate_users/)? > the word “interesting” doesn’t even set the bar very high–it’s the word we use when we can’t think of anything complimentary to say. “He is…well…_interesting_” or “Hmmm… _interesting_ perspective.” The words we _actually_ wanted to use in the checklist were _compelling and engaging_, but we thought _interesting_ would be an easier sell. > > But even if he’d left “Is it interesting?” in, I now realize that many people would automatically check it off without really stopping to consider whether something really _is_ interesting. Or that people would assume that given a certain context, “interesting” is irrelevant. Think about it. Even if your actual _product_ is interesting (but still, stop and ask yourself if _that_ is really true), do you have docs, FAQs, specs, articles, learning/support blogs, etc. that are NOT _interesting_? _Should_ they be? Of course they should. And I can’t help thinking about building training and technical documentation as a UI issue, and vice-versa. After all, [poor documentation is a barrier to entry](http://www.redmonk.com/sogrady/archives/000954.html). So, of course, is a poor UI. Bill and Kathy’s ideas meet in the concept of storyboarding. Bill says: > Thinking of storyboarding interesting moments within an application, an interaction, or a widget simplifies our thinking. > > It actually turns event states inside out and focuses them instead on the user. It asks the question, “What is interesting to our user?” and “What is needed to engage them (invitations) and aid them (feedback) through our story?” The designer becomes a director. Kathy gives some pointers to increase and create interesting moments: > **\* Surprise, novelty, the unexpected** > > **\* Beauty** > > **\* Stories** > > **\* Conversation** > > **\* Emotionally touching (the whole kids and puppies thing)** > > **\* Counterintuitive failures or mistakes** > > **\* Fun, playfulness, humor** > > **\* Varying visuals** > > **\* Faces of people, especially with strong expressions** > > **\* Sounds, music** > > **\* Shock, creepy things** > > **and of course…** > > **\* Sexiness** > > One fairly straightforward way to make documentation/training/articles interesting is to crank up four sliders **Conversation, Variety, Visuals, and Story.** What does this mean for RedMonk, or your business or service? What is our/your UI? Are the potential interaction and entry points “interesting”? I think this question is something we all need to work on in 06: how do we create interesting moments? Interesting moments foster attention which drives revenue. How does attention drive revenue? Just ask David Beckham or Kate Moss (even negative attention drives money, sometimes more money, into your pocket) or any of those popstars that have no discernible talent but do have a multimillion dollar marketing budget about the relationship between attention and money. Paris Hilton is the acme of the mainstream attention economy. Attention directly drives money, its as simple as that. The more attention RedMonk gets the more in demand our services are. RedMonk could give away all our content and if it meant more people knew who we were we would make more money in the long run. But you have to be interesting… I could argue this blog is an exercise in [Bloom’s Taxonomy](http://www.coun.uvic.ca/learn/program/hndouts/bloom.html). I certainly like the idea of ideas that bloom and subsequently bear fruit. It would be great to think a blog about training courseware could impact on Yahoo’s user interface design, especially if I had been involved in introducing the ideas to one another. This blog might even introduce the people behind the ideas. And that is, like, The Conversation in a nutshell: what story are you telling and how can you be more interesting to people? And what would a creepy event state look like?