usability

Recently the topic of complicated versus complex has come up both in relation to a book group discussion I was leading on REWORK and also with an online Twitter-based chat I was moderating on innovation. It's pretty central to everything I've learned, experienced and thought about with regard to design, so it seemed worth it to capture it here.

I've had the honor recently of being asked to moderate discussion of REWORK by Jason Fried & David Heinemeier Hansson (of 37signals) on the Business Innovation Factory's BIF Book Group. I thoroughly enjoyed reading the book, and as with other of their writings, take much of it to heart. They have taken a lot of time and effort to impart a lot of what they've learned over the years in a way that is easy to understand and apply to many more endeavors than just software.

When I woke up Wednesday morning I was looking forward to an always-fun and interesting meeting day on the newschoolyard.com project, for which I'm the platform architect. We're working on a platform targeted at independent schools to maintain their own web sites, parent and alumni communities, and the whole project is really satisfying. Great challenge, great way to help bring innovation (and huge cost savings) to schools.

I know, I know. If you listen to the Boagworld podcast or follow his incessant tweeting and audioboo-ing you'll doubtless be saying something like 'good heavens, don't give him any more reasons to inflate his overblown sense of self-worth' - but I think that he's struck upon a really important topic, and one that has an enormous impact on the future of our industry.

Two workshops today at the Future of Web Design conference: Real-World Accessibility for Web Designers with Derek Featherstone and Design Secrets of Digg with Daniel Burkha. It was tough to narrow down to these two - all of the sessions looked great - but I chose these for important reasons. [I'll be adding more about Daniel's talk in the next day or two - it's too much to cover now!]

While I've been 'away' from posting here, a big change has come about for me professionally: I've decided to leave (add)ventures and start my own web strategy and design consultancy. There's been a huge amount of interest in my work, and it seemed like the right time to move. My role previously was far too focused on just implementation, and this way I'll more often get to bring my full experience to projects rather than only a small slice.

So there it is: the shingle has been hung: web strategist, designer, technologist - now for hire.

I've traded a few tweets over the past day or two on the subject of good books for web professionals. I use that term to avoid 'designer' - as that seemed limiting or possibly a bit arbitrary. I think that information architecture, understanding business requirements and translating them into web site features and functionality, usability/user exerience, interaction design and visual design are all distinct enough that they can be a specialization unto themselves.

I've been working full-time at (add)ventures since late 2007, but thought it would be worth it to share my thoughts on the process of interactive projects. When I was interviewing at (add)ventures I was asked the question 'how do I tackle interactive projects,' and this got me thinking about not just the steps, but the philosophy behind them. While I think this might have been more than was anticipated, I thoroughly enjoyed the process!

Marketing? Corporate Communications? Or is it IT?

It's been a common discussion lately on some of the web design boards and podcasts I listen to. Unfortunately I think there are some significant limitations to all of those choices: Marketing has a primary function of communicating to consumers/end users; Corporate Communications is generally focused on communicating to the media and investors, and IT simply wants to get something done that fills a need but doesn't cause problems with the 'real' concerns of their department.

Drupal is a quite capable platform, and I've used it quite a lot, both for work and for personal projects. Its Achilles heel though is the admin interface - with ultimate flexibility comes a lot of configuration choices. While the simple solution is to tell the client 'just don't look at that stuff' - it's not ideal, and can be intimidating. Enter some key modules: jstools, form_store and formfilter.