why simplicity matters

thought “nobody will be blogging this” because it’s a very small conference, etc. 😉

going to be personal. researching operant conditioning at seaworld, car crash with pickup truck. louder than he would’ve imagined.

first thought: ctrl+z. got big laugh.

the tools we’re creating change us. (which is why using IE drives me batty; ctrl+tab does nothing.) ballerina’s toes. a pivot point in the world…we (in this room) are replacing the roles of kings, priests, shamans, in re: creating ritual. “persuasion technology” with great power comes great responsibility.

concerns about persuasion. “how computers can manipulate people”

like fire, good uses and bad. right now it’s like slow torture. not just a nuisance. think how many hours of your month have you wasted on solving computer problems.

the digital products we create will determine the future of this planet. (yes! yes! yes!)

bongo video. (I think this is part of why Mom & Dad A. didn’t want to keep their computer.)

*frustration* — cost is higher than expected and/or benefit lower than expected — resentment, sense of powerlessness.

vs. delight. cheaper or more benefits than expected…can’t always live here, but satisfaction is good too…that point in the middle.

we need to keep our users out of that corner. “radical simplicity”

why simplicity?
# lazy
# limited abilities (40% of american adults are illiterate or semi-literate; his sister would probably fall into that category, as might mine. hi, liz; I love ya, babe.)
# busy
# it sells; fewer examples in the hightech world, but lots in consumer products, look at cleaning products. picking a small/narrow problem and solve it simply.
# inclusiveness
# empower people to do what inspires them
# untouched field, lots of opportunity; either commercially or to do good things

back to the diamond. learning brings costs down. or fun makes things seem simpler, same difference. conclusion from studying video games: secret sauce is instant feedback that you are improving.

gratitude is the healthiest emotion (?)

what gets in the way of radical simplicity? it’s just more work. simplicity is brittle, doesn’t always translate between design and execution, easily broken.

plus cost and benefit are different between people and between contexts. costs: what people hate: giving up scarce resources. (cognitive energy, physical energy, time, money; there’s the other reason…it took way too many of those resources for mom to get any benefit out of computing.)

# research. studying people outside of silicon valley and their experiences with computing. “I just want a [cell] phone that makes phone calls” — he lives in a senior community?
# empathy. can be developed/learned. #1 quality he wishes for from his students at stanford. research can be about developing empathy. being an outcast can be good for developing empathy (is it because outsiders have the dominant mindset all around them at the same time they have their own…thought for later)
# be couragous. add a new feature? get the data to support it! every feature is an opportunity for failure.

grow your freedom…his goal is to create technologies that help people grow their freedom.

OMG…so inspirational!

q: why living in a senior community? was going to be a weekend home, but turned out to be a great place to live, and great interaction opportunities.

q: web as it? research/perspective on creator’s perspective? subjective nature of the user changes perspective on web? no, but he has a story/metaphor. dad makes wooden bowls, gave him a bowl that had fingerprints in the varnish, and that’s what he wanted. you should be proud of leaving those fingerprints.

q: how you teach students empathy? if he shares uncertanties, they open up more. more systematically, pictures with cards, people photos on them. (oh, like that writing exercise from intro to fiction!)

q: how do you get to simplicity? in a few months will be able to talk about case study in detail…lots of user-facing stuff to find key components. “3 things that always came up.” solve for the smallest set. enough talking that you never hear anything new…but what is the commonality? the smaller a chunk you solve for, the better.

q: how to avoid analysis paralysis? he uses external constraints, because it’s too much fun.

q: is anybody making a phone that’s just a phone? he doesn’t know.

q: wanting a search engine for the physical world. 🙂 (more a comment than a question…) simplicity is the way of getting things done that spends the least resources. he wants to Tivo people. (I’m always wanting to blog conversations.)

q: shining examples? can you think of products that are too simple? products he admires: ipod shuffle. jump to research on web credibility (I’ve blogged that at some point) — the more it looked like google, the more credibile it was. “clean” as an adjective.

infocloud

okay, so losing all my notes was teh sux0r, but lunch made up for it. Susan & Brian from Evergreen, Kathy from UW, Denise who used to be at SCCC, and Jay from Dartmouth (!!!). headache is a little better, but I think I went over the top on the caffeine. (go Mtn. Dew.)

personal infocloud, model of attraction. focus of web has changed with the turn of century, from going out, finding content provided by someone else. (ew, ppt with bullet points.)

now I am the center of the universe. 😉 usability, user-centered design. going from navigation to other modes of understanding infospace, which isn’t real space, because you aren’t going anywhere, everything comes to us. but how do you rediscover your personal infospace? or share across uses, devices, etc. scraping info possible because of web standards.

refindability. if you are the center of your information universe, how do you get through it?

sweet drawing of overlapping clouds representing sources of information. personal, global (the whole web), local (intranets, mailing lists, etc.), external (stuff you can’t get. frigging electronic journals).

what a weird chart. I almost don’t understand it. something about repurposing carharts by german skateboarders. (C has been wearing their stuff for years and years. it’s not farmer’s clothing, it’s construction worker’s clothing!)

okay, now it makes sense in comparison with this other chart: our view as designers is that the center is the local/global cloud, and for users the center is the personal cloud. we should be focusing on that center. (how?!?!?!)

properties: person-centered, continuous access (which is why wifi is so important!), organized for self, context-aware.

another presentation talking about reuse & creativity, then. all in the interest of commercial, “make it easier for them to consume” —

okay, I’m going to rant for a sec. is all this reuse stuff just another way of coopting human creativity to fuel the capitalist machine?! are the open-soure web hackery tricks just exploitation? — of the hackers themselves, I mean. it’s the converse of the warm happy feeling I had in the last session, that feeling of connection with other people, and instead the sense of being sucked into the machine. you and your online friends are friends because you both are interested in the same movie trailer. feh.

the utopia and the dystopia of the web are only a hair’s breadth apart.

how do I use this in my context?

model of attraction to replace the metaphor of navigation. receptors: intellectual, perceptual, physical, mechanical.

(I think I’m going to step out and get a drink of water, see if any of Molly’s books are left. short answer: no.)

assessing content. hmmm, maybe there should be a way to subscribe to the bulletin? learn what people do with your content — and what they want to do, or could do.

what triggers people to do something with your content or even get to it?

subscribe to a page?

gaps are an opportunity to improve.

what environments do people need your information in?

structure information for access from the middle, not necessarily the home page. making it easier for people to add your pages to their structure.

I really wish I were learning something about ways to *construct* a personal infocloud for non-webnerds. because this all very esoteric. maybe I should’ve gone to the design session, or even the blogging one.

oh, hey…I just realized: this stuff may make *way* more sense for the intranet than for the public site. after all, most of our students are a short-term audience, but employees stick around for a while, and then we can build bonds internally. ad-hoc portaling? (of course, it doesn’t seem to matter what ideas I have, because the IT people will just decide to buy something, or the CIS people will just decide to do something, and i won’t know about it until it’s all over but the shouting. but you didn’t hear me say that.)

“friendly and easy” — yes! doing something that’s working that used to be broken and horrible.

whew. unfortunately no time for questions.

future of content

Nick Finck, Molly Holzschlag (get Zen of CSS design signed?!), Keith Robinson, “Kevin Smokler”:http://www.kevinsmokler.com/ (haven’t heard of him before, book sounds interesting)

loooong introductions!

what do we mean by content? Molly sez it’s an unanswerable question. communicating a message. Keith: blog is technology, not content. clients who refer to individual posts as “a blog”, same with Flash. Kevin’s content pet peeve: content is not an element of the design!!!!! non-graphical elements. Keith: podcast is format: the words/music are the content. audio as well as text. Molly wonders what the audience thinks.

audience (is that peterme?) — content is what people are coming to your site for. he says blogs are a genre, not a technology. (mmmm. nice distinction.) most people don’t discern design/format from meaning. (yep, that’s him. he’s a freaky-smart guy, because I think he just got right to the center of the thing.)

Molly says as a designer that she’s also thinking when talking about blogging both about it as a genre but also as a technique.

audience: service as a space where *users* create the content. Molly adds that the the service facilitates the production of content. we tend to think sometimes outside the way that users think. she’s getting mad about syndication, and how to understand the presentation of RSS/feeds/etc. Keith talks about the difficulty of explaining RSS; Kevin “if you go to 10 websites a day and the 7th hasn’t updated, then you’ve wasted your time. imagine having a program that will check to see if the sites have updated so you don’t waste your time.”

audience: social interaction? Molly: one beauty of the environment is that it’s not one-way. non-linear, global.

q: concern with blurring between experience and meaning…and the breaking of content as just another site design element. user experiences what the design is. example: delicious user experience; when behind the curtain, it’s meaningful, but otherwise baffling. Kevin: terrible interface! Molly: drive-by. (which is how I use it, too.) as a sideblog. notebook/scratchpad. for what it is, it’s amazing. show of hands: who uses it?

crap. I got all distracted by the mention of the wiki for the conference.

Molly asks if there’s a difference between information and content.

fuck. I just lost all the notes I’ve been taking for the last half-hour…and some of them were really good.

that’s sort of depressing

::sigh::

I’m totally enjoying WV05, once again, but then I looked at the schedule again…27 (?) presenters, 2 women. 7% of the presenters.

Gah.

podcasting

Eric Rice (audioblog.com), Matt May, who’s the 3rd guy?

“automatic delivery of media files” — that’s the best description I’ve heard yet.

sparkcasting…beercasts. sounds like that comedy central show where the guy travels around at night.

“staccato.”:http://staccatomusic.org/ Oh, I’ve seen that one before, I’d just forgotten about it. Oh, the “podcast feed” is just RSS.

Okay, why is this such a big deal?!?!?! It’s just blogging with sound…oh, maybe I should upgrade iTunes…

So it’s switching from the technical to basic how to be a radio person…how to talk, better interviewing techniques. Just keep trying & get better.

“okay, we’re done: any questions?”

radio voices? don’t worry about it! smart interesting people sometimes have lackluster voices, can be more important to be good about having something to say, interviewing, etc.

basically, some people are interested in writing, some people are interested in talking or sharing music. that’s the only difference.

q: how to tell if you’re telling a story well? focus groups, if you don’t see anyone moved, then you’re not doing a good job. (like my old writing groups, or even learning from that performance art class in high school!)

q: workflow? esp. in remote locations? carry a microphone & little tape recorder, brute force method. “as long as it’s audible it’s okay.” (good enough seems to be the motto of the web.)

I missed a question or two in tweaking my notes.

something about audience…the audience of mom & best friend is okay too. (hi, guys!)

“we don’t offer value” — but ministers are using it, here’s my daily sermon. (OMG. I wish my grandpa were still alive; I’m not a Christian, but so help me, I’d subscribe to his sermons.)

q: how is anybody going to make money? most people might not…but big names could. Howard Stern, WSJ? private, niche comment. some people will pay.

q: transcripting, searchability? (from Dartmouth guy in front of me) imbedded talk show in events: transcribe everything. (that’s sparkcasting.) MCMatt is hoping metadata will catch up. iTunes has support for chaptering (in AAC format only). he transcribes himself or gets listener transcription (fanscription) for things with “lasting value.” compares to fan subtitling of anime. capabilities of systems to emerge from community of practice (!!!!!). findability may never be what it is for text, just by the nature of the thing.

podscope, searching thru podcasts. not thru transcription, searching, kinda like OCR for audio. (hmmmmmm.) searching for “umm” 🙂

q: ???? something about repurposing rss.

sexiness of name. audioblogging vs. podcasting. it’s the same fricking thing.

q: do’s & don’ts? don’t play major label music, ask permissions from independents. old model doesn’t have space for it, legally. then a rant about crappy modern radio. no other rules. “ultimately something’s got to give here” (MCMatt) streaming licensing scheme, mechanical reproduction scheme, neither matches the model.

q: where do I find what I want? podcastalley, podcastpickle, odeo, itunes…. depends what you’re into. (is that Keith R. with his hand up?)

q: editing software? adobe audition on PC ($300), audacity (free), garage band (mac only), audioblog.com, audio hijack pro ($30) for interviews with VoIP (and a bunch of other stuff).

q: aggregator issues? RSS playlists? webjay does spif. 3 things will break this out: itunes, IE7, atom. atom allows multiple encloses to be able to do track-by-track w/in a post. rss ubiquity in longhorn. (sigh. joke from dartmouth guy about longhorn in ’09 or ’10.)

q: what about major label stuff with live365? streaming, live stuff. but crappy for what you pay for.

q: rambling questions about alacarte consumption, major media outlets…oh, hey, NPR podcasts. (dude. now I get it. which means yet another thing to suck me into the internets.)

another bit of distraction on my part.

q: how will podcasting develop in comparison to blogging: big money has showed up so quickly? (mhowie) not always going to be participatory (blogging): mh: I find it more intimidating the whole podcasting thing. probably won’t be as many podcasters as bloggers.

webvisions 05 — designing for the sandbox

still trying to wake up. (we had *fun* last night!)

Peter Merholz (yes, peterme…here’s a “link to his slides”:http://www.peterme.com/archives/000540.html for future reference.)

canon powershot camera “we all have digital cameras…” well, maybe. he’s showing iphoto, and it looks strikingly like picasa. why does someone take photos? to share. but it’s a PITA to share.

flickr! and then uploadr. but still a lot of work…

geek in scotland reads api. while he explains what an api is, I get a big drink of my venti 2% mocha.

oh, so it’s an export tool to flickr from iphoto. which made it easy, which made it easy for him to max out his service…so he spent the $25/year to get unlimited storage, 2gb bandwidth.

moral: guy makes tool for free that makes a service easier to use. flickr got more of his money because they allowed that to happen. (…so…what goes the guy get?)

relinquish control! and create a simple architecture. (hmmmm…what nifty things could be done with the book exchange? am I smart enough to write an api?)

flickr got bought by yahoo…hopefully that won’t make them less “open and pure” (pure?!)

the sandbox metaphor: sand is information…the stuff of a service. then drop in the kids. it’s not software but a network…value increased when people can connect to one another. and then tools: what allows people to manipulate info.

philosophy: “let go” (all Alec Guiness stylee — these adaptive path people sure know how to do presentations.)

fun! not a dictated experience.

designers hate letting go. (then again, so do IT people. designer people want to control how it looks; tech people want to control how people use the tech.)

“dirk knemeyer scares him.”:http://www.knemeyer.com/dk.cfm?a=cms,c,292,1

comparison to actual architecture: the getty in LA (someday I really want to go) — how do you work with the space that actually exists.

portals “back in the day” (hahahahahaha. in .edu-land, people are still talking portals all the goddamn time. but I suppose it’s a little different meaning of portal. which is why the term portal sux.) — bumping up pageviews by trying to keep people trapped in their zone. “sticky” — fundamentally user-hostile.

“a white light appears!”:http://www.google.com and they’re doing okay (stock chart graphic).

cw: what’s the value/business model?

hard thing in design: stop larding with features. “if you buy me a beer I can tell you some stories” (hmmm, do I have enough money to buy him a beer?)

“when you reliquish control, you receive value”

“5 planes.”:http://www.jjg.net/elements/ (JJG) up from the bottom:
# strategy: goals
# scope: what are we doing?
# structure: IA
# skeleton: interaction design
# surface: visuals

abstract to concrete. and the duality of the web: software vs. hypertext. and now the diagram gets *really* complicated!

so at each level….

# surface: the obvious stuff: don’t take over. allow skinning if appropriate. be simple. example: flash guide to tent buying. cute ad, but not really useful…excels as production, but not as service.
# skeleton: don’t be too clever. calif pizza kitchen. lost his network connection…. “why don’t they have open wireless at a goddamn web conference” and ew, that is kind of a dorky interface.
# structure: the problem of hierarchy. which way do you get to recipes? allrecipes vs. epicurious. faceted classification. (is there a way to do that on *our* site? might be fun to try a different navigation method.) gah…tags. sony imagestation vs. flickr. folksonomy. increasing meaning. dmoz vs. delicious. (I showed “my delicious”:http://del.icio.us/epersonae to Susan.) we hate the term usability, but that’s what people apply to us. (mmmmm…tagging as market research?!)
# scope: what is the sand in the sandbox, what are the tools? anatomy of the long tail. (what is the least popular song on Rhapsody?) wired article: amazon sold more than half of its books from stuff that b&n (physical) doesn’t/can’t carry. relationship to control? we’re not going to tell you what’s most popular: buy anything! google maps: go have fun, play. mashups. (again the mention of hacker types not being able to make money out of these things…)
# strategy: netflix! the long tail. relinquishing the control of late fees.

2 minute warning…craigslist: 1/5 of traffic of ebay, 18 employees vs. 8800. using community to help making decisions.

why doesn’t B&N have a dating service? problems with blockbuster & no late fees. walmart realized they couldn’t do video rental online: not nice but smart.

what about convergence? we don’t know what else is going on…either online, or in reality. not convergence but *divergence* — yes!

he has bullet points, but there’s no time.

for the HEWD people

here’s my conference notes category: http://www.epersonae.com/ew/index.php/categories/hewd-2004

(I don’t usually use categories here, so there’s no listing for it in my archives.)

these notes represent my summaries, intuitions, inspirations, and opinions. they are certainly not either a transcript nor an authoritative record. oh, and I’m an opinionated bastard.

also, at some point, I’ll clean it up and post a version more like my webvisions notes from this last July.

best of track: a class (year) site

came in a bit late. 2 guys from URochester. I can see why this did so well in the reviews: they have a good presentation style, maybe one of the best I’ve seen all week.

establish unity, provide communication, basic resource.

URL sent with admittance letter. content added as needed.

first done for class of ’05, started in their sophomore year (was then an incoming student site). that would’ve been 2002, I think. class of ’07 was launched 4 weeks before start of school (2003); ’08 got the early date like they described up front.

this is definitely aimed at the four-year process; I’ll be listening for things we can do in *our* environment, which is significantly less uniform.

calculation of “creative hours” which is a growing trend, but levels off now, because they know what they’re doing. 🙂

benefits, started by calculating site traffic. drawing people back by adding info gradually.

used Yahoo groups, then converted to an inhouse message board where students’ user ids were the same as email addresses. nice.

quotes from faculty/staff on the success of the project. parents said it reduced stress. downward trend in phone calls with questions, quote from orientation staff. heading off questions before they’re asked.

going thru look/feel of various years. 2nd one had a calendar as the centerpiece.

they did some work to sell on having a look/feel that’s different from the main templates, with the goal of differentiating from previous/next years.

all done with Dreamweaver/Fireworks/Photoshop. no dynamic stuff. student/volunteer webmaster in coordination with “dean of freshmen” (?!) also head of orientation.

asked us what we’d wanted to know before we got here. (51% of their students are out of state)

then added more staff, brought in admissions office. lots more content, communication opportunities, downloadable forms.

then added orientation system using college-wide login for filling out forms electronically.

q: why not just use a portal? (so much obsession with portals!) most of their staff is focused on getting content. followup question: keeping it going after the start of school?

had to use school colors for the ’08 site.

(ugh. this is interesting on its own merits, but only vaguely related to our environment. and that spot inbetween my thumb & first finger is starting to ache. weird stuff with using the trackpad, I think.)

they upgraded to CSS2, but forced people to upgrade browsers. said nobody had problems, but I just don’t see any reason why they should’ve.

more technical & content improvements the next year. more connections between depts. moved to PHP/mySQL. selling the university…used article about the class site in promotional materials for prospective students.

class site hand-off…their goal is not for an incoming students site, but for a site that’s connected to the actual class. they hand it off on Sept. 1 to Student Activities. they get to keep the site until the very last person in the class *dies*. jesus christ on a crutch.

ew, he just quoted back the idea that gets slammed in “conference presentation judo”:http://perl.plover.com/yak/presentation/samples/slide001.html — which I used to some extent as my guide for my presentation.

some wireframes of what they’re looking at for next year. quick facts, live weather, rss (! “we don’t touch it, it changes daily, we like that”), hot topics (from the message board).

highed.dulongvanscott.com

q: who gave signoff on showing weather? wow, weather is a big deal here.

q: what about transfer students? a lot of info works for them, but they also can use the orientation site. (I’m not thrilled with their answer.)

q: what does your site look like now? (to one of the students) not too bad.

I’m finding the discussions related to non-standard students, not just transfers, but 5-year (engineering majors).

q: what about content policing? no administrators moderating. these two guys moderated. followup: student life questions, who answered? some other year students, but they gave some misinformation.

my q: were students informed of policy? yes, and it’s their basic acceptible use policy.

q: how did you find problem messages? he was just there all the time.

I’ll need to think about how/whether any of this has an application to us.

best of track: conversion to web standards

Daniel from UWisconsin Platt
http://www.uwplatt.edu/web/webstandards

talk about changes in methodology, along with concepts, reasons to make the switch.

zen thing: is standards, aren’t standards.
if you think of the W3C as the UN… if the countries in the UN don’t want to play well, they don’t. but the UN at least has an army; maybe the W3C should?

XHTML, CSS, DOM, ECMAScript 262 (he keeps pronouncing ECMA as a word rather than an acronym, makes me crazy)

“HTML is dead.” (okay, whatever.) if there’s no HTML, then what the heck is XHTML? (digression: SVG got merged into XML) huge freaking quote on what XHTML is.

how to convert to XHTML: doctype, lower case, quoted attributes, end tags everywhere, proper nesting, validation. “validate first before you ask me a question; it’ll save us both a lot of time.”

benefits? accessibility (at least more so), eliminate silly mistakes — works well in old browsers, because it’s tight (my word) no guessing needed.

XHTML is our future, moving from HTML to XML. now he’s tripping; XHTML 1.0 transitional/strict is doable I think for most people, but 1.1?! and talking about 2.0, you might as well be smoking crack.

q: why transitional? I don’t know about his answer.

HTML structure. most corporate is going to use table design (except not so much anymore): nice layout, predictable. hard to find stuff (although his example is faulty, I think, because it’s the kind of thing that would likely be drawn from a db). don’t do it.

div is alternative to table. huh? this sounds like the road to divitis. separation of structure from layout/presentation. divs as the skeleton.

*now* he says don’t overuse, talks about divs for major sections.

browsers: as long as we point back to W3C, we should be prepared. rant vis a vis WYSIWIG editors, the “hi mom” effect: HTML generated in word, which makes Baby Jeebus cry.

then CSS “skinning concept” like face plates for a cell phone. “we just swap out the CSS” — well, in the best of all possible worlds. 1st css design is painful, but then redesigns are easier, faster.

ah, the zen garden; he mentions Dave & Molly’s book.

suggests using lots of stylesheets: base, @import, layout “separate from skin” (huh?), print.

print view of Slashdot. didn’t the user just want the content? I wonder about print stylesheets: they’re a sweet idea, but do “average” users understand the idea?

“information superhighway” not “design superhighway” (photo of Al G) info should come first, design isn’t important. hrm.

backward/forward compatible. ready for the future!

he very briefly alludes to the slashdot makeover. (in ALA?)

bandwidth savings.

oh, hey, he’s the guy who *wrote* the article about redoing Slashdot with web standards. he’s talking about that now, but then again, I read that article when it first came out. talks benefits: not originally impressed with bandwidth savings 2-9 K…but it adds up. 14GB daily.

personal bandwidth story. freakout by server people because of drop in load with CSS implementation. y’know, we’ve done this so gradually, and without ever really having done a big-ass table design, that I can never show those kinds of numbers. sigh.

a journey not a destination, not a quick fix, but lots of benefits.

tells how he ended up writing the story for ALA. “I thought you were kidding.” and getting slashdotted. 🙂

recommends Meyer’s definitive guide to CSS, talks about speaking with Eric. more books, Zeldman, More EM on CSS.

he has 12 minutes, so he’s going to…demo the FIR technique. I mentioned the negative margin technique. (Dave Shea has a whole page full of techniques.)

demo also of a student project, another rework, playing with firefox web dev extension. (which rocks my world)