Analytics apps don't tell you much about usage behavior. You might be able to see how many users performed an event, or how many times they did it. But none of the analytics packages out there are good at showing you how often people do things. Are they using to-dos once a week? Every day? Only signing into the app once a month but happily paying for years?
Time matters. You can't understand usage without time.
Here I describe an approach for defining new information architectures for large organizational websites managed by many stakeholder groups.
Broadly speaking, there are four general phases to the approach:
Auditing. Begin by immersing yourself in existing content and encourage stakeholders to adopt a critical, audience-minded perspective of their content.
Diagramming. Work with stakeholders to develop new conceptual categories that better serve audiences and organizational direction.
Elaborating. Think through content in detail and test new categories against specific instances and edge cases.
Producing. Prepare content teams for production using a shared database of new sitemap pages and editorial considerations that you’ve developed incrementally.
There are two types of work: growth work and maintenance work.
Growth work involves making new things. It can be something big or small. In either case, growth work often follows a loose process.
Maintenance work is different. Maintenance work involves caring for the resources and instruments that make growth work possible. This includes tools, but also body and mind.
Maintenance is ultimately in service to growth. But effective growth can’t happen without maintenance. As with so many things, the ideal is a healthy balance — and it doesn’t come without struggle.