This speech reminds me of Wilson Miner's "When We Build" talk (vimeo.com). They're pretty different in length, subject, style. But they share (or perhaps I'm hallucinating this) an interest in the obligations that people-who-build-digital-things have to the people that use/absorb them. I think this is interesting, so I'm creating a 'branch' in hopes that other people find it interesting and want to spitball on the topic.
To start: For the next few interactives/software-bits I build, I'm going to try thinking in terms of heartbeats — but what should this mean? I suppose I'll want to make sure I'm not wasting anyone else's heartbeats. But hopefully I'll also try structuring the work around the tempo of heartbeats, e.g., "this part of the visualization should take about three heartbeats to understand, and 10 heartbeats to fully absorb." Perhaps I've jumped the shark.
[This is the weekend, so take your sweet heartbeat-time to respond. Thanks Al, for flagging Ford's talk.]