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.
Let us take a look at how one of these scholars or critics goes about his work. Let’s say he is going to write a commentary on a particular painting. If he is not a man of intuition, certain features will characterize his approach. First he will try to place the painting genealogically, or he will try to define the painting by assigning it to a particular school. He feels uneasy unless he succeeds in doing this.
But more than anything, he is extremely wordy. He seems incapable of speaking of beauty without innumerable layers of adjectives.
One can study an object and note its features, but that only touches the surface. A knowledge of an artwork’s properties does not lead to an understanding of its essence.