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 walked around with a map, penciling in X’s wherever there was a barn or shed. For the next three days, I covered four kilometers in all four directions. Living toward the outskirts of town, there are still a good many farmers in the vicinity. So it came to a considerable number of barns—sixteen altogether.
I carefully checked the condition of each of these, and from the sixteen I eliminated all those where there were houses in the immediate proximity or greenhouses alongside. I also eliminated those in which there were farm implements or chemicals or signs that they were still in active use. I didn’t imagine he’d want to burn tools or fertilizer. That left five barns.