Boxes and Arrows has been serving the user experience and information architecture community since 2001. Along the way, some pretty big ideas have been developed here by people who are now leaders in the industry. We hope you’ll find inspiration in these posts.
When resources are limited, the design must be optimized to make the best use of all resources. To account for this complexity, it is important to have a clear understanding of both sides of the design equation—what you have to work with and what you are trying to build.
Continue readingHow often do we want to simply make our point, instead of bringing our opinions together to reach consensus? Look at all the PowerPoint presentations and slick brochures: we want to tell our view, instead of listening to others. We want our opinion to be heard.
Continue readingWe’ve all seen blueprints–formally known as contract documents–which architects produce and builders use to construct. No one person knows all the details of the design; the end result is entirely a product of teamwork. But there is one axiom: architects do not build.
Continue readingDesigning web-based enterprise software involves creating complex artifacts like architecture wireframes, object models, screen flows, and clickable prototypes in order to articulate aspects of the online experience for product stakeholders. But what does “craft” mean for interaction designers?
Continue readingDiscussions of how we should label ourselves and define our work are like flu epidemics. They break out from time to time, follow a fairly predictable course, and often make us want to barf.
Continue reading