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.
Because the approach to the room is along a long corridor, the attentive visitor might at first think that three light squares had been affixed to the windows or, as one gradually came closer, that the tinting of the windows had simply been removed in these three lighter near-square areas. Davies continues: "only at this point do the other senses kick in. The visitor begins first to hear and smell the ocean and then to actually feel the outside air entering the gallery; this sensory experience is in complete contradiction to the faulty first impression."