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.
Radić's texts are almost always assemblages of several pieces or paragraphs that, although written by an architect, do not attempt to refer to a particular project or work (and if they do, it is always laterally, avoiding explanations of the how and the why, or demonstrations and apologies).
Like notes from a fragmentary diary or a review of a collection of memories, at times they share the melancholy tone of the writings by Aldo Rossi and at other times they recall the obscure density of John Hejduk's poems.
There are places I will never go. Due to laziness or boredom, or premature fatigue. But there are also landscapes or buildings I should have visited a long time ago. This text reviews those possible places. All of them are part of my story, and they are places I am familiar with in one way or another.