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.
Though you might not think it from the comic, I’m actually sympathetic to questions about tools and process, as I myself am a kind of process junky. I love hearing about how other writers work.
I’m also not someone who dismisses questions about tools with the line “the tools don’t matter.” In fact, I think tools matter so much that if you don’t talk about them correctly you can do some damage.
...What I love about John Gardner and Lynda Barry is that they believe that the tools you use do matter, but the point, for them, is finding the proper tools that get you to a certain way of working in which you can get your conscious, mechanical mind out of the way so that your dreaming can go on, undeterred.
You have to find the right tools to help your voice sing.