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.
I’ve written this before but I constantly need to remind myself of it, so, once again: A certain kind of work, lifestyle, mode of living — in and of itself — is protest. That is, work that is curious and rigorous is implicitly an antipode to didactic, shallow bombastity. It is inherently an archetype against bullshit. That to be committed to this work or life of rigor (be it rigor focused on “art” or, as they say in Japanese, sakuhin, or family or athleticism or whatever), and to share it with the world is to opt-out of being paralyzed by idiocy, and help others who may be paralyzed find a path back to whatever fecundity of life it is that they deserve.