When you start to need IA

Rashmi's comment about outgrowing Basecamp reminded me (with just a bit of schadenfreude) of the IA Summit 2006 buz about how 37 Signals didn't think they would ever need an IA. I wasn't too worried at the time - look, they are doing software design, and they shouldn't necessarily need an IA.

I think Rashmi's issue points out when you do start to need an IA - when the content itself gets large and complex, and when it needs to be created and found by separated people. Now, Basecamp needs some basic info architecture only - to decide what needs the created content will typically have and what tools will help access it. And they need to decide the additions of these access tools will break the simplicity of the tool.

Other thought implied - there may still be a space where the code never needs IA. If web 2.0 is about "small tools, loosely joined", then those small tools need to be IA-independant. It's the joining part - the microformats - where the IA lives.

Hmm, or maybe not. I'll have to mull and then update this.

Next year...

I'm thrilled with the theme for the IA Summit next year, "Experiencing Information". I like it, because I often feel that tactile connection with the information I work with.

But the most important question is whether we can work with AIGA to sponsor an occasional conference - Designing the Information eXperience?

Please?