For a while we at B&A have been feeling unsatisfied with our software and website. It was perfect when we were young turks, but now that we have a larger body of articles, increasingly richer material, and a growing audience, we know we need something different, something that will tell the world we are a magazine on the rise.
REDESIGN UPDATE Submissions are closed and we are no longer accepting entries.
Thanks to all the folks who worked hard to submit a new visual vision for Boxes and Arrows and for all the great questions and discussion about the redesign.
Little Boxia has just turned two. Look how proud she stands, barely wobbling at all! See how she toddles around, smearing food on the walls! So independent, so curious and wait… did she just say “no!”? No, no, no! Here they come… the terrible twos.
A few years ago, a manager of mine gave me the assignment to work on a five-year career plan. I had never created a career plan before (not even to plot out goals for the coming year), so I was completely unprepared for how and why I should do this.
At the beginning of 2004, Boxes and Arrows, takes a moment to reflect back on the predictions made for 2003 and where we landed at year’s end. Feeling optimistic, we also invited our peers in the community to share some of their professional resolutions for the new year.
A common view of vision is that it’s something handed down by a leader to the troops. When a redesign goes awry, the troops complain, “There was no vision.” But the problem goes deeper than either scenario; the problem is that there was no shared vision.
Wireframes: At once a singular composition and a collaborative expression, communicating the vision of both an individual and a team. As a result, they can be stacked with an enormous amount of detail. Are we becoming victims of information pollution in our own wireframes?
In my experience, I have found that creating and documenting process has been a good exercise to help institutionalize ways of working, to help educate new team members as well as to unveil the mysteries of what we do for executives, product folks, and development teams.
Normally I would write a traditional conference overview to inform people about the recent Designing for User Experiences conference (DUX) held in San Francisco, June 6-8. Instead, I would like to impart a few of the impressions I came away with and recommend that everyone go to the AIGA Case Study Archive to read the papers that were accepted.