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.
A useful analogy for what [Sedgwick] calls ‘reparative reading’ is to be fundamentally more invested in finding nourishment than identifying poison. This doesn’t mean being naive or undeceived, unaware of crisis or undamaged by oppression. What it does mean is being driven to find or invent something new and sustaining out of inimical environments.
I would like to adopt that line as a mission statement: “To be fundamentally more invested in finding nourishment rather than identify poison.”
Because you can identify all the poison you want, but if you don’t find nourishment, you’ll starve to death.