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.
Irwin's thinking was informed by the writings of Alfred Schutz, a follower of Husserl, ...[who] had noted that typification was at the basis of the assumption of the reversibility of perspectives, which was a condition for the possibility of intersubjective experience and the notion of a shared, commonly experienced world. It is also the first step in overcoming the specificity of the individual in favor of knowledge about groups. What is gained by this procedure is an understanding of demographics, but the cost of this understanding is a lack of emphasis on differences between individuals and their unique subjective experiences.