Showing posts with label webvisions. Show all posts
Showing posts with label webvisions. Show all posts

Notes on Data Visualizations by Des Traynor


This was a highly visual presentation (as you'd expect), and so there's only so much I could capture in notes. I suggest you check out Des Traynor's blog: http://blog.intercom.io

Data Visualization
Des Traynor
  • hard to make visualizations better than text
  • especially hard to make them work good on mobile, desktop, etc.
  • Be clear first and clever second. If you have to throw one of those out, throw out clever. — Jason Fried
  • Lots of examples of bad graphics:
    • unemployment rate: sloping lines in the reverse direction of the data
    • gas prices: different units of time (year vs week)
    • gulf oil spill: 
  • Who’s the level?
    • CEO level: high level
    • Analysts: trends
    • Operations/logistics: Is anything going wrong? traffic going in the right direction?
  • What department?
    • Sales: leads, conversions
    • Marketing: impressions
    • Customer support: satisfaction rating, number of issues
  • These two (level and domain) together tell you what needs to be presented
  • Six Things to Communicate
    • A single figure: a bank balance, server status
    • Single figure with context: number plus sparkline
    • Analysis of a period: a good line chart
      • Never imply precision you don’t have. e.g. for four months of data, use a bar chart, not a line chart. 
    • A common error in visualization: to force the processing on the user. If we want to look at the delta between sales and target, don’t show the numbers for each, show the delta.
      • awesome example of using cycle charts to display user retention over time by cohort analysis
    • Breakdown Over Time
  • Lying with grouping
  • Lying with rotation
  • Bar charts aren’t sexy, but they rely on an innate skill: following a line
  • When picking visualizations, use innate skills
    • determining height
  • Tufte principles:
    • Chart junk: minimize anything that does change when the data changes
    • Data Ink ratio: how much of your ink is showing something useful?
    • Smallest effective difference: the least you can do to highlight
  • Ryan Singer: HTML has a strong tag, but no weak tag. As a result, we forget to think about what we need less of.
    • Remember to quiet down your less important parts
  • Visuals should say something: some narrative or point.
  • Visuals should all be created in HTML
    • Highcharts is a Javascript library is excellent and worth the money
    • Flotr2 is new, but popular
    • D3 is immense
    • Rickshaw
  • References:

Crystal Beasley on 13 Signs Your Site Needs a UX Exorcism


Crystal Beasley (@skinny)
#wvpdx webvisions 2012
  • “I’ve got this really great idea for a site.”
    • sometimes they are, sometimes they aren’t.
    • The Post-It note: the innovation is the glue. But then design comes in and plays with it.
    • Observation of behavior: if we cut them smaller, they can be page flags. people won’t write on them, they’ll just place them in.
      • That’s not a technological innovation. it’s a design innovation.
  • “I’ve got this really great idea for a feature.”
    • For every feature you add, the UI complexity goes up (exponentially).
    • A simple cooking web site: shows one recipe, refresh to get a different recipe.
      • Very successful. Got a book out of the the deal.
  • “Let’s put a sentence under the button to explain.”
    • When you get to the point where you are trying to explain your way through a user interface, it’s time to back up.
  • “What we’re doing here is so novel.”
    • Not usually true.
    • Even when it is true, you want to make use of existing design patterns.
    • e.g. see the yahoo user experience guidelines for pagination.
  • “I think the button should be on the right.”
    • Too many decisions are made on gut decisions.
    • “I think” is the least effective way to make that decision.
    • Don’t be a slave to your data either... Use data to inform decisions.
  • “I don’t want the user to do the thing they want to do.”
    • It doesn’t usually sound as simple as this, but this is what it boils down to.
    • maybe it is because it is counter to what your business wants, maybe it is because it is technically challenging. but you can solve it.
    • Maybe it is contacting support. (because it costs money)
    • But you have to help your customer. you have to help them do what they want to do, or you are alienating them.
  • “Maybe we need a FAQ”
    • better: give them bite-size bits of content where they need it, instead of a huge data-dump.
  • “Can’t we just pop up a confirm dialog?”
    • They interrupt too much. They are too harsh.
    • Instead, just support “undo” for whatever the action is.
  • “Let’s split this up into different steps so it seems smaller.”
    • The better approach: cut everything that isn’t absolutely essential out of the forms so there is less information to complex.
    • Recommended book: Web Form Design
  • “Make it red so it will really stand out.”
    • Then it becomes impossible to delineate what really needs to be paid attention to.
    • If you really must use red on your site, then you can use yellow for errors.
  • Navigation
    • Information Architecture
      • really important, takes time, taking learning vocabulary
    • Structural navigation: what does on what pages and how do we get there?
      • decisions are often made before a UX person gets involved.
      • Every single page should answer the questions: who are we? what are we about? where you are on the site.
  • Copy
    • Please don’t talk to users like they are a robot.
    • Error copy is particularly bad.
    • Read your copy out loud to a friend.
    • Does this sound like a sentence that one human being would say to another human being?
    • If you must have the dry robot speak, bury it under an a “more info” link.
    • Data
      • Plugins vs Extensions: Users don’t know the difference, and by dividing them into those two terms, if just confuses users.
      • Research technique: “card sorting”.
        • Put topics on cards, ask users to sort into categories and name those categories.
      • If your website organization mirrors your organization chart, then your navigation is definitely not working.
    • Jakob Nielsen Eye tracking chart: http://www.useit.com/eyetracking/
      • it’s an F pattern normally.
      • So keywords must be toward the top and to the left.
      • If the first few words of every page are the same or not useful, then you are forcing the user to have to read further, and they will miss the keywords.
  • Login
    • Did survey of top 100 sites: 
      • 90 out of top 100 sites: you can use all of the meaningful content and features of site without login
    • Make everything you can open on your site.
    • Login only when it is essential.
    • Otherwise, they will bounce away.
    • Don’t be greedy.
    • Gradual engagement is the term for this. http://www.lukew.com/ff/entry.asp?1128
    • “Remember me” checkbox
      • Login is not about security, it is about recognizing the face of your friend.
      • Do everything you can to remember your users.
      • Are you going to be like a bank and timeout after 20 minutes?
        • a 15 minute cookie does help protect the user against internet cafe type intrusions.
      • Are you going to have a 24 hour timeout?
      • Having a 24-hour session cookie vs. a 4 week session cookie doesn’t really buy you any security.
      • So either do a 15 minute timeout (if you are bank level security), or do a 4 week or forever cookie.
      • Amazon remembers you forever. But for the critical stuff (e.g. to change shipping address), you have to re-auth.
      • Facebook remembers forever. Google remembers for many weeks.
      • Best practice:
        • Remember forever/long time
        • Re-authenticate for anything critical.
    • Question:
      • Q: Does using Facebook authentication reduce friction?
        • Yes, reducing friction.
        • But, huge variability in user populations.
          • Some people love it, use it for everything.
          • Some aren’t crazy about it, would rather have their own login.
          • Then there’s the tin-foil hat crowd.
      • Q: Example of a perfect site?
        • Mint.com is really good.
        • BankSimple is doing some good UI stuff
        • OKCupid: gets the subtles of the UI right. Really good polish. The way they engineer interacts on the site so get value on both sites: the user gets value and the site gets value.
  • Q: Are carousels useful?
    • Not really
  • Q: Favorite UX/design trend?
    • Save as you go. e.g. No need to submit, no worry about losing a page of stuff.
    • Save as draft.
    • e.g. shoebox (receipt tracking, OCRs photos of receipts), evernote, 
  • Q: How do you convince a boss who says a lot of these things?
    • Data, data, data.
    • That boss will love spreadsheets.
  • Q: Information architecture / card sorting. Are there documented best practices? e.g. “For industry A, these are the results...”
    • Don’t know of anything existing. Because it is as unique as your content. If your content is different, then your information architecture is different. utility navigation may be pretty much the same.

Discussing Design: The Art of Critique


Discussing Design:
The Art of Critique
#wvpdx webvisions 2012


Slides: http://t.co/u9mMXXBl 
  • What is critique?
    • critique and feedback are not the same thing.
    • feedback: gut response. instance reaction to something.
    • critique is an ongoing process: built on refining to create a better product.
    • it needs to be presented in such a way that it is actionable.
  • critique is about critical thinking
  • there are two facets to critique
    • giving and receiving
    • at their foundation is intent. the “why?”
    • why am i asking for feedback? why am i giving feedback?
  • giving critique with the wrong intent is selfish.
    • “I’m smart, this is wrong, I want to be validated that I’m smart.”
  • it’s about approach as well: “hey, congratulations on your launch. that’s awesome. i love the product. when you get a chance, i want to give you some feedback. can i buy you lunch or a beer or send you an email?”
  • Tips for giving critique
    • Use a filter: Gather initial thoughts and reactions. Revisit them in the right context.
    • Don’t assume: Find out the reason behind thinking, constraints or other variables.
      • Odds are, they had many constraints.
    • Don’t invite yourself: Get in touch and ask to chat about the design.
    • Lead with questions: Show an interest in their process?
      • What were your goals?
      • What were you trying to do with that?
    • Talk about strengths. Critiques are not just about things that aren’t working. It’s also about understanding what is working well: to maintain or to build on.
  • Receiving critique with the right intent takes humility and meekness
    • Remove yourself from the setting. It’s about the product.
    • Don’t ask for feedback if you aren’t ready to receive and act on and think about.
    • Remember the purpose: critique is about understanding and improvement, not judgement.
    • Listen and think before you talk back. Do you understand what the critics are saying?
      • Don’t be thinking about your rebuttal while they are talking.
    • Refer to the goals. Is what you’re hearing pertinent to the goals you’re trying to achieve?
    • Participate. Analyze your proposed solution along with everyone else.
  • Critique is a life skill, it is not a design skill.
    • It applies to sports, cooking, anything that you can do.
  • Making critique part of your process
  • Design Reviews
    • This is not part of design review. You can have 30 people in a design review. Half the people there don’t care.
    • design review is not a critique
    • critique is impromptu, or scheduled, but it comes before design review.
  • Critique is a skill. You only get better with practice.
  • Start small.
  • Think before you speak.
  • Choose who you critique with carefully.
  • Rules of Critique
    • Avoid problem solving and design decisions.
    • The designer is responsible for follow up and decisions.
    • Everyone is equal.
    • Everyone is a critic.
      • Don’t let people be silent...because they’ll come back two months later with feedback, and it’ll be too late to address it then.
  • Goals are critical for successful critique
    • Scope the critique session: “today i want to talk about flow”, “today i want to talk about this one UI component”.
  • Who should you invite?
    • 4-6 people.
  • Tools and techniques
    • Active Listening, question for clarity
    • Round robin
    • direct inquiry
    • quotas
    • six thinking hats: emotional perspective, behavioral perspective, etc. 
    • Facilitators
      • Helpful in the beginning, but as you get more experienced, you will want to take control of your conversation yourself.
  • Handling difficult people
    • Set expectations at the beginning. “We’re not here to talk about the color. We’re here to discuss this UI component.”
    • Make sure everyone understand critique.
    • Ask quiet people for feedback directly.
    • Refer back to personas, goals and principles.
    • Use laddering (the 5 whys).
    • Critique with people individually ahead of time.
      • Get them out of a group session. It’ll be more civil. They won’t flare their peacock feathers.

Thor Muller on Planned Serendipity

Notes from Thor Muller's talk at Webvisions 2012 (#wvpdx)


Get Lucky: The Business of Planned Serendipity
Thor Muller
  • A lot of success is luck.
  • But how can we manufacture luck? Can we create chance encounters?
  • There’s nothing random about luck.
  • GetSatisfaction
    • Started with a joke. (So many great scientific breakthroughs came from play.)
    • We could start a shwag of the month club. And we did, and within two months had 2,000 subscribers. But fulfillment is hard, and customer service is even harder. Hundreds of emails every day.
    • But we discovered that customers would repost our answers to them, and would ask questions on the web.
    • So founded GetSatisfaction. Now have 65,000 paid customers.
  • Serendipity = chance + creativity
  • Recent research shows that we can do more/different to enable creativity in ourselves. We can read the owner’s manual for our minds.
  • But... we’re wired to avoid risk and change. We want predictibility.
  • So how do we let in unpredictability and predictability at the same time?
  • The answer is planned serendipity
  • http://bit.ly/liHRUy
  • Jane’s Story
  • Preparation
    • “Chance favors the prepared mind.”
    • Obsessive curiosity. Going deep. Following curiosity further than is normal.
    • Jane’s first obsession was sculpture
    • Notice the anomalies. The things that don’t fit. (Most business people look for the similarities.) Arresting the exception
    • Forget what you know to be true. This is important to be able to make big leaps. Otherwise beliefs limit you. 
    • Jane went to school
      • played with materials. made something out of silicon and wood chips. it amused her that it was a bouncing wooden ball. 
      • When we think concretely, it’s about things very near to us in time, space, relationships.
      • When we think abstractly, we’re able to connect things beyond categories, because we’re seeing things from a much higher level perspective.
      • when Jane went into her materials workshop, she came in with a sculptor's mentality. 
    • Structures you can use to create this: 20% time
  • Motion
    • To stir the pot. Run into new ideas and new people. Open space.
    • taking the materials workshop helped jane run into new ideas and new people.
    • computer models show that diversity helps solve complex problems.
      • when people are the same, and they tackle the problem, they all get stuck in the same place.
      • when people are very different, and they tackle a problem, they get stuck in different places.
      • the problem with the workplace is that we stick everyone into cubicles, so they can’t talk.
    • Structures to create: pot-stirring events and open space
  • Commitment
    • To have an overriding purpose. To stick to that purpose. 
      • Which implies: knowing what to say ‘no’ to.
    • Overly broad mission statements don’t help us unless they tell us what to say ‘no’ to.
    • Decision fatigue: the more decisions we make, the worse decisions we make. the decisions become arbitrary.
    • By knowing what to say no to automatically, we have more willpower left for the decisions that do matter.
    • Structure to create: The automatic No-list
  • Attraction
    • Jane talked to everyone about: scientists, media people, fellow students. 
    • Project your sense of purpose out into the world.
    • It changes what the world sees as possible.
    • And it gives people a place to come if they care.
    • For Jane, it brought people in who could contribute their skills.
    • Will to Meaning
    • Interviewed a group of people to assess first the sense of purpose of the people. then asked the people to do a 10 minute introduction of themselves. Then showed the videos to other people and asked viewers to rate the attractiveness of the speakers. Those people who had a higher sense of purpose were rated as vaster more attractive across the board.
  • Divergence
    • Branching strategy
    • Jane got a 35,000 pound grant. but the material was imperfect. that wasn’t enough money to do the necessary rounds of testing. the only way she could do it was to do the research and testing herself. she spent two years and taught herself materials science on the fly to perfect the material.
  • The Hidden Bias Against Creativity
    • Inserting uncertainty into a situation caused people to rank creative ideas in a negative way or with negative connotations. (the example given was a study in which some participations were told they would be entered into a lottery to win a prize. this uncertainty caused negative responses.)
  • Permeability:
    • Customer Community

Notes from Thea Boodhoo's UX for Aliens Talk


content specialist on the UX team at AKQA
(Sorry, again came 15 minutes late to session, so notes are incomplete.)
  • Dolphins use ecolocation to form a 3D projection of the world
    • Can also transmit the 3D representation to other dolphins
    • There’s no word for “tuna”. There’s a compressed 3D representation of a tuna.
    • Two dolphins from different parts of the world can come together and communicate a plan using 3D representations of the world, without having to use vocabulary or symbolism.
  • Scale of Context Dependency
    • an in-joke is an example of a highly context dependent communication
    • other end
  • Resolution
    • Project high, design low
    • We don’t know what resolution things will be consumed at. So we want to project at high fidelity, but design for low.
  • Speed
    • We don’t know what kind of frame rate an alien would receive.
    • So we again want to project for highest possible, but design for slowest.
      • e.g. we don’t design a website that requires the transfer of 3 mb of video data before getting to the point, for a user on a smartphone. 
    • Play at several speeds at once.
  • Strength
    • Build up the signal from a very low strength and give it a stop button.
    • Don’t send anything that, if returned, could kill you.
  • Channel
    • The frequency of visual spectrum, audio range. For humans, we know we can smell roses, hear certain range of sounds. With alien users, we can’t know. All of the animals we know can receive more than one channel.
    • So we want to use many parallel channels
  • Devices
    • Devices we’re born with: native devices. eyes, ears. signals being experiences as raw, direct.
    • Non-native devices: picks up channels we can’t physically receive and translates them into channels we can. We can’t receive radio waves, but we can translate it into audio signals that we can listen to. We can’t receive IP packets, but we can render a twitter stream visually in the shapes of letters.
    • Design for the native device:
      • The best way to represent a water bottle is with a video or a photo of it.
  • Assume the user has the ability to project a tool as an extension of itself
  • If you know nothing about your user, you have to do a lot of work. The more you know, the less work you have to do.
  • Don’t let the what ifs stop you.

Notes From Jason Crawford Teague's Trust Me, I'm A Designer


Trust Me, I’m a Designer
#wvpdx webvisions 2012
(Came 15 minutes late to session, so I am missing the notes for the first three principles.)
  • First: Keep Promises
  • Second: Show Results
  • Third: Know Your Voice
  • Fourth: Respect Context
    • if we give the user the wrong interface for their context, they aren’t going to trust us. e.g. giving them the full website experience when they are on their smartphone, or the smartphone experience on their desktop computer.
      • Context Prevents Confusion
  • Fifth: Transition Changes
    • Change Blindness:
      • If we go from one picture to black to a modified version of the picture, we can’t see it. We have change blindness. 
      • By comparison, if we transition directly from one photo to the other without anything in between, then we can easily see the change.
      • By default, web page loads are more like the former: you click a link, the page goes away, and a new page comes in. It may not be obvious what happened.
      • If we use transitions, it preserves context and makes the user feel more comfortable.
  • Sixth principle: Guide, Don’t Dictate
    • Our natural tendency is to tell people what to do. And we tell them the way we would do it.
    • But we don’t like being told what to do.
    • Showed version of gorilla video: people passing ball, count the passes.
      • except a player leaves the team and the curtain changes color.
      • no one sees that.
    • When I tell you what to do, then you’re going to focus on it. 
      • They’re going to worry that you’re trying to do a sleight of hand on them.
      • Don’t fall for the sleight of hand.
    • If you guide someone, if you give them choices, then they are going to trust you.
  • Seventh principle: Show, Then Tell
    • We seek patterns
    • Example website:
      • Each page has a very large photo that identifies the page: e.g. an image of a building he built, a photo of a person for the bio.
      • the image sets the tone for the page.
      • then give the text
  • Eighth principle: Make it simple, not simplistic.
    • Steve Krugue: Don’t make me think - http://www.amazon.com/Dont-Make-Me-Think-Usability/dp/0321344758
      • But he’s not saying “Don’t let me think”
      • Simple: Don’t make me think
      • Simplistic: Don’t let me think
    • Example: netflix
      • interfaces are context specific and very simple
      • interface is simple: just photos and titles
      • but I roll over titles to see the details, drill in and get more details, search on attributes
      • unveil the information when people need it
  • Ninth Principle: Always Leave Them Wanting More
    • To be persuasive we must be believable; to be believable we must be credible, to be credible, we must be truthful. -- Edward R. Murrow

Notes from Baratunde Thurston Keynote at Webvisions 2012


Correspondent from the Future: Future & Digital Storytelling
Baratunde Thurston
The Onion
Webvisions 2012, wvpdx
  • @jjpolitics 
    • jack and jill politics
    • “the watermelon has long symbolized intelligence discourse”
  • tv host discovery channel “future of”
  • director of digital at @theonion
  • live hate-tweeting: all twilight movies
  • Author of How To Be Black
    • if you don’t buy this book, you’re a racist
  • Use brainstorm for headline about steve jobs death
  • For live-tweeting events, have prep documents with many dozens of tweets prepared.
  • for oscars: search onion archive and retweet.
  • using analytics to see what got retweeted, and then used that information to decide what to published on the website.
  • Be a Platform
    • Did planned parenthood satire story about “abortionplex”
    • Didn’t ask anyone to do anything, but...
    • Someone created Yelp destination for it
    • Received 282 reviews, quite detailed.
    • Supports and extended the world/story.
  • Invite people to participate
    • “If you sight a 500 foot tall Bin Laden, send pictures.”
  • Evolve Story Across Platforms
    • Created entire campaign around mayorship on foursquare
    • Video
    • In person campaign
    • In these divisive times, we need something to bring people together. That’s whiskey. Hence, “Whiskey Fridays”.
  • #HowBlackAreYou
    • Started as a dialogue on twitter
    • Turned into an idea for a book
    • Interviewed people on video (using iPhone 4s)
    • Invited people to respond on their website and tell their own story
    • The book had dozens of questions around identity.
    • “When did you learn you were black?” ... “a white ghost?”
    • Did a live-writing idea:
      • while writing certain chapters:
      • shared screen using join.me
      • shared links on google+ and twitter
      • posted rules on the left:
        • chat amongst yourself, not with me
        • don’t request control, etc.
      • “How self obsessed does one have to be to set something like this up?”
      • “I have an urge to tweet about this”
      • “Based on what I read here, I am going to buy this book.”
      • “it is interesting to see his writing flow”
  • Stories Are Worlds
    • we ask people to suspend disbelief and join us in that world
    • the platforms are just different access points into that world
  • check out http://cultivatedwit.com

Webvisions Notes: Designing for Mice and Men - Bill Scott of Netflix


Designing for Mice and Men
Bill Scott
@billwscott
Netflix
  • Current Experience Chaos
  • First we had a site, then we had devices.
  • On 400 different devices
  • How do we tame it?
    • Netflix Owned Experience Across Devices
  • Wanted a web-like design, development, a/b testing experience across all devices
  • PS3 browser is Netfront, which is a clone of IE6. All the bugs of IE6 plus more. jQuery wouldn’t run on it. 
  • They decided to port webkit to the PS3.
  • Then realized that they could provide this to manufacturers. If they had webkit, then they could design and develop for webkit across all devices.
    • across TV, smartphone, tablet, browser.
  • They have a single javascript bundle on the content delivery network, which they can change at any time, and update the experience across all the devices.
  • Why do we want to own the experience?
    • netflix is known for valuing UX. -- you can’t do it if you don’t own it.
    • We love server-driven, testable, dynamic UIs
    • We like agile web better than rigid CE firmware process
    • We value “learn fast/fail quickly”
    • Any other path would lead to chaos
  • Initial HTML5 Experience: PS3 - “Special”
    • Content and navigation tied together.
    • customers always self-report that they want movie discovery tools.
  • Alternate HTML5 Experience: PS3 - “Plus”
    • just a grid in which you move around, not ability to move categories or genres.
  • Design Across Platforms
    • We chose a portability layer - html5, css3, js
    • But we don’t use progressive enhancement since we want the freedom to experience with different UX on different platforms. if we also add progressive enhancement, it gets too complicated.
  • Design Principles - haven’t really changed in 1983
    • Get Physical  - making things feel real, direct, interact with them. 
      • Give them the illusion of physicality
      • Granddaughter fell in love with the iPad - specifically something called spinart.
      • Apple HIG: whenever possible, add an actual physical dimension to your interface.
      • Original netflix player on roku: when you pause it, there is a filmstrip that you can flip through.
      • the iBook has pages that turn.
      • But on the Kindle, they have an anti-pattern - broken metaphor. They have “location”. It’s an implementation, but it’s not a user’s mental model. 
      • “Books have pages”
  • We can break the metaphor with magic.
    • “back to the original page”, “you are here” you can go anywhere. “pages left in the chapter”.
  • Apple breaks this with iCal. They give you the illusion of pages -- using depth and visual indicators, but then they break the metaphor by not having the ability to flick pages.
  • The brain cannot see a change happening to an element that has not yet been stored. 
    • example: flipping between two similar photos, one has the airplane engine edited out. when the two frames have a flash between them, we can’t see it. when there is no flash, we all spot it immediately.
  • “Plus” experience won. Reduces page transitions.
  • Lots of UX examples of Twitter app on iPad vs Mac app vs. browser. Can’t capture them all.
  • Questions
    • Q: How do you determine the winner when you try different theories?
      • We care most about retention. But people don’t quit the service immediately because a button style changed.
      • The proxy for retention is consumption... do they watch movies? add them to their queue.

Webvisions notes: Lies My Data Told Me by Thor Muller


Lies My Data Told Me
Thor Muller
Get Satisfaction
@tempo
#datalies
  • 12.2 minute: average time to completion to close out a customer service ticket
    • for thousands of companies, over decades, this has been a key number that companies manage.
    • Companies look at customers as to-do items, and so less time is better.
    • But we could have
  • Data is backwards looking.
    • Imagine if you are driving a car, but you can only look in the rearview mirror.
    • We can project out with trendlines, and pattern match, and extrapolate -- people will say this.
    • But you could say the same about driving looking in the rearview mirror. In general, the road ahead will be much like the road behind. But this doesn’t help you when you come to a Y in the road.
  • LTCM - built the algorithm to look at historical data and to tell them what trades to make. It worked great. Until Russia defaulted on obligations, causing a near global collapse.
  • Launchrock
    • Helps companies launch a business... Cowritable has viral growth even before they have launched. However, success getting people to subscribe for a product they have seen does not predict what will happen when the product comes out.
  • [missed a bunch of notes here while I got distracted reading the Launchrock site.]
  • Data Can Be a Real Killjoy
  • Success often requires patience or a patch... rather than a pivot.
  • When to ignore the data
    • When you are in “blue sky” creative mode.
      • don’t think in terms of constraints. don’t limit your imagination.
    • When available data is too general or ill-fitting.
      • e.g. “2/3rds of all startups fail” -- that’s not useful for evaluating a specific startup.
    • When you’re unsure of what matters.
      • e.g. do page visits matter?
  • The Optimization Trap
    • “Multivariate testing caused us to design a product that we’ve come to hate. It’s ugly and pointless, but it generates real revenues so we can’t kill it.”
    • Optimizing your product can it is more like it is, but it can’t get you to a new product.
    • Optimization brings you to a local maximum, rather than a global maximum - you might get a better buy button, but you won’t get a whole new design that gets you 100x customers.
  • The squeaky wheels get the grease
    • OpenID vs. Facebook
    • Once had a very vocal part of community would complain about our OpenID community.
    • Whereas Facebook users hardly complained at all.
    • But Facebook accounted for 50% of users, whereas OpenID was a fraction of a percent. The OpenID people may have been vocal, but it wasn’t really the business relevant thing to do.
  • Data is Amoral
    • Data makes us blind to our own values -- people making mortgages to people who couldn’t pay them. It just couldn’t make sense. But since it was returning money, the data said to invest in it.
  • The Tyranny of the Obvious
    • If you spend all your time looking at the strong, concrete data points, you are looking more than ever in the rear view mirror, because you are seeing the strongest trends.
    • If instead you look at the oddities in the data, you can see the yet-to-emerge trends. Like Lego, who found a teacher doing robotics, which turned into the Mindstorm’s product line, highly profitable.

Webvisions notes: Pig Faced Orcs - Design Lessons from Old-School RPG


Pig-Faced Orcs: Design lessons from Old-School Roleplaying Games
James Reffell
@jreffell
designcult.org
Slides:
  • This is not a gamification talk
  • photos: first convention badge at age 11, awesome map he drew of a dungeon as a kid.
  • Old School Roleplaying Games
    • Chainmail - 1981
    • D & D - 1974
  • There were army games before, but you played an army. The twist was that then you played an individual.
  • D4 version:
    • Give them something to manipulate.
    • Use randomness to generate a story.
    • Use sandboxes and railroads.
    • Enable risk-taking.
  • Give them something to manipulate
    • if you’ve ever done pen and paper rpg, people fiddle with the dice. They are there for randomness, but people play with them, build towers with them.
    • random number generator: you have to move the mouse around a whole bunch to generate a random string.
    • ipad app: for etch-a-sketch. you shake it to clear the screen.
    • Having things to fidget with helps you concentrate without distracting you
    • But we need more things..
      • Texture
  • Use randomness to build story
    • dice/randomness are used, in a very exposed way, to build narrative and build tension. you worry if you will win the fight.
    • Example: rumor table - from d&d adventure. rumors are given out to players at random.
    • One of the classic examples in social media is asking people to contribute content. what should they write about? they often don’t know. sometimes they use a “topic of the day”. but what is that is randomly generated?
  • Use sandboxes and railroads
    • In a sandbox game, players can explore a world. But you really don’t know what is going to happen next.
    • A railroad game has a plot. You don’t know exactly how it is going to go, but it’s got good guys and bad guys and you know who they are.
    • Amazon 
      • A sandbox world. From a product page, you can do anything:
        • you can buy it, you can see other objects like that, you can see stuff that other people who liked that thing liked, you can read reviews, you can go to forums or to wiki, you can see stuff you bought. 
      • A railroad world. From the shopping cart page, there are no distractions, no navigation links. You are heading toward purchasing the product.
  • Enable risk-taking. (Carefully.)
    • In RPG, sometimes characters die. You become even more attached to the characters who don’t die. Characters who die create memories.
    • We don’t want to risk user data, or risking their privacy exposed.
    • Good examples:
      • Bidding on eBay. You have the risk of losing - not winning the bid.
    • Fun failure is a way to prolong the game experience.

Webvisions Notes: The Independent Software Developer - Peat Bakke


The Independent Software Developer
... or how I learned to stop worrying and started my own business
Peat Bakke
@peat
  • My goal is to do things I Really Care About
  • I’m not particularly good at being a 9-5 employee, because there are too many things I like to do.
    • like this, traveling, having a kid, contributing to open source
  • The Problems
    • I need more time.
    • I need full ownership.
    • I need to pay the bills.
  • The Solution
    • Freelancing!
  • More Time
    • If you are working full-time for an employer, then you have to work overtime in your personal life to do cool projects.
    • Would You Rather...
      • Convince your boss to pay you to do personal projects for 25% of your time at work?
      • Would you like to spend your evenings and weekends working on personal projects in addition to your work day? (this was great in my 20s...)
      • Spend October, November, and December working on personal projects, without having to worry about going broke?
        • maybe in Mexico?
        • On the beach?
    • Freelancing = Flexible Schedule
      • You have the ability to choose when you are working for a client vs. working for yourself.
      • The downside: “You get to pick which 60 hours a week you work.”
        • This comes and goes, and it is possible to set limits.
  • Ownership
    • Don’t Cross the Streams
      • Personal work and client work
      • It would be bad
    • If you are getting paid to write code, you most likely don’t have the copyright to that code.
      • If you don’t have the copyright, you can’t legally contribute it to an open source project.
  • Freelancing = Flexible Ownership
  • Paying the Bills
    • How much do I need to charge? How much do I need to work to pay my expenses?
    • Your base rate: Expenses x (1 + Tax Rate) / Working Hours / Billing Ratio
      • Expenses: Everything you need to spend to be happy
      • Tax Rate:  (30% is a safe estimate.)
      • A standard full working year is about 2,000 hours a year.
      • Billing Ratio: What percentage of your hours will be billable? Some of your time is spent finding clients, arguing with clients, etc.
    • e.g. $50K in expenses * 1.3 tax rate / 1500 hours / 70% billing ratio = $61.90 base rate.
  • Focus on Your Expertise
    • Do not write your own contracts.
    • Do not prepare your own taxes.
    • Do not run your own payroll.
    • You can spend an entire career trying to develop the expertise trying to do this stuff.
    • He spends $3,000 on this stuff.
    • What would be the opportunity cost? How much time would it take to learn and master all of that?
    • Or he can raise his base rate by $2.19 and pay for it all.
  • Freelancing = Flexible Finances
  • My Goal is to Do Things I Really Care About
    • Freelancing is the model he’s found that really works.
    • It’s one of many models.
  • Questions
    • Q: What if you are not good at getting clients?
      • Software is in high demand. Your skills are in demand.
      • Most people don’t even show up. The first thing you need to do is to show up. Send an email, make a phone call. Buy someone coffee. 
    • Q: What if you have friends with a non-profit and they can’t afford your regular rates?
      • I take those hours out of my personal time. I have them set aside, and I can use them for anything I want.
      • Plus non-profits are a really good way to promote yourself.
    • Q: Did you make this transition gradually or abruptly?
      • I did it eleven years ago, during the dot com crash.
      • I had to learn this stuff from scratch.
      • There are no books about being a freelance software developer.

Erin Jo Richey on Mapping a Unified Experience Across Multiple Devices


Mapping A Unified Experience Across Multiple Devices
Erin Jo Richey
@erinjo
  • Maintaining a core vision
  • Working across..
    • Televisions, Cars, Kiosks, ATMs, table surfaces, displays refrigerators, mirrors. 
  • Habits of online newspaper readers, by device and time of day...
    • 97% of views on computer, 2% views on smartphone, <1% on tablets.
    • In early morning, more likely to use smartphones and tablets. During the day, people more likely to use computer. In the evening, phone and tablet skyrockets, and computers fall off.
  • Marketing strategies...
    • multichannel marketing: Sending out messages to multiple places. Just because you are communicating to all these channels doesn’t mean you have a strong campaign.
    • Cross channel marketing: You are sending out to multiple places, but you are targeting messages and collateral to the platforms where it works best, reaching them where they are with the right message at the right time. 
  • A continuous system, until it breaks.
    • Example: You bought a product on Thursday, and on Saturday you get a message about a discount for buying it. The communication strategy should be integrated so that the mailing list suppresses the addresses of the people who just bought it. 
  • Need information architecture strategy
    • Top down: user needs > company needs
    • Bottom up: where are customers now>
    • Push and pull marketing
  • So we’ve got all this activity, all these pressures from all different directions.
    • It’s a spider web, a messy bunch of interconnections
  • We’ve got to build bridges across experiences.
  • Environmental design...
  • http://bit.ly/kCTBLz / http://bit.ly/bundles/erinjo/3
    • Worksheet available as Omnigraffle or PDF
  • Worksheet goes through
    • External Forces (the nest) -- influence
    • The design your company creates (the egg) -- control
    • The internal Forces (the egg) -- influence
    • You can influence some of the external forces and the internal forces. But you can control the design.
  • The Egg
    • Message - the campaign, marketing message, or brand slogan
    • Content Item - the unique content item
    • Task - what task is associated with the content
    • Frequency - how frequently are these tasks performed?
    • Urgency - how urgently is the information needed or tasks get completed?
    • Privacy - is this content intended for one person, multiple people...
    • Intimacy
    • How to Track - How do we track usage
    • What to Measure

Webvisions notes: Good App Bad App by Jason Glaspey


Good App / Bad App
Jason Glaspey
  • Audience Survey
    • How many have smartphones - All
    • How many downloaded at least 5 apps -- Half or more
    • 10 or more -- a quarter or so.
  • Companies are saying...
    • What’s our mobile strategy?
    • Should we have an app?
    • We NEED to have an app.
  • Mobile has exploded
    • 10 billion app downloads
    • over 350k apps on iOS
    • 30-50 apps per person
    • mobile app revenue > $15B this year
  • Your app has competition
    • 40 hours per month spent in-app
    • people download 15 apps per month
    • but, on average, 1 month lifespan
    • 26% of apps never opened a second time
  • An app isn’t enough. Even a GOOD app isn’t enough.
  • If people don’t have the problem, and aren’t searching for the problem that your app is solving, then you have to go through a lot of work just to reach those people.
  • Brand Loyalty
    • How many of you have loyalty to a brand?
    • Do you search for an app for a company?
      • Example: Guy searched for VW app, hoping that there would be an app to provide an experience of what the new car would be like.
    • But this is exceeding rare that people are looking for an app so a company can market to them.
  • Most loyal brands in America
    • Ford, Facebook, Apple, Dunkin Donuts, Sam Adams, Cheerios
  • Do you need an app?
    • People are coming to Urban Airship because their boss said “we need an app”.
    • What should it do?
      • Don’t know, don’t care, it just has to be good.
  • Would a mobile website be enough?
    • Sometimes an app can be really lightweight - for search, the Google app does voice recognition.
    • Sometimes it doesn’t need to be. Google doesn’t have a Gmail app, just a really good mobile app.
    • Google uses apps when apps make sense, and web content when web makes sense.
  • Pros of an app: 
    • You can have a badge on your homescreen. Can promote engagement.
    • Can have push notifications, e.g. getting an alert when someone mentions you on twitter. Hard to do with web apps, easy with apps.
  • Cons
    • It’s expensive. Are you going to be on iOS? On Android? Which Android? On Windows? On Symbian? On Pre? Well, no one is on Pre.
    • It’s easy to find people to code html. Harder to find good web developments.
  • Sometimes your mobile strategy is: “We don’t need one”.
    • An air-conditioning company asked “What should be their Facebook strategy?”
    • “You don’t need one”
    • They don’t believe it.
    • They spent thousands of dollars trying to get to the 100-friend requirement just to have a vanity URL.
    • It was really about covering your ass: the marketing manager didn’t want to say to her manager “we don’t have a facebook strategy”.
    • Unless you have a product that a customer will be looking for on their phone, you probably don’t need a mobile strategy.
  • Know Your Audience
    • Do they identify with their phone?
    • Or are they just trying to solve a problem?
    • The people who identifies with their phone may spend half the day trying to find the coolest new thing. But the person who just uses it to solve problems just wants to do that, not be bothered with app updates and complexities.
  • Your App Needs to Tell a Story
    • Breitling: Make an app that shows their watches. Totally pointless. You could have just put the content online. The app is about the company.
    • Weber’s: their app helps you find recipes that are specific to the BBQ. The app is about making the customer more powerful. It makes you the perfect BBQer.
      • And it makes sense... you don’t want your laptop sitting on the BBQ. You can pull up your phone.
    • (Note to self: Get Weber app.)
  • Toyota Example
    • Web app to totally configure, price out, and order cars on the website.
    • But people aren’t going to do all that on their phone.
    • But, what about an app that lets you take a picture of your VIN number. And then the app alerts you when you need an oil change, gives you a coupon, and tells you when they have a bay open.
  • Don’t create barriers to your app. It’s hard enough just to get them to your app.
    • Coke came up with an app called Lifecycle.
    • The first thing the app did was make your log into Facebook. They didn’t even know what the app would do.
    • No one used the app. They didn’t trust Coke enough to blindly log in via Facebook without even seeing the benefit.
    • Then they added a “skip this step” button. Usage went up.
  • Know Your Apps and the MotivationsBehind Them
    • Revenue: Angry Birds
    • Branding: Weber On-the-grill
    • Utliuty: ESPN score center
    • Product Extension: xfinity remote dvr control
    • Storytelling: Democrats
  • Howe will they use it?
    • Drive-thru apps: 15 second usage: word play. 
      • Don’t make a long loading sequence or require saves if the user will use it in tiny increments.
    • waiting apps: 1 to 5 minute usage
      • Angry birds, YouTube
      • opening quickly, closing quickly
    • Entertainment: 5+ minutes
      • plenty of time
    • Utility: 
      • make it fast.
  • Why Would Users Download?
    • Does it have a clear valuye proposition?
    • Are people asking for it?
    • Will you have to market your marketing app?
  • Why Would Users Return?
    • Keep track of how people use it, and add to that.
  • The best apps have deep content.
    • TripIt
    • Nike Training Club
  • Push Best Practices
    • Don’t spam or over-send, or they will turn off notifications.
    • Track active devices to see if you’re oversending.
    • You want users to LOVE getting your messages.
    • Give lots of control to the user.

Less Is the New More by Adam Ware - Webvisions Notes


Less Is the New More
Adam Ware
@wheresitworking
hashtag: #somuchdata
  • SwellPath: Love child of a web analytics and search marketing company
  • Everyone’s dilemma: 
    • An overarching problem collecting, organizing, reporting on, and analyzing data
    • Universal across all organizations, scaling large and small, even non-profit preschools, small business, and large corporations
  • How did we get here -- What caused the growth of internet data?
    • Speed : real-time data
    • Scale: unprecedented processing power
    • Sensors: many new kinds of data
  • Growth
    • In 2002: 5 exobytes of data
    • In 2009: 281 Exabytes of data
      (1 exabyte = 1024 petabytes = 1M terabytes
  • Digital Marketing Data is a Mess. The problem is exacerbated by:
    • Most metrics not being aligned with business objectives
    • Disparate data sources: website, social, mobile, CRM, etc.
      • And it’s really hard/ impossible to track people across those experiences.
      • So the data looks like seperate people. A person on twitter isn’t tracked as the same person who was on your website yesterday looking for tech support.
  • How do we overcome it?
    • Ask: Do the Number Even Matter?
      • Reasons why they might not matter:
      • Aesthetics: Are you studying stuff that you wouldn’t do anyway, because it would look ugly. e.g. Do you need to do A/B testing on a flourescent orange buy button?
      • Brand values: Are you testing things that, if you took action on, would be outside your brand value.
      • Overarching business strategy
    • Look at the Few (whitepaper from a company called Juicy Analytics, section called choosing the right metric)
      • Metrics that are actionable
        • Can you do anything about them?
      • They can be commonly interpreted
        • Does everyone in the organization understand the numbers
      • The calculations are transparent and simple
        • Example: on a website, they needed to measure which visitors were engaged. They had a way of figuring that out, based on pages visited, videos watched, etc. They could explain up front how the numbers were calculated (transparent), and while not simplistic, they were simple enough to be understood.
      • The data is easily accessible and credible
  • Aggregate Metrics
    • Would it be less valuable in aggregate?
      • Example: If you are studying growth in community, it’s useful to look at twitter, facebook, and forums in aggregate, not individually. 
    • Be broad, but be comprehensive
    • Helps avoid uncertainty, data-doubt.
  • Visualize It
  • Q and A
    • Q: Making sure the data you have is actionable.. Is that a chicken and egg problem?
      • We spend time with the data, isolate the things that are really actionable for the people who don’t have a lot of time to dive into the data.
      • But we are spending a lot of time looking at all that data figuring out what is actionable.
      • And, of course, you need to deep dive to figure out what to do.
  • Resources:
    • Marrisa Mayer at PSRC: innovation at google the physic of data
    • blog.kissmetrics.com/you-vs-the-data
    • juicenanalytics.com

Webvisions: Intro to HTML5 by Scott Vandehey


Intro to HTML5
Scott Vandehey
@spaceninja
  • Great history of why HTML5 came into being: 
    • Long version: diveintohtml5.org/past.html
    • Backlash against XHTML2, which would have been too draconian. Would have cause sites with any errors at all to not render. Browser manufacturers hated this.
  • HTML5 Design Principles
    • Support existing content
    • Any new stuff we add should degrade gracefully
    • Pave the cowpaths
      • Let’s look at the way the community is already doing things. Let’s document how people are actually working, and make sure things work that way.
    • Priority of Constituencies
      • users > authors > implementors > specifiers > purity
  • Joke: HTML = How To Meet Ladies
  • Better Forms
    • New input types
      • email
      • telephone (tel)
      • url
      • number
      • and many more...
      • ex:
    • Only small browser enhancements so far, but it is getting there. On the iPhone browser, for example, they optimize the keyboard for the type of input field.
      • prefills the text box with the instructions
      • to avoid javascript or server side validate to validate forms.
      • in the future browsers will do this, include field type validation
    • Create an input field out of anything:

        click me to edit
  • Better Videos/Media
    • Example shown: massive amount of code shown for doing Flash video...
    • In HTML5:
    • Actually, a little more complex, because each browser supports a different format. But you can encode the video multiple times, and then put the source multiple times.
  • New Semantic Elements
    • header
    • footer
    • nav
    • aside
    • article
    • section
  • Simplified Elements
    • doctype:
    • meta: 
    • No type needed for js and css elements
  • How to convert to HTML5 in one easy step
    • Just change the doctype to . You’re done. Because everything is backwards compatible.
  • Browser shims:
    • Add some css:
      section, article, header, footer, nav, aside, hgroup {
        display: block;
      }
    • Also, add some conditional comments to your head for IE
  • Rumors
    • Browsers don’t support HTML5
      • Wrong. All support it to some extent. There’s no reason not to use the parts that work today.
    • Rumor: HTML5 won’t be ready until 2022
      • 2009: W3C working draft
        • browser manufacturers already working to implementing.
      • 2012: W3C recommendation
      • 2022: two complete working implementations
        • This can be ignored... There aren’t two complete implementations of CSS2.1, but we’ve been using that for years. Browser manufacturers get to 95%, and then they quit implementing the spec.

Webvisions Keynote Summary: Douglas Rushkuff - Program or Be Programmed - Ten Commands for the Digital Age


Program or Be Programmed:
Ten Commands for a Digital Age
Douglas Rushkoff
  • “You are our last, best hope for peace.”
  • first time I spoke in Portland was 17 years ago, for the book Siberia.
  • First publisher cancelled the book, because they thought the internet would be over by 1992. They thought it was like CB radio.
  • Premise of first book: We were moving into a hyper-text reality. We would imagine things happening, and they would happen. Thought we would need psychodelic people, people who were comfortable with the idea that we would have visions, and that they would come out.
  • Very upsetting to people the idea that we would live into a world where what we imagined would come true.
  • “but don’t worry, children and stoners don’t have a problem with that.”
    • so it was the stoners who did the early innovations, it’s why early internet culture was so weird.
  • now the resistance is that “programming is too hard”, that people can’t do that.
  • so at first, a resistance to dream, and now a resistance to work.
  • so certain kinds of people and forces have been in charge of the movement forward.
    • so in 1992, was like dropping acid. anything was possible. experiencing hypertext for the first time was crazy.
    • coming out and seeing the grid pattern in new york, maybe him realize that everything is a design choice, someone’s decision about how things should be. it’s us programming the world.
    • all of the bridges coming into NY have 8 1/2 foot clearances. why? to prevent buses from coming into the city to keep the black people out. someone created that.
    • SXSW: 
      • was once like webvisions, a bunch of people trying to figure it all out, trying to figure out if they can make a living at it.
      • now it’s about making that next killer app, about getting angel funding. it’s all feeds into an artificial scarcity central bank system that’s destroying the planet. 
      • how is that the hacker ethic?
      • it’s fine to make apps, but do we have to support a system that is destroying the planet?
  • we have all had the experience of a favorite local band. the worst thing that can happen is that they make it big. suddenly their music changes. suddenly they are everybody’s band. you’ve lost something.
  • imagine if you woke up, and the only operating systems was windows. you wouldn’t know anything different. you wouldn’t have the idea that there could be other operating systems. you wouldn’t even know what operating systems were, but there would be nothing to talk about.
  • He once thought kids would have this all figured out. That they would be better able to sense fantasy versus the real world. That they would be better critical thinkers. But that’s not what has happened. They accept things at face value.
    • Ask any kid what Facebook is for, and they will say “to help me make friends”.
    • Is that what they are talking about in the corporate boardroom? How to help Johnny make friends? No, they are talking about how to monetize Johnny’s social network.
    • Johnny thinks he is Facebook’s customer. But their customer is where the money comes from. Which means the advertiser. The product is Johnny. The customer is the advertiser.
  • Speech: people learned not how to listen, but to talk.
  • Literacy: people learn not just how to read, but how to write.
  • Computers: People learn how to use, but not how to to program. This is a big loss.
  • I’m not talking about knowing how to change a sparkplug or fix the engine. I’m talking about how to drive the car. It’s the difference between being a driver and being a passenger.
  • It’s not just being a passenger, it’s about being a passenger, and the windows are blacked out.
  • This generation is not going to learn how to program. It took a thousand years for literacy to become commonplace. But we can teach people at least understand the biases of these technology. 
    • Guns don’t kill people, people kill people. --> But guns are biased towards killing people. More so than say, pillows.
  • Digital technologies are biased too. If we understand the biases, then we don’t use them as stupidly as we do now.
  • The 10 Commandments helped us through a transition from an oral tradition to a written tradition.
  • We want to stay in command of digital technology. Not in the control of digital technology.
  • These are not just rakes and hammers and things that you use. They are things that you program and then they go off and do stuff. Robotics and genetics and ... - they live on.
  • We want to build the world we want through them. Or at least 
  • Biases
    • The Bias of Time: 
      • Digital Technology is biased asynchronously. 
      • It’s not about speed, it that you could do them in your own time. Email vs. phone.
      • You could be smarter on the Well than in real life. You’d download the conversations, you’d read them, you’d have all night to think about and write replies, and then upload them. 
      • When people try to adapt themselves to this asynchronous behavior.... when they carry a smartphone, and get vibrated anytime we get a tweet or an email or anything. Then people get phantom vibrations. It’s a maladaption. People are  having the same issues that 9-1-1 operators used to get. Now everyone does.
      • People don’t want an always-on mentality. Your boss might want it, but you don’t really want. But we get suckered into it.
      • Command: Don’t Be Always On.
    • The Bias of Distance:
      • Digital technology is really good for things that are far away, not so good for things that are really close. 
      • You don’t want to text the person you are having dinner with. But you do want to text the person across the country.
      • Command: Live In Person. 
      • He followed a teenager through her nightly ritual of texting with friends to find out where the best party was. For two hours... And once she was there, her activity was to take pictures of where she was and share them to show that she had been there. But she was never actually living in the moment.
    • The Bias of Choice
      • Digital technology is biased towards discrete choice. 
      • Everything has to be chosen or it doesn’t exist. What happens when you have to choice all the time? You are guided by the choices that are available to you.
      • It’s like walking down the detergent isle. You have 300 detergents to choose from, but they are all detergents made by 3 companies.
      • Your Facebook status: are you married or single? You have limited choices, you  are forced to make a choice. 
      • Command: It is OK to choose none of the above.
      • If you are being forced to make a choice you don’t want to make, don’t do it. Don’t confirm to the program. Why are they making you do it?
    • The Bias of Complexity:
      • Digital tech looks complex, but it is actually biased towards oversimplicity.
      • If you are forced to make choices too earlier, at low resolution, at a great distance.
      • People are looking at the tools for amateur production, and think that because they exist, there is no value to professional production. Why should we pay for a journalist? Because corporations are spending hundreds of millions of dollars to convince you of stuff that isn’t true. Can’t we spend a hundred bucks to have some guy spend more than an hour writing a blog post trying to figure out what really is true?
    • The Bias of Scale:
      • Command: One size does not fit all.
      • Talk to any business person, and they want to know “can it scale?” It it can’t be everything to everyone, then they can’t grow their money exponentially.
      • This is what is leading to the downfall of business in America.
    • The Bias of Identify
      • Be yourself
      • Do whatever I do as me.
      • Once I go down the road of segmenting my life...
      • 94% of human communication is non-verbal. 6% is the words that you type.
        • your pupil size.
        • are you breathing with the person or not
        • are they nodding
        • it’s call “rapoor”. 
        • if you are living online, without all those social cues, you don’t know what they mean. you are living like a person with aspergers. you just don’t know.
        • It’s why analytic tools have such a hard time. Does “good one Obama” mean something good? or is it sarcastic? 
    • The Bias of Social
      • The Internet is biased toward Social
      • Content was never king, Contact was.
      • The military tried to use it, and what happened? The scientists talked about Star Trek.
      • Command: Don’t Sell Your Friends.
      • This will be the next big opportunity: to sell your friends, your friendship relationships. 
      • Companies are so focused on getting friends. When what would really be good is if they got their friends to be friends together.
    • The Bias of Openess
      • It is biased toward openess.
      • Command: Share, don’t steal. 
      • It’s so easy to steal in real life. Someone could break into my house and take stuff, it is easy. But we have a social contract that prohibits it. But we don’t have that social contract online.
    • The Bias of Purpose
      • It is biased toward purpose
      • Command: Program or Be Programmed
      • If you are not using the technology, then the technology is using you.
      • If you want someone to read, they have to learn to write. They don’t have to be James Joyce. They just have to string some words together. Then they can appreciate James Joyce.
  • We are the last people who were alive before digital technology. We are the last people who understand life before digital technology. We can choose to design technology to expose things or conceal. To support corporate economic structure, or to fight it. 
  • Q&A
    • Q: about privacy...
      • We are not consumers, we are people. 
      • The direct marketing industry was doing this stuff on notecards before they had computers. they had a card for every household on every block. 1 car or 2? dog or no dog? kids or no kids?
        • They wanted to save stamps
      • They can use factor analysis on Facebook to figure out what kids are going to be gay. They can predict who is going to get the flu based on twitter post frequency.
      • People are leaving this huge trail of data everywhere they do online.
      • Everything you do online might as well be chiseled in the side of the partheon. It seems to ethereal, but it is seriously there.
    • Q: what about the way facebook is program kidding to use their tools?
      • it’s like early MTV. MTV was watching kid culture, and kids were watching MTV, creating these kinds of feedback loops
      • kids use Facebook like we used to use the mirror: they primp themselves online, how they look. but facebook gives them the tools to create a monetizable social graph. That’s got biases in it.
    • Q: What about the the level of abstraction? Technology seems to be about abstraction.
      • When the alphabet was invented, people are to trust that the symbols used didn’t have hidden messages.