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.
Taking notes has always helped me zero in on the interesting questions.
In taking field notes, the way to find these peculiarities is to keep track of as many observations that may not appear at the time to be relevant at all.
I’ve been keeping journals of one sort or another since I was a teenager, and if there is one thing I can now confidently say about all this scribbling and note-taking, it is that if it wasn’t written down, it didn’t happen. The more I wrote the more that did happen, because all this process stirs up ideas. Stopping to sit and write costs time and energy, and some biologists feel that it should be discouraged.
Note-taking helped transform me from a young boy on barefoot runs who passively observed the tangled bank of the Maine woods into a naturalist-scientist who is an active participant in unraveling the mysteries of the natural world.