I’m working like mad through March to write a book on information architecture.

As I go, I find I need two things – stories to illustrate points I describe, and examples of sites that do particular things. This post will be a continually-updated one that lists what I’m interested in and what I have enough of.

Stories

I’m interested in stories – usually about a page (400-500 words) around the following ideas:

• How skills in previous roles helped you when you started in IA. I’m looking for an example from people who previously did usability testing and business analysis (I have tech writer, graphic designer & developer all covered)
• How setting clear project goals at the beginning of a project helped that project run smoothly, and how you used them the project
• How not having clear project goals caused all sorts of project crap
• Stories about how you brainstormed and selected content for a new site or redesign. Particularly any that used a quantitative approach to selection (e.g. a scoring system)
• How you’ve worked with clients to get content from them
• How you’ve communicated about content needs, what content you have, and gaps
• How did you test a draft IA before you designed navigation and pages

All stories will be in your words (I may tweak slightly for length or clarity, but will show you) and I’ll include your name, role, website etc.

Examples

I’m interested in examples of the following sites or features. It would be fantastic if you’ve been involved in designing the one you give me – I may want to chat to you about them (I don’t want to say ‘this is a good example’ and later find out that it’s completely unusable for real users):

• A real-estate website that uses an interesting filter or faceted browse
• Great comparison interfaces, of any type
• Tools other than Xenu Link Sleuth that can list out everything on your website
• Link-rich home pages

Contact me

You can leave me a comment, tweet to me (@maadonna) or email me on donna@maadmob.net.

This week’s big news is that I’m writing a book on information architecture.

It will be a introductory-level book, mainly for people who have to create an information architecture but who don’t do it very often. It will be very practical and down to earth and written in a friendly way (if you know me, it will sound just like I’m talking to you, though without the swear words!). If you’ve taken one of my information architecture workshops, it will be the workshop expanded and updated.

It will be published via Mark Boulton’s company Five Simple Steps. I’m really excited about this – I think we are a great fit for each other.

More details to come of course, including release date (which we haven’t discussed yet, but I think we’re both hoping to get it done fairly quickly), table of contents and a book website.

Given I’ll be writing more, I’m likely to be blogging more – yay!

I’ll also be on the look-out for people who can review chapters or who I can talk to for some case-study material to provide real-world examples. Let me know if you’re interested in either of these.

When I teach information architecture, the most common questions aren’t about the principles, but about the process. Just how do you decide on a particular method, how do you choose categories, how do you know what you’ve come up with is right.

As a teacher I’ve spent much time thinking about this, reflecting on my own process and how it actually works for me. And I’ve figured out the answer.

When I teach I tell people this answer. Most are surprised, but there are always a couple of people in the room who nod to themselves and look comforted.

Would you like to know the answer?

Here it is.

Wait for the surprise.

Just make it up.

Yep. As some high profile product says, just do it.

This is surprisingly easy, but there is a dependency. You need information. You need to understand what you are trying to achieve, what users of the service need and know, and you need to know the content well. If you don’t have these things, it will be hard. But if you do have them, pulling them together into a first draft is surprisingly easy.

When you have made something up – and I don’t care whether you do it on a whiteboard, in a spreadsheet or in your head – then start thinking about whether it will work for the users, and whether it will work for the content. Revise and play with your idea until these things start to fall together.

At some point you’ll start to feel good about your made up draft IA. In your head it will look like it will work for the users and the content will fit in. You can see how it will help the organisation achieve its goals. (If you can’t get to this point, it’s likely you are missing some kind of information. You’ll need to do something to fix that, or it will never work).

For me, there’s a funny feeling at this point – it feels simple and clear and makes me wonder why it took me so long to figure out.  That’s when I stop fiddling and start talking to people about it. And I’m yet to be be majorly wrong, so there must be something in it.

Today’s example

So I was doing this today for a client (I won’t say who, not that it’s sensitive – I just haven’t mentioned this to them). I took photos as I played with the new IA & thought you might be interested.

The background is that this is a fairly straightforward redesign of some government content. I know what the team want out of it, have done some basic user research, cleaned up the content and decided what to keep and create. It will be for a simple hierarchical site, so the IA in this case is a set of categories/subcategories to be used in navigation.

I don’t always do it like this, but today I jotted the main content chunks onto sticky notes. Apart from being physical, this helps me get away from the way content is organised now:

Then I jotted things we learned from user research onto a different colour note:

Then I shuffled them around into groups of things that go well together:

I played with these for a little while and moved a couple of things between piles, but it wasn’t hard. It fell together easily. All the user needs are catered and all the content fits in. There are some spots where we need some extra content, and there is no content that someone doesn’t need. I could come up with sensible titles for all the groups.

My followup step from this was to create a quick spreadsheet with the categories, subcategories and main content pages that came out of this shuffle; and also add a couple of special navigation items that will pull together some things across the piles (like forms and publications, which are scattered across the piles according to their topic, but will need separate entry points for some user tasks).

Next steps

Tomorrow I’m going to run through this with the client team. I’m not drawing it up into a sitemap now. I’m going to talk them through it as I draw it on a whiteboard. This lets me describe each section and the rationale behind it, without them being distracted by something I have already written down. I’ve done this before and it is a great trick for communicating the draft IA – it lets me present it as a story, and triggers sensible questions.

Then, of course, there is lots more to do. I’ll be using an existing navigation approach, so don’t need to design navigation. But I need to design all of the index pages – these will introduce each topic and provide deeper links plus cross links.

And we need to revise all the content. As this happens, the IA will change, but if I’ve done my job well it won’t change dramatically.

What, no card sort

OMG, I just wrote a book on card sorting, and didn’t run a card sort. Why not?

Well, I did other forms of user research which gave me a fairly good idea of the main issues and needs for users. Most users only ever need one or two content pieces, so there was little point getting them to do a card sort on things they don’t care about. And I didn’t feel like I had big gaps in my knowledge that would mean a card sort would help. So I didn’t.

We’ll do usability testing on this as well, probably before content rewriting and after.

I’ve been recently looking for new suppliers for products (lanyards, badge holders, pens etc etc). No matter what I’m looking for, I start my search on the web.

Now I don’t usually write black and white rules for things, but today I’m going to.

If you are a supplier of a product, and that product can be purchased elsewhere, you must, on your website:

• Include prices
• Not make me register to see prices
• Not make me wait for my registration to be approved to see prices
• If your product is out of stock, tell me when it will be in stock
• Make it easy for me to order online
• Be credible
• Help me feel confident that my order will turn up

Because, duh, if you don’t, I’m going somewhere that does.

Earlier this week I had the pleasure of becoming a published author.

My book on card sorting is now available.

You can buy it right from the book website – either the printed version (plus digital) or digital alone.

Or you can get it via amazon if you are buying other things at the same time : Card sorting (Donna Spencer).
Please let me know what you think!

I’m going to be in London in June (for UX London) for the first time and have about 4.5 days completely free to tourist. I have absolutely no idea what I absolutely must do. I will definitely see stereotypically London things but need some help with the weird things that I might specifically like. 

So, based on my previous touristing, here’s what I like:

• Walking through interesting history & architecture (can probably tick this off with no effort)
• Anything that is just stunningly beautiful, or unique nature
• Costumes, of any type and any period
• Weaving
• Other textiles
• Design museums (even better if they have textiles, but furniture and interesting industrial design is excellent)
• Paul Weller, The Jam & late 70s punk
• Dr Martens – is there a Dr Martens museum? Or awesome shop. That would be cool.
• Doctor Who
• Interesting, funky shopping streets. Even if I don’t buy anything
• Cool arts & crafts markets
• Secondhand bookstores
• Pubs that combine great beer with great people watching
• Pubs with good beer
• Live theatre
• Cathedrals – not for religiousness, but they are often awesomely beautiful

And I really don’t need:

• General art galleries: Yes, I’ll pretend to be cultured, but I feel more like ‘yes, I saw that’. If I must do it, I must
• Snooty expensive things
• Touristy expensive things
• Any tour that makes me do it your way, not my way (I’m looking at you, Gracelands audio tour)
• Nasty, flashy shopping streets where I feel like I can’t walk into a shop (I’m looking at you, South Beach)

So tell me what I should at least research. And tell me what I should think about…

Sometimes twitter just doesn’t do it for a good, solid ‘what have I been doing’ catch up post. So here’s one that takes more than 140 characters.

It’s already April and I feel like I haven’t done much work this year. Of course, I have been busy as hell. I’ve done loads of planning and administration for UX Australia, wrote a brand new full-day advanced information architecture workshop, and had plenty of meetings with content authors for a long-running government project.

What I’ve really been doing is teaching. I’ve done five in-house full-day workshops, 2 conference talks, 1 full-day conference workshop and 2 full-day public workshops. So that’s work, and it’s work I love. But it is so fun that I forget that it is actually work, and feel like I haven’t done anything.

But really, the pain of airports and airplanes should make it feel like work. I’ve travelled so much this year that I can visualise the Qantas Club lounge in every Australian city (except Adelaide). I do think I could walk in and make it to the wine bar with my eyes closed. 

But April is looking up. I’m home all month, in my lovely house, with my lovely dog and a brand new bed (mattress arriving Thursday, 1000TC sheets ready in the cupboard). I have a nice pile of client web writing, new book writing (I’m writing an e-book on web content for Rockable press), some wireframes for a favourite client, and more bits and pieces for UX Australia.

I hope that the biggest news for April will be that my card sorting book is published. It is at the printer now, and should be ready in a couple of weeks. I promise I’ll tell you when that happens.

May is also looking like fun. By then I’ll be over my travel fatigue, which is good as I’m going to Philadelphia to talk at the jboye conference (IA workshop and content talk). Just as cool is that I’m going to be around for the IXD/IASummit redux in DC. Going to hire a car, drive from Philly to DC, see some friends. Ahhhh, I’m already getting excited about it.

Then June. OMG June!

In June I’m first going to Denmark to teach an interaction design masterclass (and some community of practice meetings). Then to London to do some touristing with my friend CJ (I’ve never been to London), then two workshops at UX London, then more touristing, then home.

So in late June, I’ll be saying ‘I’m so glad to be home’ and desperately waiting to get away again. I feel like that Camp Grenada song – you know, the one where the kid starts of hating it, then loves it. Me & travel – Camp Grenada.

One of the main challenges with creating any categorisation system is to make sure it collects what you need and matches up to the real world.

Here’s a list of single-select items I just came across on an otherwise-decent survey for a hotel where I recently stayed:

• Household with children no longer home
• Couple, no children
• Household, with children
• Single, no children

Firstly, I wonder how it is useful to them to know about my family situation. But secondly, where do I fit? Right now I’m single, with a child who lives with me half time. That so doesn’t fit into any of those categories…

I woke up feeling strange this morning. No, it wasn’t the three hours sleep – I know what that feels like. And it wasn’t a hangover – I certainly know what those feel like. It was something quite different and it took me a little while to figure it out.

But it needs some backstory. I was at South by Southwest Interactive this weekend. It is an incredible conference, with lots of smart people and interesting talks, and quite famous for its parties. The SXSW film festival is on at the same time so Austin is packed and there is more than plenty of stuff to do.

I was on a panel with the awesome Nick Finck and Michael Angeles, called ‘Wireframes for the Wicked‘. It was fun to work with them and according to twitter our session went pretty well. Lots of people appreciated that we left half of the time for audience questions and that we actually tracked questions asked via twitter (#wickedwire) and answered them at the time and alongside questions from the floor. 

Immediately following our talk was one by Bruce Sterling. His SXSW rants are famous (his SXSW party at his home also used to be famous), and I’m a big fan of his writing, so this was absolutely mandatory for me. I didn’t realise it would be so hilarious. Via a few wandering twists and turns, he spoke about change. It was a serious topic, and delivered seriously in some sections, but right in the middle he had a Bruce party right there, with crisps and beer and awesome cookies. His delivery is amazing and his timing is just perfect – he had the audience roaring with laughter (or was that just me).

With that over, I grabbed my buddy Dan Willis and we went out to dinner. Dan always makes me laugh – I’m still wondering just how mad he really is. But that doesn’t matter because we really can spend a lot of time just talking and laughing.

With the film festival on, we could get into first-showings and Dan suggested we go see ‘Observe and Report‘. I love going to movies without knowing anything about them and that certainly was the case here – I hadn’t heard of the film, the director, the actors and had no idea what it would be about. The lack of expectations can make for an amazing experience and that certainly was the case. This was one of the funniest (and weirdest, and with incredible timing) movies I have seen in a long time. I don’t usually laugh out loud in a theatre but I was laughing and hooting and clapping and so was the rest of the audience. I also don’t usually talk about movies straight after, but Dan and I were laughing and cracking the best lines all the way to the next part of the evening – the Blue Flavor party.

When the bar closed and we were all pushed out the door, as happens every morning at 2am in Austin, Dan, myself, Matt Balara and Ola hung around for another hour or so just shooting the crap, talking about everything and nothing and laughing a lot.

So can you pick up the thread here and know why I woke up feeling strange. I spent about 10 hours straight laughing. Laughing in Bruce Sterling’s talk, laughing with Dan, laughing at the movie, standing ’round on the street laughing with friends.

And I still have a big ball of laughter glowing inside me. It feels incredible and amazing and wonderful and I can’t wait to do it some more…

I usually tweak my bio now and then, but with my card sorting book coming out soon (yes, really – March) I want to have a better look at it – after all, it will be on the printed version forever.

It made me think about the point of a bio and what you really want to learn from it. Mine at the moment sort of tries to tell a bit about my experience, a bit about my personal approach and some of what I want people to know so I can do more of it (i.e. teaching!)

But is that what you want to know when you read someone’s bio? How important are these:

• Time in the current industry or doing the current work (I have 9 years up, and it feels strange…have I been at this long enough to be less specific?)
• Types of systems I’ve designed (intranets, websites, applications, e-commerce, search). Does that matter? Or is that actually the most important thing?
• Who I’ve worked with. I never include this – do you trust me more if I’ve worked with big-name brands?
• My approach or philosophy. I care about this when I read other people’s bios, but do you?
• What I do when I am not working? Does that make me look human, or get in the way of what you really need to know?

Ah, this is all too hard. And I teach people how to write. Now while I wait for your comments to pour in, I think I’ll go take some of my own advice.

And if you’d like to tell me about your favourite bio (of someone else), that would be fantastic!

I’ve been annoying my friends by hinting at a secret project underway. Sorry guys, but I’m glad I’m finally able to tell you.

The big secret is that we (me, Andrew Boyd, Steve & Danielle Baty) have been doing the initial planning for a user experience conference, to be held in late August in Canberra (Australia).

I think it goes without saying that I’m really excited. I’m excited to be involved in conference planning again, and excited to be able to arrange a conference for my community.

One of the things I’m happiest about is that it will be a proposal-based community conference (ie one where anyone can submit a proposal, and the community reviews to help select the program). Don’t get me wrong, I love conferences with professional, high profile speakers; but I also love the homey feeling of a community conference where you get to contribute to who presents what.

The other thing that we are going to be doing, and this will get started later in the year, is running workshops. I haven’t been able to run my own workshops as often as I’d like in Australia, so hope to do that more. And we’ll be inviting other folks to teach practical full-day workshops. If there’s someone you’d like to see, or a topic you’d like to see covered, let me know and we’ll see what we can do.

Anyway, that’s the news. I hope you’re almost as excited as I am!

For me, the next few months are full of conferences and workshops. My calendar is so packed I don’t know where the work will fit. You can catch me at:

• Web standards group Canberra (4 Feb): Talking about user research, why we don’t do enough of it and my new user research decision diagram
• Webstock, Wellington (11-14 Feb): I’m not speaking here, just hanging out at a conference for once
• South by Southwest Interactive, Austin (13-17 Mar): On a panel with the awesome Nick Finck & Michael Angeles, called Wireframes are wicked
• IA Summit, Memphis (18-22 Mar): I’m teaching my full day workshop on information architecture, and doing a presentation called ‘Design games for IA’
• Wellington, NZ (end Mar): my good friends from Optimal usability are hosting me to teach beginning and advanced IA (more details to come soon – this will be the first time teaching my new advanced IA workshop)
• April – wow, I have the whole month free
• JBoye09, Philadelphia (May 5-7): I’m teaching my half day IA essentials workshop, and doing a talk called Getting content right
• UX London (Jun 15-17): I’m teaching two half day workshops – IA essentials and  Designing for people

I hope I see you at one or more of these.

And remember, I can teach any of these workshops in-house to your team (see my list of IA, interaction design, usability & content workshops).

The User Interface Resource Centre have published an article I wrote for them called What, Where, How: Designing and selecting components for user interfaces.

The article is about how to make sure your components will be usable and easy to learn. It covers some fundamental cognitive principles and their implications for component selection.

Yesterday I attended what I think will be my last conference presentation for the year. And it was a doozy.

I’ve sat through at least 100 conference presentations this year. Some were awesome, some were awful and most were pretty good. But the awesome and awful ones stick with me – when a topic is not of interest to me or is about something I already know, I pay more attention to the presentation style, looking at what works and what doesn’t.

So I’ve compiled my ten tips for presenters. These represent the things that great presenters do well and bad presenters just butcher. Of course, I’m not perfect, and I know I’ve made some of these mistakes, but I’m trying to do silly things less often.

1.  Work to time

In the worst presentation of the year, the speaker got up in front of 500 people and said “I have too much material, so I’m going to go through this quite fast”. Immediate FAIL. Then, 10 minutes before the end he said “I’m almost out of time, I’ll just go a bit quicker through the last points”.

Conference organisers are usually quite clear about how much time you have allocated. If they are paying your airfare, accommodation and a speaker’s fee, not tailoring your presentation to the timeslot is just rude, and doesn’t help you or the audience.

The best presenters know how much time they have to work with, tailor their presentation to fit the time and then keep an eye on the time. One of the best I saw this year was Jeff Veen at Web Directions – with technical problems at the start he lost 15 minutes and still came in almost on time.

And if you are running out of time, stop. Jump past a couple of slides if you need to make one last point. Otherwise you are saying “I’m more important than you, you can wait until I’m finished”.

2. Leave time for questions

A common behaviour for bad presenters is to run right up to, or over, time, then ask ‘any questions’ (in a rushed voice too of course). No-one asks questions, and the speaker thinks they’ve done a great job.

Great presenters run 10 minutes before time, ask ‘any questions’ and get a ton of hands.

This, believe it or not, has nothing to do with the material. It has everything to do with feeling permitted to ask questions. If there is obviously no time for questions (especially right before lunch or coffee break), the person who asks one is holding up the room. We are polite folks and we know how to play the game – we don’t want to hold up everyone just to ask a personal question. But when there is plenty of time, we feel like we are allowed to, so we do.

And questions are a good thing. They give you a chance to elaborate on something that wasn’t clear, or cover the topic that everyone wants to know but you forgot to include. They help the audience feel like you are approachable and a peer.

3. Know what your point is

I attended many presentations that were well-spoken and well timed but never actually made a point.

Yesterday’s presentation was a perfect example. I spent most of it wondering what the speaker’s point was, and finally concluded that he didn’t know what his point was either. Talks like this waffle all over the place and never get anywhere. And listeners walk away feeling stupid.

If you aren’t sure of your point, do the ‘Why, who cares, so what‘ test. Think about what you’re actually trying to convey, think about why someone needs to know it, why they would care about it, and what the consequences are. This is a simple trick that really helps you think about what you should be communicating.

4. Rehearse

The first time you give a talk, especially if you are using slides someone else has prepared, rehearse it.

Really. Yes, I really mean it.

Rehearsing helps because you hear yourself say the words. You can hear your jokes (I think my jokes are hilarious until I say them out loud), practice stories and figure out the pace. Then when you have to perform for real, your brain doesn’t have to figure it out from scratch.

You can rehearse in your bedroom – it feels odd, but works. Or ask a couple of friends to listen to you. Our local IA cocktail hour has been the rehearsal ground for a few people this year, and we are happy to do it.

5. Avoid self talk

This tip came to me via the very awesome Dan Willis.  We were sitting together watching someone who is super-smart and always has really insightful things to say. And Dan said ‘if only he’d stop self-talking, he’d be perfect’.

Self-talking is all the little things speakers say when they are simultaneously trying to deliver a talk and thinking about themselves doing it. Comments about technology, ‘oops, there’s a spelling mistake’, ‘oh, there’s an extra slide’, ‘what does that point mean’. They can subtly undermine your credibility and make you look inexperienced.

Of all the tips I’ve ever learned, this one has been the most helpful to me personally.

6. Understand your audience

The two worst speakers of the year made the mistake of not understanding the audience. But the reason they were the worst went further – they also assumed that the audience didn’t know anything and needed educating. Guess what – audiences can actually pick up on it when you think of them like this.

Before speaking to a group, find out what they already know and where they are up to with your topic. If you think you might need to explain some fundamental concepts, don’t talk down to people. Just say you are going to quickly go over some background so some key points later on make sense.

But really, the trick to this is to genuinely care about your audience. No matter how hard you try, if you think they are beneath you, they’ll pick it up.

7. Talk about what you know

Another difference between great presentations and mediocre is the presenter’s knowledge of their material. A great presenter not only knows what points they are making, but knows why those things are important and what they mean. They can answer a question on the fly, or elaborate on a point as needed.

You might be caught having to give a presentation on a topic that you don’t know thoroughly, or use a presentation someone else has written. If this happens, rehearse it a couple of times, think about each of the points, why they are important and what they mean. Do some background reading, discuss it with colleagues and think up a story for each of the main points. This will increase your understanding of the material and your confidence.

8. Tell stories

Humans don’t learn by listening to strings of facts. We learn from stories and examples.

One of the best things you can do in a presentation is to tell stories. Make a point, then put it into a real situation. It may be something you’ve experienced, something a colleague has, or your opinion about an issue. Your listeners will understand your point better, and you’ll sound more credible. Win-win.

I tell stories in all my presentations. Sometimes I even completely ignore what is on a slide and just tell a story. The thing I have to be most careful with is that I don’t tell a story twice in one session – how embarrassing would that be!

9. Talk in inverted pyramid

Inverted pyramid is a style of writing where you present the most important facts first, then elaborate on them, then elaborate further. The urban myth is that it developed with the introduction of the telegraph and the need to get the facts through before the connection was lost.

Whatever the history, get your point across, and then build up on it. Your audience can then make a decision about whether to listen to you or do something else (think about sex, read twitter, write nasty things about you on twitter). If you build up to your point essay style, chances are you’ll lose part of the audience part way through and they’ll never get the point you are so carefully working up to.

10. Balance imagery and text

If you’ve been attending presentations for a few years like I have, you’ll have noticed that bullet points have almost dissappeared. The current style, at least amongst the user experience and web folks, is gorgeous imagery and a small amount of text.

Some of the worst presentations I saw this year went so too far with imagery – I kept getting distracted trying to figure out how the image and the speaker’s point related, and ended up missing the point entirely.

Don’t be terrified of text and bullet points. They are OK when:

• the point you want to make isn’t easy to communicate visually
• visual language is the best way to communicate the idea
• people need to see the whole idea in order to understand it
• you are discussing lists of steps or sequences

But if you are going to use bullet points, make them communicate your point. Don’t use them as a memory trigger for what you want to say – that’s what speaker notes are for.

Conclusion

So, if you don’t want me sitting in the third row twittering about how terrible you are:

1. Work to time
2. Leave time for questions
3. Know what your point is
4. Avoid self-talk
5. Rehearse
6. Understand the audience
7. Talk about what you know
8. Tell stories
9. Talk in inverted pyramid
10. Balance imagery and text

More

If you’d like to improve your presentations, my two favourite resources/books are:

• Made to stick
• Presentation zen

Note: I’m going to polish this later, but wanted to get the basics down quickly.

We know that we should do user research for projects. All the user-centred design material says so, we talk about it at conferences, we put it in proposals. We just know that it is a good thing to do.

But when I talk to people about their actual projects, I find that very few people actually do user research. There are many many reasons (no time, no money, already know what users need etc etc etc).

I think that part of the reason it doesn’t happen is also that we don’t have good tools to tell us just how much research to do, and even when it isn’t necessary at all to do research.

In preparing for my Edge of the Web talk, I spent time thinking about that issue, reflecting on some of the projects I’ve worked on in the past and thinking about the factors that led me to push to do research, or to go ahead without.

The factors I came up with are:

• Importance to the business: Just how important is the project/application in meeting organisational/business goals?
• Importance to users: What will happen to users if you mess up. Will they be harmed, or will they just go elsewhere?
• $$: How much is the project going to cost? (i.e. how much will be wasted if you mess up)
• Profile/politics: What sort of profile does your project have? Is there a political implication? (e.g. is the Minister going to get hauled up in Parliament if you mess up. Will your work reflect badly on your industry?)
• Convincing others: How much work will you need to do to convince other people that your ideas are good?
• Existing knowledge: How much (real) knowledge do you have about your users?
• Ability to iterate: Can you make changes quickly if you make a mistake, or is it a one-shot deal?
• Feedback: How easy is it to collect feedback from your users?

Given each of these is a continuum, we can do this:

And then we can think about our projects, and plot where we fall on the dimensions…

Example 1: A personal blog

Example 2: A conference website

Example 3: An e-commerce shopping cart

Example 4: An enterprise-wide core business application