analytics
Time-based analytics
An Article by Ryan SingerAnalytics 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.
Collaborative Information Architecture at Scale
An Article by Brandon DornHere 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.
Craft and Material in Digital Design
A little bit more about the stone
In the documentary Rivers and Tides, artist Andy Goldsworthy repeatedly struggles to stack stones into a sculptural cairn. Over and over the stones fall. Each time, Andy’s sculpture stands a little taller before the moment of failure. At a penultimate moment in the episode, the ever-patient Goldsworthy begins to look exasperated. He’s just staring at the rocks scattered on the ground, studying them intently. A curious passerby has watched him fail a few times, and Andy tells the man, “Every time, I learn a little bit more about the stone. I’m learning how it works.”
It is how we come to understand our medium
There is such a unique quality to experiential learning, through direct experience with a material. It cannot be substituted through lectures or books. It must be felt. It must be earned through time well spent, through making and failing and re-making. It is how we come to understand our medium.
If you’re a digital designer who doesn’t understand basic principles of computer science, or has never written a bit of code, or has never built a website, what are you doing? What can you say about the material you shape?
The idea that designers in the information age shouldn’t waste their time with this skill baffles me. It is woefully misguided advice.
A digital designer who has not learned the nature of their medium is a designer unprepared to argue for their vision. This is a designer who is unable to push back against the criticism of skeptical engineers. This is a designer who risks offering opinions instead of solutions.
If you are crafting experiences in the digital space, you should know what’s required to implement your ideas. You should try implementing it yourself, (if only to build empathy with your developers!)