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.
In conventional agriculture, vegetation is kept at the weed or herb level using energy to keep it cut, weeded, tilled, fetilised, and even burnt; that is, we are constantly setting the system back and incurring work and energy-costs when we stop natural succession from occurring.
Instead of fighting this process, we can direct and accelerate it to build our own climax species in a shorter time.
There is no attempt to form the garden into strict neat rows; it is a riot of shrubs, vines, garden beds, flowers, herbs, a few small trees, and even a small pond. Paths are sinuous, and garden beds might be round, key-holed, raised, spiraled, or sunken.