Designing for Networks: Four Provocations

33
Designing for Networks: Four provocations for Harvard Arab Weekend 9 November 2013 by Ian Fitzpatrick

description

Slides from my talk to the Startup Track at Harvard Arab Weekend 2013

Transcript of Designing for Networks: Four Provocations

Page 1: Designing for Networks: Four Provocations

Designing for Networks: Four provocations !for Harvard Arab Weekend 9 November 2013 !by Ian Fitzpatrick

Page 2: Designing for Networks: Four Provocations

Hello. My name is Ian. !Principal / Chief Strategy Officer, Almighty Mentor, TechStars Mentor, Harvard Innovation Lab @ianfitzpatrick

Page 3: Designing for Networks: Four Provocations

A brief history: !Student of philosophy to founder of Unwrapped to music journalism to design research at Mattel to production at Havas / Euro RSCG to founder, Almighty

Page 4: Designing for Networks: Four Provocations

A caveat: !It will, occasionally, seem as though I particularly dislike marketing. And startups. This is not really the case. !I just believe in people.

Page 5: Designing for Networks: Four Provocations

Let’s start here: !Using channels and tools designed for the needs of larger competitors, but at a smaller scale, is not a viable strategy for resource-starved startups.

Page 6: Designing for Networks: Four Provocations

Here’s a useful way to think about ‘marketing’: !The price that organizations pay for improperly aligning the value they provide to the needs of users.

Page 7: Designing for Networks: Four Provocations

!Put another way, courtesy of John Willshire: !Make things people want > Make people want things

Page 8: Designing for Networks: Four Provocations

Value: !It’s what gets me to buy/use/pay attention to you because it’s more useful/helpful/enjoyable than the 1000 other important things I could/should/would otherwise be doing instead.

Page 9: Designing for Networks: Four Provocations

The product experience and the marketing experience are intertwined.

Page 10: Designing for Networks: Four Provocations

Currency is (a) measure of value, and it takes (at least) two important forms: !1. The direct value of a product, service or

experience (or information about it). 2. The indirect value of exclusive access to

that information, product or service.

Page 11: Designing for Networks: Four Provocations

Four provocations for the startup enterprise:

Page 12: Designing for Networks: Four Provocations

Provocation #1: Who uses what you make?

Page 13: Designing for Networks: Four Provocations

When someone asks what you do, do you describe a market need or a human need?

Page 14: Designing for Networks: Four Provocations

Audiences are passive receivers. Users are active participants. This distinction is not trivial.

Page 15: Designing for Networks: Four Provocations

It has never been easier or less-expensive to learn about what your users want and need.

Page 16: Designing for Networks: Four Provocations

It’s probably time to start thinking (far) beyond your vertical. !Only organizations talk about ‘best in class’. People talk in terms of what they like.

Page 17: Designing for Networks: Four Provocations

Provocation #2: It’s time to stop equating byproducts with ‘waste’. !When we make one thing, we almost always make something else. Too often, that byproduct goes unused (which is why we tend to confuse the two).

Page 18: Designing for Networks: Four Provocations

Stories are one kind of byproduct.

Page 19: Designing for Networks: Four Provocations

Data is another.

Page 20: Designing for Networks: Four Provocations

Data & stories about us will spread more than data & stories about you.

Page 21: Designing for Networks: Four Provocations

Provocation #3: Build for, rather than take from, networks. !It’s more than a magical place to push stuff. No one wants you at their dinner party.

Page 22: Designing for Networks: Four Provocations

Get to know Metcalfe’s Law. !The value of a network is proportional to the square of the number of connected users within it.

Page 23: Designing for Networks: Four Provocations

Adding scale to a network should create value for each user, not just each shareholder. !How does adding more nodes make your product, experience or service better for users?

Page 24: Designing for Networks: Four Provocations

As a rule of thumb, you should add more value to a network than you take from it.

Page 25: Designing for Networks: Four Provocations

Provocation #4: Design for non-linear engagement. !(and stop saying ‘engagement’)

Page 26: Designing for Networks: Four Provocations

Traditionally, communications hinged on the sequential consumption of messages, hence ‘communications stream’.

Page 27: Designing for Networks: Four Provocations

In an ecosystem defined increasingly by search and word of mouth (social), sequence is a lot less relevant to the way we process things.

Page 28: Designing for Networks: Four Provocations

Design for a crowd that comes in through the windows, not through the doors.

Page 29: Designing for Networks: Four Provocations

Try this:

Page 30: Designing for Networks: Four Provocations

Pick the most important user and build only with them in mind.

Page 31: Designing for Networks: Four Provocations

Go deep on that user, in their lives, where they operate. Look for gaps in value.

Page 32: Designing for Networks: Four Provocations

Place a lot of small bets. 50 ideas x $100 is better than 5 ideas x $1000.

Page 33: Designing for Networks: Four Provocations

Thank you for listening. !

@ianfitzpatrick