De Voorhoede

front-end developers

A great Meetup with a very high level of speakers and diverse talks, from more philosophical to practical.

Hooked on Behavior Design

April 24th De Voorhoede was at the Behavior Design Amsterdam meetup for the first time. This meetup-group talks about how you can base your design on human behaviour or, the other way around, how you can design to influence human behaviour. A very interesting topic for us as front-end developers as well. In our agile scrum working approach we work closely with interaction designers. Understanding about each others work field is a key aspect in this process. Besides that I’m always curious what the underlying principles are of the stuff I develop. So enough reasons to go to this meetup!

Kars Alfrink
Kars Alfrink explaining principles of behavior design

First Talk: Principles of Behavior Design

First talk was from Kars Alfrink, the principal designer at Hubbub. He talked about the principles of behavior design based on the COM-B system. COM-B is a ‘behaviour system’, involving three essential conditions: capability, opportunity, and motivation.

Kars used an intriguing quote in his presentation: “Just because you can measure it, doesn’t mean you should”. He explained that measuring is the first step in commoditization. Commoditization is the process by which goods and services that once had economic value and distinction end up becoming simple commodities in the eyes of the market consumers. Commoditization of design is bad, because it makes everything look and feel the same. At the end this will result in dull design, not interesting to the user.

Kars gave an example in games, where coded (and measured) behaviour prevents the user to be co-owner of the game. If you give the players more freedom, and give them the chance to play the game with there own rules, they will be much more connected and involved with your game.

Dariu Gavrilla
Dariu Gavrilla talking about 'Smart' cars

Second Talk: 'Smart' Cars

Second talk was from Dariu Gavrila. He is a senior research scientist at Daimler R&D. There he is leading a team that works on ‘smart’ cars, cars that see (and act). The fruit of his labor can be found in the Mercedes-Benz E-class and S-Class models (2013). The amount of technology that is put in those cars is incredible. For example, the cars have 8 cameras with all kinds of sensors that collect data. With that data you can do all sorts of things. For instance, scanning the road in front of the car for bumps and adjust the shock absorbers accordingly. You can glide over the road that way. Or what about adaptive cruise control, with which the car can drive itself?

Pedestrian Safety

The most important thing Dariu talked about was pedestrian safety. The smart cars can see when a pedestrian suddenly crosses the road, and can give the driver a warning or even use the brake by itself. Detecting whether there is actually somebody crossing the road is very hard. Thats why the cameras and sensors used in the cars are very advanced, and can make an almost 3d image of the surroundings.

Concept of a car brake with pedestrian recognition

Dariu also talked about what the future has in store for us. Daimler is now working on making the system even smarter. They want to predict in advance if a pedestrian wants to cross the road. Dariu and his team are using facial recognition and analyse the movement to see if this is the case. With facial recognition it is possible to see if a person sees the approaching car. They are also testing with camera’s facing the driver, so they can see if the driver is looking the right direction to see if a person is crossing the road.

Nir Eyal
Nir Eyal talking about his book How to Build Habit-Forming Products

Third Talk: Habit Forming

The final talk was from Nir Eyal, author of the book ‘Hooked: How to Build Habit-Forming Products’. He studies behaviour design and habit forming. Nir talked about how technology pursuits people. How big companies like Twitter, Facebook and WhatsApp manage to make people develop new behaviour.

The Hook

If your website or application has a business model that requires daily use to succeed, it’s important your website makes the user form a new habit. Nir has made a framework called ‘Hook’, that can help you achieve this. The Hook framework contains 4 elements: Trigger, Action, Reward and Investment.

The Hook
Figurative presentation of the 'Hook'

Trigger

A trigger can be external, like a button or alarm, or internal, like an emotion. An example of an internal trigger is people visiting Facebook when they are lonely, or using Google if they are unsure about some information. A good design keeps this internal trigger in mind. Something that is mostly forgotten.

Action

The next element is the action. This is what the user does after the trigger. The action should be a very small thing, and is done in anticipation of a reward. Like hitting the search button on Google, or pressing play on Youtube.

Reward

The reward is what follows the action. A real eye-opener to me was that the reward itself is not the most important thing. The anticipation for the reward is much more powerfull. This is called ‘the power of the unknown’. The reward can have many forms. For example, it can be a piece of content, like a search result on Google or a video on Youtube.

This was the part that fascinated me most of Nir's talk. It made me look at some web applications in a totally different way. Netflix for instance. I never understood why they don’t show a list of movies and tv series that are being added each month. Instead you have a slow and endless scroll page, where you go through all the content. Now I know why: because of the power of the unknown. You never know if you’ll find something good between all the mediocre content. And it works, at least for me. I regularly go back to Netflix, just to see if maybe I can find something I like.

Investment

The last element is the investment. Investment loads the next trigger of the ‘hook’. Every message on WhatsApp is an investment. It’s an open invitation for an external trigger to be returned. The external trigger in this case is the message you get when you receive a reply.

There is a lot more behind the hook framework from Nir Eyal. I just bought his book and I’m planning to write more about the ‘hook’ in the future.

This was a great Meetup. Very high level of speakers and very diverse talks. From more philosophical to practical, with real life examples. I can really recommend this meetup-group) for anyone who is interested in design and human behaviour. There is something for everyone!