- Information Architect (August 8, 2011)
I've been an information architect since 1994. This means I've put in my 10,000 hours several times over, and earlier this year, as I pondered my future, it invited some soul searching around the following questions:
* Am I getting better?
* Should I do something else?
My analysis began with a look back at the work I've done in recent years, which includes consulting projects and relationships with Fortune 500 corporations, e-commerce startups, government agencies, foundations, universities, libraries, and publishers. In this retrospective, I focused on what's timeless and what's changing in the work that I do.
What I Do
First, classic information architecture (IA) remains central to my work. Demand for the structural design of websites, intranets, and interactive services continues to grow, driven by the challenge of creating search and navigation systems (and the underlying taxonomies and metadata schema) that enable users to complete tasks and find what they need.
However, the context in which I practice has changed dramatically. The dance between Google and search engine optimization (SEO) has shifted attention from "home pages" to the design of findable, social objects that serve as both destination and gateway. The rise of user-generated content has invited the marriage of architectures and algorithms in support of conversation and collaboration. And, the growth of mobile has us thinking hard about Responsive Web Design and Ubiquitous Service Design in a world of cross-channel user experience.
As an information architect, I'm finding this complexity of context creates opportunities beyond the borders of information architecture. Increasingly, I'm asked by my clients to formulate a "web strategy" that explains relationships between their sites and social media channels, and these conversations naturally lead towards development of full-blown strategies for mobile and multi-channel user experience as well.
This strategy lays the foundation for a "road map" that describes roles, responsibilities, requirements, and the sequencing of activities. At this point, I help my clients to identify skillsets and specialists to fill gaps in such areas as governance, content strategy, and technology integration. The ensuing collaborations are often tremendously productive and fun.
Value and Values
After reflecting upon the evolving content and context of my work, I turned from what I do to why. An obvious answer is that I'm paid well to work with smart people on interesting, important projects, and in this I recognize that I'm very fortunate. But what about my value to my clients and end-users and my desire to make the world/web a better place?
I've always been proud of my work for the National Cancer Institute. We redesigned the site in 2003 under serious time pressure, and it went on to win awards and rise to the top of the E-Government Satisfaction Index. And today, 8 years later, while the design and content have changed, the information architecture remains the same. I'm not sure that's entirely good, but it is validating to have had a lasting impact.
Recently, I've worked with the Library of Congress to develop a web strategy and an information architecture framework. It's been a real honor to serve the world's largest library. The work has been difficult, due to both the massive scale and the humbling sense of responsibility. Now, I look forward to the rollout of improvements that will advance the Library's mission "to further the progress of knowledge and creativity."
Of course, not all projects carry such moral weight, and yet there are always opportunities to teach and inspire clients, and to help users by designing for better usability, findability, and accessibility. And, I'm also exploring ways to design for learning, literacy, and understanding. It's rewarding to bring not only our value but our values into our work.
To Be an IA
Having pondered what and why, I returned to the two questions:
* Am I getting better?
* Should I do something else?
I think my answer to the first is Yes. After nearly two decades of consulting, I'm able to identify the right fit for an organization. Experience improves my ability to know what will and won't work. Plus, my credibility and confidence help sell solutions to difficult audiences.
I know my answer to the second is No. Looking backward has convinced me to be an information architect moving forward. Given my love of strategy, design, and systems thinking, it's the perfect vocation.
However, this raises a new question. How do I explain my role as an "information architect" when the context keeps changing?
Let me first note that I don't care about job titles. In my mind, everyone is an information architect, at least some of the time. For instance, it's often the crazy entrepreneur or the executive with a vision who sees how to unify multiple platforms into a new cross-channel experience.
But not every company has a Steve Jobs. Usually, this challenge must be met by a cross-functional team. However, it's hard for these folks to shift frames from inside-out to outside in. An information architect can help by employing user-centered design and multi-channel maps to show what's possible when we think and plan outside the org chart.
This idea of the information architect as mapmaker is powerful. In fact, this tweet captures how I explain my role to myself:
I'm an information architect. I map paths and places across physical, digital, and cognitive spaces.
Of course, this is a bit abstract for an elevator pitch, but it helps me think more creatively and expansively about how I can help my clients.
Similarly, I often find it useful to assume the mantle of a bridge builder.
For instance, an information architect builds bridges between:
* Users and Content. We design search and navigation systems that connect users with the content and services they need.
* Strategy and Tactics. We translate abstract visions into well-grounded, actionable blueprints for design and implementation.
* Units and Disciplines. We facilitate cross-functional collaboration using boundary objects (e.g., wireframes) to start conversations.
* Platforms and Channels. We sketch maps for new services and experiences that span multiple platforms, channels, and media.
* Research and Practice. We use the scientific method, heuristics, analytics, user research, and ethnography to inform our designs.
As you can see, I enjoy these exercises in framing, which is good because defining the damn thing is central to what we do. And, the task only grows harder as tech spins faster, which is precisely why I believe that there has never been a better time to be an information architect.