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.
My heart belongs to the details.
I actually always found them to be more important than the big picture.
Nothing works without details.
They are everything, the baseline of quality.
Truly functional design only comes from the most careful and intense attention to detail.
Although he did not directly design all products and even had very little to do with some of them, he constantly encouraged tiny improvements that could make a good design better. This attention to detail ranged from the acuteness of angles in forms; the size, feels and distances between switches; the integration of handle fixings; the placement and nature of graphic elements on the products themselves and extended to product photography and packaging.
Designing detail is about achieving a fine balance in all aspects and areas of the product, including those external to the object.