Quick Reset: Design & IA

100 Days Project — #42

This is my first work-related post in a bit, so excuse me as I jump from general musings to specific reflections on designing for the web.

This week we worked through key designs for a project which has been quite frankly, a huge stressor. I’m all for a difficult challenge, but that usually comes with the caveat of having enough budget to get the job done. This project had minimal information architecture budget, so we moved right into design phase with a site map, but no wireframes or further indicator of user pathway or content outline.

As a result, I’ve had the privilege of working more closely with our designers in this abridged version of IA, as we’ve made decisions in minutes which would usually take hours or days.

After our latest wire-on-the-whiteboards session, I reflected:

• Information architecture will happen in the process, whether there’s a budget for it or not. There will never be an instance where user pathway does not affect design decisions.
• Whiteboards are just as effective a medium (as digital) for wireframing, particularly if you need to quickly retrace your steps and remold your thoughts.
• If you feel you’re in a rut, write down the objectives of the page in order of priority. Anything on the page that negates the goals, or does not meet and reinforce the goals does not belong on the page.
• Show how your designs meet the objectives, and keep this at the forefront during the presentation.
• IA is a collaborative process which benefits from multiple heads together in the same room. Whether for 15 minutes, in large chunks, or at set increments, strategies are most effective when silos are broken down early in the process.

More quick resets are on the way soon, and I’m out!