The following seven principles are from a book called A Pattern Language by Christopher Alexander et al., and they describe the method by which builders should implement the “patterns” laid out in subsequent chapters of the book. The patterns used by the book are essentially design guidelines, and they range from exceptionally broad (creating rings of similar density throughout a town or region) to exceptionally specific (having multiple types of chairs within a common space). It’s a rad book:
- The region is made up of a hierarchy of social and political groups, from the smallest and most local groups – families, neighborhoods and work groups – to the largest groups – city councils, regional assemblies.
- Each group makes its own decisions about the environment it uses in common.
- Each of these groups takes responsibility for those patterns relevant to its own internal structure.
- Each neighborhood, community or city is free to find various ways of persuading its constituent groups of individuals to implement these patterns gradually.
- Implementation should be loose and voluntary, based on social responsibility, and not on legislation or coercion.
- Experts use patterns to inform their construction of lower-level places, using any higher patterns that the community has adopted.
- It is possible for individual acts of building to begin working their way toward communal patterns before neighborhood, community and regional groups are formed.
All are a reminder that the stuff we all ramble on about today – when talking about building successful communities online, etc. – is old news once the sheen of digital is washed away.
Alex and I are nearing completion on our Web 2.0 deck. Which is a good thing, considering we’re presenting it Thursday.
Here’s what it’s going to look like. I’d love your thoughts.
Option 1: Looks nice. Unfortunately the hidden reading is, “Clay Parker Jones does Alexander Chung.” We’ll leave it out.
Option 2: Vertical. Clean.
Option 3: Funnel. Clearly implies that we’re talking about things being small rather than big.
I’m really happy with the title cards for each of the key story sections. I traced some Clarendon numerals for these and they came out pretty killer.
The infographics are starting to come together. Also… I think the above is pretty remarkable. $92MM in profits off of a circulation of 1.4 million? Nutty.
I’m also really happy with the “statement” slides. I think we’ve got a good thing going here.
Alex and I got accepted at Web 2.0 Expo, and in that fit of excitement, we came up with an idea for a SXSW talk.
We’re calling it: “People are Stupid, and How to Fix Them.”
Our over-dry description of the discussion:
There is nothing more certain than our ability to mess things up. We repeatedly make irrational, ignorant and naive decisions, fumbling through life with a broken compass.
Strangely, technology isn’t helping much. In interactions with people and things through a digital layer, our ineptitude is reaching a zenith. (And we mean more than Fail Blog.) Misplaced passwords, scammyness, broken check-in systems and lost trust are just some of the digital disasters affecting our success as a species.
We will present findings from in-depth interviews, site analytics from major online platforms, digital/real life ethnographic studies, and scholarly works to show how systems continually break under the weight of the human error.
These findings include remedial strategies and design recommendations – from button locations to business structures – to account for the digital dunces of the world.
Who it’s for:
This session will be perfect for anyone who designs things at any level (from user interfaces to user experiences), or considers design an important part of their business. Small business owners, entrepreneurs, media folks, and other strategists will also love the session.
- What are some common errors that occur within digital experiences?
- What is the state of digital aptitude and how can we design for varying levels of ability?
- How can we take 15 minutes off an airline passenger’s waiting/queueing time with digital?
- What’s wrong with my website visitors and why aren’t they using my site correctly?
- Why is Farmville so popular?
So when the Panel Picker comes out, vote for us!
An outline for something I’m writing for someone else.
An outline of something I’m writing for me.
I mentioned to a friend the other day that I had already erased around 500 words, without having even written a single one. A lot goes on upstairs, but when it’s time to put pixels to paper (?), nothing beats an outline. And for me, whiteboards are the best.
Bonus round! My outline for Planningness:
That’s how I write presentations. Mildly crazy, but a single page always works for me.
I’m talking this week at the Planningness Conference in San Francisco. I’m talking about the experimentation imperative within digital marketing agencies.
I’m talking about how traditional advertising got to be good, and how we can all work to improve digital marketing/advertising/whatever.
I’m also going to talk about two really interesting tropical storms.
You’ll have to wait until later to see more about these storms, but if you want to read up in advance, check out the STORMFURY and POPEYE wikipedia pages. Note: I’ll be changing the title to say, “Project” rather than “Operation”. Sorry about that.
And lastly, I’m going to talk about why we all need to be experimenting with things on the internets outside our client obligations. And even more importantly, why we have to share data with each other to make all our digital things better for the people. Because right now—and I hate to say this—we’re not doing consumers much of a service with the things we’re doing online.
If you have any examples of interesting digital experiments that you’ve done, send them to me. I’ll present them at the conference.