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.
How the Blog Broke the Web
Homepages had a timeless quality
On the early web, there were thousands and thousands more personal homepages than weblogs.
Homepages had a timeless quality, an index of interesting or useful or relevant things about a topic or about a person. You didn’t reload a homepage every day in pursuit of novelty. (That’s what Netscape’s What’s Cool was for!)
Chronological content was in the minority.
When Movable Type ate the blogosphere
Here’s the crux of the problem: When something is easy, people will do more of it.
When you produce your whole site by hand, from HEAD to /BODY, you begin in a world of infinite possibility. You can tailor your content exactly how you like it, and organize it in any way you please. Every design decision you make represents roughly equal work because, heck, you’ve gotta do it by hand either way. Whether it’s reverse chronological entries or a tidy table of contents. You might as well do what you want.
But once you are given a tool that operates effortlessly — but only in a certain way — every choice that deviates from the standard represents a major cost.
Movable Type didn’t just kill off blog customization.
It (and its competitors) actively killed other forms of web production.
Reverse chronology bias
Once you’ve had a taste of effortless updates, it’s awfully hard to back to manual everything.
So they didn’t.
And neither did thousands of their peers. It just simply wasn’t worth it. The inertia was too strong.
The old web, the cool web, the weird web, the hand-organized web… died.
And the damn reverse chronology bias — once called into creation, it hungers eternally — sought its next victim. Myspace. Facebook. Twitter. Instagram. Pinterest, of all things. Today these social publishing tools are beginning to buck reverse chronological sort; they’re introducing algorithm sort, to surface content not by time posted but by popularity, or expected interactions, based on individual and group history. There is even less control than ever before.
There are no more quirky homepages.
There are no more amateur research librarians.
All thanks to a quirky bit of software produced to alleviate the pain of a tiny subset of a very small audience.
That’s not cool at all.