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.
Rain chains are a beautiful and functional alternative to traditional, closed gutter downspouts. Guiding rain water visibly down chains or cups from the roof to the ground, rain chains transform a plain gutter downspout into a pleasing water feature. From the soft tinkling of individual droplets to the soothing rush of white water, they are a treat to listen to.
Rain chains (‘kusari doi’ in Japanese) in concept are not a new idea. For hundreds of years, the Japanese have used the roof of their homes to collect water, transporting it downward with chains and finally depositing the rain water into large barrels for household water usage. Japanese temples often incorporate quite ornate and large rain chains into their design.