Menu

AeroPress: An origin story of design and tenacity

One of my favorite articles of the year so far is Zachary Crockett’s The Invention of the AeroPress:

The AeroPress was conceived at Alan Adler’s dinner table. The company was having a team meal, when the wife of Aerobie’s sales manager posed a question: “What do you guys do when you just want one cup of coffee?”

A long-time coffee enthusiast and self-proclaimed “one cup kinda guy,” Adler had wondered this many times himself. He’d grown increasingly frustrated with his coffee maker, which yielded 6-8 cups per brew. In typical Adler fashion, he didn’t let the problem bother him long: he set out to invent a better way to brew single cup of coffee.

It might sound like an article about coffee, but it’s more about entrepreneurship, product design, and the sheer tenacity of true inventors. Great read.

A product strategy approach to understanding Facebook, Instagram, and WhatsApp

A few months ago I wrote about the forces at work when people choose a product. I discussed the Jobs-To-Be-Done concept of Progress-Making Forces, and shared this diagram to illustrate what happens when we try to get people to use our product instead of someone else’s:

Progress making forces

In this article I want to discuss this framework in the context of a practical example: WhatsApp vs. Instagram Direct (now both owned by Facebook). I started thinking about this recently after MG Siegler wrote his post Going Against The Grain:

We’re seeing over and over again now that the behemoths can’t simply add a startup’s functionality into their own app as a feature and kill said startup. But it’s equally important to note that if you are able to establish your startup, especially those in app form, it may be hard to get your users to do anything other than what they originally came to do. Especially if the new functionality is against the grain in any way.

So, let’s consider this statement in the context of the Progress-Making Forces, and apply it to Instagram’s decision to add private photo sharing with Instagram Direct. First, let’s talk about existing photo sharing behavior. How do people currently send photos to each other? Facebook used to be the king of photos, but people are increasingly using messaging apps for this instead:

WhatsApp is processing 500 million images per day, compared to 400 million Snapchat (“snaps”) per day, which could include photos or videos. For its part, Facebook processes a comparatively paltry 350 million photos a day.

Enter Instagram Direct, a way for Facebook to try to claim back some of the private photo sharing pie. That’s the new behavior in the context of the the forces diagram. So the big question for Facebook is this: How do you get people to move their private photo sharing from WhatsApp (existing behavior) to Instagram (new behavior)? According to our framework, the progress-making forces need to be stronger than the progress-hindering forces, so let’s look at each force in turn:

  • Push of the situation. Is there anything people are not able to do by sending photos through WhatsApp that they wish they could do? It doesn’t seem that way. Some of the biggest advantages of using WhatsApp for photos are that (1) it’s completely private, and (2) it ties into your phone’s camera roll, so you have access to any photo, not just the ones from a particular app.
  • Pull of the new idea. Is there anything in Instagram Direct that could entice people away from WhatsApp? Again, it doesn’t look like it. Using Instagram Direct is simply more work than using WhatsApp for photos. If the photo isn’t in Instagram yet you have to import it. You have to apply a filter because that’s what you do in Instagram. Only then can you send it. But then the entire conversation is centered around photos. You still have to use WhatsApp for text messaging. So now you’re communication is fragmented, while it’s all seamlessly integrated in WhatsApp. There’s no pull here.
  • Allegiance to current behavior. How strongly are people attached to their WhatsApp experience? Extremely. The benefits of having all conversations and photos centrally located in WhatsApp can’t be overstated. You’re not just sending photos, you’re talking about life. It becomes a timeline of your relationships, and everything is there.
  • Anxiety of new solution. How worried are people that the shift would ruin their experience? Well, it seems there would be quite a bit of anxiety involved in moving to a product that doesn’t support the functionality you’re used to, and sits within a walled garden.

This analysis clearly shows that while the progress-making forces for moving people to Instagram Direct are relatively weak, the progress-hindering forces are extremely strong. This keeps people glued to WhatsApp, and it explains Instagram Direct’s apparent failure.

So what happened here? I think Facebook realized that they won’t be able to change people’s existing photo-sharing behavior. And that’s why they bought WhatsApp.

Whatsapp Instagram Direct

Space syntax and urban design

I really enjoyed Nick Stockton’s exploration of the space syntax concept in architecture in There’s a Science to Foot Traffic, and It Can Help Us Design Better Cities. He explains:

Space syntax [is] the science of how cities work. In the late 1970s, British architects Bill Hillier and Julienne Hanson hit on the idea that any space within a city — or the entire city itself — could be analyzed in terms of connectivity and movement. They reasoned that a city’s success depended largely on how easy it was for people to move about on foot.

This wasn’t a huge revelation. Studies reaching as far back as 1960s have shown walkable cities have higher property values, healthier residents, and lower crime. What set Hillier and Hanson’s ideas apart was the notion that a city’s geometry did more for movement than any other design factor. They argued that every other cog in a city’s engineering depends on the walkable grid. Cars, buses, trains, and bikes play a role, too, but only as much as they transport people to places where they then proceed to walk around.

There’s some great examples in the article, including a case study on the redesign of Trafalgar Square in London.

Where A/B testing does (and doesn’t) make sense

Peter Seibel discusses data-driven design at Etsy in his post Building websites with science. After going over the dangers of relying solely on A/B testing for product decisions, he concludes:

Ultimately the goal is to make great products. Great ideas from designers are a necessary ingredient. And A/B testing can definitely improve products. But best is to use both: establish a loop between good design ideas leading to good experiments leading to knowledge about the product leading to even better design ideas. And then allow designers the latitude to occasionally try things that can’t yet be justified by science or even things that my go against current “scientific” dogma.

This echoes Julie Zhuo’s thoughts in The Agony and Ecstasy of Building with Data:

You can’t A/B test your way into big, bold new strategies. Something like the iPhone is impossible to A/B test. If you had asked people or invited them to come into the lab to try some stuff out, they would have preferred a physical keyboard to a virtual one. If you had them use an early prototype of the touch screen where not every gesture registered perfectly, it would have felt bad and tested poorly. […]

Data and A/B test are valuable allies, and they help us understand and grow and optimize, but they’re not a replacement for clear-headed, strong decision-making. Don’t become dependent on their allure. Sometimes, a little instinct goes a long way.

This all relates back to the difference between variation (trying out different ideas) and iteration (small changes to improve an existing idea). A/B testing is great for iteration, but not for variation. For variation we need our brains, and lots of paper and pencils.

[Sponsor] Creative Labs Intelligent Wireless Sound System

A big thanks to Creative Labs for sponsoring Elezea’s RSS feed this week with their AXX 200 sound system!

We believe there’s so much more that your portable wireless speaker should do for you. That’s why we made the AXX 200.

The AXX 200 is a Bluetooth wireless speaker + Sound Blaster audio processor. This means a portable wireless speaker with power for real-time audio enhancement.

Intelligence. That’s what the AXX 200 brings to the table.

  • Make a call. Listen to music. AXX 200 intelligently adjusts the audio settings for you.
  • The Sound Blaster Central App for your iOS or Android device places the control in your hands.
  • Built-in quad array microphone – That’s FOUR microphones in a single wireless speaker for 360° of clear, unmatched audio pickup for voice calls and recording.
  • A wireless speaker that automatically cancels out noise during voice calls. For real.

It’s for work, it’s for play.
It can be everything you need it to be.

The AXX 200 is now on sale for a limited time at Creative.com and Amazon.com.

Doing it right vs. doing it over

Cap Watkins in Just Ship*:

We work in a world now where fast isn’t good enough. Where quantity is fairly regularly getting edged out by quality. You shipped twelve just-good-enough things this year? You’re about to get smoked by folks who shipped three of those things thoughtfully and holistically. Where you cut corners on twelve projects to get them out the door, someone else crafted three focused experiences and left themselves little-to-no design or technical debt.

This also describes why arbitrary release dates are poison to good quality products. It forces teams to cut corners to hit a date, which puts them in a more vulnerable position than if they just took the time to do things right.

Also:

How teens use Facebook and Twitter

Evie Nagy did a fascinating interview with danah boyd about her new book, It’s Complicated: The Social Lives of Networked Teens. On how teens use Facebook and Twitter:

They’re also more likely to have protected accounts, and use it to talk to a small group of their actual friends. To them Facebook is everyone they ever knew, and Twitter is something they’ve locked down to just a handful of people they care about — which is often the opposite of how adults use them.

A lot of the teens I talk to, they’ll have like 30 followers. It’s a small world for them, as opposed to trying to grow large followings. There are teens who are themselves microcelebrities, which is a different game. There are also a lot of teens who use Twitter around interests. An obsession with One Direction, and just talking to other One Direction people. That becomes Twitter, and then they’ll use Instagram with another group of friends. This one girl I talked to said, ‘Yeah, if you’re not into the things that I’m into, don’t follow me on Twitter.’

I’ve long been a fan of danah’s work, so I just bought the book and can’t wait to read it.

Related, Kayleigh Roberts wrote a very interesting article on how teens try to get celebrities to follow them on Twitter. From The Psychology of Begging to Be Followed on Twitter:

It’s not rare for a teen who is spamming to reach what is known as the tweet limit, something that the average user of the site might not even know exists. The tweet limit is 1,000 tweets per day, and many teens reach it regularly, especially when seeking the attention of a celebrity. It may seem excessive, but celebrities with millions of followers receive so many tweets, that it’s easy for even 1,000 to go unnoticed. Reaching the tweet limit can happen by accident, but it’s often a premeditated decision.

This is a world I didn’t even knew existed. I feel pretty old right now.

Designing for Google Glass

The small screens are coming, and we’re going to have to adjust our design processes accordingly. Emily Schwartzman does a great job of exploring how they worked through some of this complexity in Cooper, Augmedix and Google Glass: No Real Estate? No Problem:

Designing for Google Glass made us rethink the way we do software design. Many of our projects devote a significant amount of time to defining the framework of an application and developing the detailed design of key screens. When designing for Glass, we discovered that these phases needed almost no time, given the restrictive framework and visual language defined by Google. For future projects we might devote more time to refining personas and scenarios. We might even name the project phases a little differently—instead of “detailed wireframes” it might be “detailed scenarios.”

In general, Glass design projects will be focused more on flows than screens, and spending time on scenarios will help crystallize the flows.

More

  1. 1
  2. ...
  3. 102
  4. 103
  5. 104
  6. 105
  7. 106
  8. ...
  9. 201