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.
Years ago a friend of mine had a dream about a strange invention; a staircase you could descend deep underground, in which you heard recordings of all the things anyone had ever said about you, both good and bad. The catch was, you had to pass through all the worst things people had said before you could get to the highest compliments at the very bottom. There is no way I would ever make it more than two and a half steps down such a staircase, but I understand its terrible logic: if we want the rewards of being loved we have to submit to the mortifying ordeal of being known.