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.
A primary motivation for creating my Stream was the paralysing sense that a blog post needed appropriate length and weight. Since switching to Kirby, there’s relatively little friction to posting, but there’s definite friction in evaluating a post’s worth to the reader. I’d think to myself, “I’d like to write something about that, but I’ll have to come up with all sorts of extra stuff and dressing, and it’ll take all afternoon.”
And so, I was increasingly aware that I was letting many interesting or essential thoughts go undocumented, allowing them to drift from memory, or exist only on social media, likely to one day evaporate. I’ve become more and more interested in the human desire to document, and it’s something I’ve always valued, so I needed to find a solution that I could entirely control and own. That solution was my Stream.