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.
Districts have to help bring the resources of a city down to where they are needed by street neighborhoods, and they have to help translate the experiences of real life, in street neighborhoods, into policies and purposes of their city as a whole. And they have to help maintain an area that is usable, in a civilized way, not only for its own residents but for other users—workers, customers, visitors—from the city as a whole.
To accomplish these functions, an effective district has to be large enough to count as a force in the life of the city as a whole. The “ideal” neighborhood of planning theory is useless for such a role. A district has to be big and powerful enough to fight city hall. Nothing less is to any purpose.