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.
If we reach such a very ordinary state of daily life, and then back it up with building and construction that comes from the depths in us, then that gradually accumulates our value in the world, all of us together as a whole. Later, then, perhaps hundreds of years later, people will look back at our stones and say to themselves, "My word, those people way back then — they certainly knew how to live," and they would say this because they could see the lingering whispers in the walls and mosses, and could read them, and could treasure them, and would learn from these traces how to live like that again.