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.
The demand for “originality”—with the implication that the reminiscence of other writers is a sin against originality and a defect in the work—is a recent one and would have seemed quite ludicrous to poets of the Augustan Age, or of Shakespeare’s time. The traditional view is that each new work should be a fresh focus of power through which former streams of beauty, emotion, and reflection are directed. This view is adopted, and perhaps carried to excess, by writers like T. S. Eliot, some of whose poems are a close web of quotations and adaptations, chosen for their associative value, or like James Joyce, who makes great use of the associative value of sounds and syllables.