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 human maker, working in unself-conscious matter, receives no worship from his creatures, since their will is no part of his material; he can only receive the response of their nature, and he is alone in fault if that response is not forthcoming. If he tortures his material, if the stone looks unhappy when he has wrought it into a pattern alien to its own nature, if his writing is an abuse of language, his music a succession of unmeaning intervals, the helpless discomfort of his material universe is a reproach to him alone; similarly, if he respects and interprets the integrity of his material, the seemliness of the ordered work proclaims his praise, and his only, without will, but in a passive beauty of right structure.