Brian Eno is well-represented in iOS. His other apps like Bloom, Trope and Air invite listeners to touch the screen to make their own composition. Reflection ($30.99) is different, there is no interaction for the listener. The interface has three buttons: a pause button, a sleep timer, and AirPlay. Reflection produces endless permutations of Eno’s 2017 album, an hour and five minute long title track.
“Just calling it an app is akin to saying Falling Water is just a building,” writes one app store reviewer. “I would not call this an app,” agrees another, “Between the music and visuals it’s more like sonic architecture.” The visuals consist of slowly morphing rectangles that only seem to change in the split second you look away from the screen.
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.
At least half of the work of design is not design, because design isn’t just "making things"—it’s making things with other people, many of whom usually aren’t designers. This is true any time you’re working with others from a domain outside of your own. Communicating ideas, marshaling stakeholder consensus, soliciting and incorporating feedback, and redefining problems that weren’t fully known at the start are all the non-design work of design, what we might generally call "facilitation."