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.
Repair is a neglected, poorly understood, but all-important aspect of technical craftsmanship. The sociologist Douglas Harper believes that making and repairing form a single whole; he writes of those who do both that they possess the "knowledge that allows them to see beyond the elements of a technique to its overall purpose and coherence. This knowledge is the 'live intelligence, fallibly attuned to the actual circumstances' of life. It is the knowledge in which making and fixing are parts of a continuum."
Put simply, it is by fixing things that we often get to understand how they work.