Thursday, Jun 12, 2008

A sample 'Only' statement for the I.A. Institute

Design Thinking, Experience, Information Architecture, Metrics & Validation by Austin Govella

A sample 'Only' statement for the I.A. Institute

A look at how to put an Only statement together, as well as how it works using the I.A. Institute as an example.

4 Comments

To kind of go through how this works, I thought we’d work through an example using the IA Institute. Now, I’m not picking on the IAI. I love them. I am a reasonably vigorous part of them. But when I was sitting in the annual meeting, I though to myself, “man, do these guys need an only statement”. So here goes our fictional exercise at crafting an Only statement for the IAI.

We’ll start with their tagline (“The IAI supports individuals and organizations specializing in the design and construction of shared information environments”) and convert that into an only statement:

WHATThe only organization
HOWthat develops and supports a community
WHOfor information architects
WHEREanywhere in the world
WHYwho want to design information spaces
WHENin a world of ubiquitous data, access, and connection

Well, that’s not totally true. We still can’t agree on what an information architect is, so let’s change that the UX professionals:

WHATThe only organization
HOWthat develops and supports a community
WHOfor information architects user experience professionals
WHEREanywhere in the world
WHYwho want to design information spaces
WHENin a world of ubiquitous data, access, and connection

And do we really develop new communities, or do we support existing communities? Let’s tweak that, and change the text so we don’t use world twice:

WHATThe only organization
HOWthat develops and supports a community
WHOfor user experience professionals
WHEREanywhere in the world around the globe
WHYwho want to design information spaces
WHENin a world of ubiquitous data, access, and connection

So, that’s it. Now we have an Only statement that describes who we are and what we do. It’s a nice enough exercise, but Only statement works best as a way to validate design decisions.

Using the Only statement

Creating the Only statement packs all of your meaning together. Once everything’s packed, you can unpack the meaning to understand more about the project’s core essence.

So, in the magic world of our example, we’ve reached the final version of our Only statement, and it reveals an interesting fact about the organization:

  • It’s not necessarily a professional organization, and not necessarily supported by membership.
  • It’s all about the community of practice, and not necessarily the practice. (Props for the ‘Blurt!)

That definitely gives us some things to think about.

Based on the Only statement, we might reassess the services the organization provides. For our fictional version of the IAI, we might decide a community needs several things:

  • Jobs (an ecology of stuff to do and people to do it; not necessarily paid work.)
  • Discussions (email lists, forums, distributed conversations)
  • Multiple languages (translations)
  • Events (meetings, conferences, f2f conversations)
  • Localized news, events, discussions, jobs (Politicians always say “everything is local”.)
  • Discussions with other communities (elevator pitches/mobile widgets, evangelization)
  • Mentors and mentees

And since we’re framing things up, maybe we organize community needs into two chunks:

  • knowledge sharing (our list of community needs from above)
  • community memory (best practices, tutorials, case studies, library, books, links)

Already, we have an understanding of what the IAI is and what it’s not. We have a framework for deciding what kinds of activities it should support, and those it shouldn’t. Essentially, we’ve defined a strategy we can follow for years.

And that, I think, is the magic of the Only statement: that it can help guide product and design strategy. But does it have to? Next, I’ll talk about at how an Only statement does and doesn’t interact with strategy.

Talk About "A sample 'Only' statement for the I.A. Institute"

Register or Log In to comment

Cindy McWilliams

Cindy McWilliams said:

I remember when we worked on an only statement for our team – there was so much debate! This post is a great intro to the use of this tool. It not only helps with definition but also with understanding the expectations of those involved with that product or organization.

I was a little surprised to see you drop the term “IA” from the statement so easily. I like to think it’s about working with information architectures in the context of user experience. I think a structural reference in this only statement is important for narrowing the focus.

I liked how you aligned content and services to the only statement in your last few paragraphs. That would make a nice visual.

Thu, Jun 12, 2008 at 07:16 PM

Austin Govella

Austin Govella said:

One thing I liked about when we did the exercise for our team is the way we couldn’t necessarily agree on an “Only”. That can be a useful insight, too.

Mon, Jun 16, 2008 at 04:27 PM

Karen Loasby

Karen Loasby said:

I was experimenting with applying this to my organisation, the BBC, but get stumped by how wide reaching the org’s remit is.

Your first post title suggested the approach was for projects but I was interested that you chose to illustrate it by using an organisation.

Do you think we should stick at trying to come up with an organisation statement or just do this for individual projects?

Mon, Jul 28, 2008 at 01:07 PM

Austin Govella

Austin Govella said:

The first time I tried this, it was for a specific, but pretty broad project (Fancast). Since the Only statement focuses on differentiation, you could use it at any level. For Fancast, we made one for the project as a whole, but we could also make one just for the online video experience.

It’s definitely useful for the whole org.

When I was working on the Only statement for Fancast, I sketched one out for Comcast (the parent organization), but I never documented or communicated it out. I used it as a very broad horizon for making sure the Fancast work was properly aligned with the company’s overall strategy.

Tue, Jul 29, 2008 at 02:25 AM

Hot topic? Subscribe to a feed of this post's comments.