Evangelizing Your Thing (Extended Edition)

107
Evangelizing Your “Thing” Lessons learned bringing hardware devices to hackathons by Rex St. John (@rexstjohn)

Transcript of Evangelizing Your Thing (Extended Edition)

Page 1: Evangelizing Your Thing (Extended Edition)

Evangelizing Your “Thing”Lessons learned bringing hardware devices to hackathons

by Rex St. John (@rexstjohn)

Page 2: Evangelizing Your Thing (Extended Edition)

Rex St. John (@rexstjohn)Internet of Things Evangelist, Intel

Page 3: Evangelizing Your Thing (Extended Edition)

We brought Intel Edison to more than 30 collegiate events last year.

Page 4: Evangelizing Your Thing (Extended Edition)

Many of the developers we met had never seen a Linux terminal before.

Page 5: Evangelizing Your Thing (Extended Edition)

We made these developers successful.

Page 6: Evangelizing Your Thing (Extended Edition)

And so can you!

Page 7: Evangelizing Your Thing (Extended Edition)

Here is what you need to know.

Page 8: Evangelizing Your Thing (Extended Edition)

An evangelist’s job is to maximize projects built with their technologies.

Page 9: Evangelizing Your Thing (Extended Edition)

Their job is to convince developers to choose their devices and finish projects.

Page 10: Evangelizing Your Thing (Extended Edition)

They are not salespeople, they are there for the good of the event.

Page 11: Evangelizing Your Thing (Extended Edition)

That means helping people no matter what technology they choose.

Page 12: Evangelizing Your Thing (Extended Edition)

Developers engage like this (hands on).

Page 13: Evangelizing Your Thing (Extended Edition)

When developers receive a gadget, their brains turn off.

Page 14: Evangelizing Your Thing (Extended Edition)

No one reads at a hackathon.

Page 15: Evangelizing Your Thing (Extended Edition)

That’s why it is called a “hackathon.”

Page 16: Evangelizing Your Thing (Extended Edition)

Reading is work. They came to have fun.

Page 17: Evangelizing Your Thing (Extended Edition)

If you have important information to communicate, you must do it up front.

Page 18: Evangelizing Your Thing (Extended Edition)

Developers will listen for a bit if they know they are getting hardware.

Page 19: Evangelizing Your Thing (Extended Edition)

But you need to keep it short. (45 minutes or less ideally)

Page 20: Evangelizing Your Thing (Extended Edition)

So do it in the first few hours.

Page 21: Evangelizing Your Thing (Extended Edition)

The first day of a hackathon is the most

important.

Page 22: Evangelizing Your Thing (Extended Edition)

85% of your work as an evangelist happens in

the first few hours.

Page 23: Evangelizing Your Thing (Extended Edition)

No one knows about your “thing.”

Page 24: Evangelizing Your Thing (Extended Edition)

You need to get them excited to use your

product.

Page 25: Evangelizing Your Thing (Extended Edition)

On the first day, people are still forming teams.

Page 26: Evangelizing Your Thing (Extended Edition)

By the second day, developers have made

their choices.

Page 27: Evangelizing Your Thing (Extended Edition)

It is often “too late” for you to convince them to use “your

thing.”

(although there are always exceptions)

Page 28: Evangelizing Your Thing (Extended Edition)

You are not the only company at the event

with a “cool thing”

Page 29: Evangelizing Your Thing (Extended Edition)

It’s a good idea to approach folks and

asking them questions…

Page 30: Evangelizing Your Thing (Extended Edition)

“So what are you thinking of building

this weekend?

Page 31: Evangelizing Your Thing (Extended Edition)

“Have you built many hardware hacks

before?

Page 32: Evangelizing Your Thing (Extended Edition)

“What programming languages do you

know?

Page 33: Evangelizing Your Thing (Extended Edition)

“JavaScript?

“Cool, we have this cool device called “Intel Edison” that lets you program hardware using

JavaScript!

Page 34: Evangelizing Your Thing (Extended Edition)

“We are doing a workshop after the keynote, stop by if you want to get a device.

Page 35: Evangelizing Your Thing (Extended Edition)

“We also have a prize for best use of Edison this

weekend, hope to see you there.

Page 36: Evangelizing Your Thing (Extended Edition)

You get the idea.

Page 37: Evangelizing Your Thing (Extended Edition)

You must market your device at the start of the event to build interest.

Page 38: Evangelizing Your Thing (Extended Edition)

You should also do a workshop.

Page 39: Evangelizing Your Thing (Extended Edition)

A collegiate hackathon may have 500 – 1,600

participants.

Page 40: Evangelizing Your Thing (Extended Edition)

There is only one of you.

Page 41: Evangelizing Your Thing (Extended Edition)

If you hand out devices without a workshop, expect to answer the same questions dozens of times.

Page 42: Evangelizing Your Thing (Extended Edition)

The average team is 4 people, 40 devices mean 120 developers

potentially interacting with your gadget.

Page 43: Evangelizing Your Thing (Extended Edition)

That translates into a lot of redundant questions…

Page 44: Evangelizing Your Thing (Extended Edition)

Where are the docs? How do I plug it in? Which USB do I

need to plug in? Where are the docs? Which USB do I

need to plug in? How do I get it online? Which USB do I

need to plug in? How do I get it online? How do I get it

online? Which USB do I need to plug in? How do I get it

online?

Page 45: Evangelizing Your Thing (Extended Edition)

You should really do a workshop to cover these questions.

Page 46: Evangelizing Your Thing (Extended Edition)

You should also have an intro slide deck for the

keynote.

Page 47: Evangelizing Your Thing (Extended Edition)

No more than 5-10 slides, don’t waste

people’s time.

Page 48: Evangelizing Your Thing (Extended Edition)

Don’t spend 15 minutes rambling.

Page 49: Evangelizing Your Thing (Extended Edition)

Developers came to build fun projects, tell them how they

can use your thing to do that.

Page 50: Evangelizing Your Thing (Extended Edition)

Introduce yourself, your product, what people can do with your product and your

prize.

Page 51: Evangelizing Your Thing (Extended Edition)

Then say “join me for a workshop after this to

get devices.”

Page 52: Evangelizing Your Thing (Extended Edition)

The end. Keep it simple, not

boring.

Page 53: Evangelizing Your Thing (Extended Edition)

Advanced evangelists often have interactive demos with

audience participation and live coding.

Page 54: Evangelizing Your Thing (Extended Edition)

You are a technical resource to support the participants, even if

they have questions on other topics.

Page 55: Evangelizing Your Thing (Extended Edition)

You are an ambassador on behalf of your company into the developer community.

Page 56: Evangelizing Your Thing (Extended Edition)

Leave a good impression.

Page 57: Evangelizing Your Thing (Extended Edition)

Why do hackathons matter?

Page 58: Evangelizing Your Thing (Extended Edition)

Hackathons are now a college sport(and students are in charge)

Page 59: Evangelizing Your Thing (Extended Edition)

“1,500 hackathons planned in 2014”–Vivek Ravisankar (@rvivek)

Page 60: Evangelizing Your Thing (Extended Edition)

*a non-complete list of sponsors for HackGT, in it’s first year!

Competition for developer attention is intense

Page 61: Evangelizing Your Thing (Extended Edition)

Attendence Total Prize Value

MHacks ~1,300 ~$31,000

PennApps X ~1,300 ~$30,000

CalHacks ~1,200 ???

HackGT ~700 ~$60,000+

HackRU ~700 ~$10,000+

DubHacks ~500 (capped) ~$10,000+

HackTX ~500 ???

Attendance is taking off(a few events we attended this year)

Page 62: Evangelizing Your Thing (Extended Edition)

Hardware + wearables stand outBe the first device students learn to hack on

Page 63: Evangelizing Your Thing (Extended Edition)

Developers cross-pollinate + talkStudents may attend dozens of events before graduating (travel

reimbursements)

Page 64: Evangelizing Your Thing (Extended Edition)

Some Lessons

Page 65: Evangelizing Your Thing (Extended Edition)

Developer Success Is The Only Metric

Developer Success Is The Only MetricDeveloper Success Is The Only Metric

Developer Success Is The Only Metric

Developer Success Is The Only MetricDeveloper Success Is The Only Metric

Developer Success Is The Only Metric

Developer Success Is The Only MetricDeveloper Success Is The Only Metric

Developer Success Is The Only Metric

Developer Success Is The Only MetricDeveloper Success Is The Only Metric

Developer Success Is The Only Metric

Lesson #1: Developer Success Is The Only Thing That Matters

Not impressions, conversions, devices distributed etc

Page 66: Evangelizing Your Thing (Extended Edition)

The target metric is “projects built per device distributed”

Page 67: Evangelizing Your Thing (Extended Edition)

If you hand out 40 devices and get 3 projects, you are

probably doing something wrong.

Page 68: Evangelizing Your Thing (Extended Edition)

We averaged 50% or greater projects per device issued. Sometimes 80% or more.

Page 69: Evangelizing Your Thing (Extended Edition)

These metrics can vary wildly based on the schools and participants, nature of the

hackathon.

Page 70: Evangelizing Your Thing (Extended Edition)

Hardware focused hackathons at schools with strong EE

departments often did well.

Page 71: Evangelizing Your Thing (Extended Edition)

Lesson #2: “Hackathon ready” is a higher standard of ready

If your product is “hackathon ready,” then it is ready.

Page 72: Evangelizing Your Thing (Extended Edition)

Lesson #3: Hackathons are not a branding exercise

Looks like marketing, smells like marketing, sounds like marketing…not marketing

Page 73: Evangelizing Your Thing (Extended Edition)

“We traveled 2,000 miles to be here and spent 72 hours for nothing because of you”

Lesson #4: Your device can ruin a team’s entire event

Page 74: Evangelizing Your Thing (Extended Edition)

We are not perfect, sometimes technology

doesn’t work well.

Page 75: Evangelizing Your Thing (Extended Edition)

Apologize and take the blame and promise to see

that the problems are fixed.

Page 76: Evangelizing Your Thing (Extended Edition)

“I am going to send an email about this now, we will make

sure this doesn’t happen again

Page 77: Evangelizing Your Thing (Extended Edition)

“Can you give me your email? I will follow up with you when I

hear back about this next week

Page 78: Evangelizing Your Thing (Extended Edition)

Consider sending them a “make good” item if you can do so

Page 79: Evangelizing Your Thing (Extended Edition)

DXDeveloper Experience

Page 80: Evangelizing Your Thing (Extended Edition)

Introducing HDXHardware Developer Experience

HDX is synonymous with strong performance at hackathons

Page 81: Evangelizing Your Thing (Extended Edition)

How do you achieve HDX?

Page 82: Evangelizing Your Thing (Extended Edition)

Work backwards from “hackathon conditions” to your product

Page 83: Evangelizing Your Thing (Extended Edition)

8-36 hours to build a project with your hardware, no time to waste

Page 84: Evangelizing Your Thing (Extended Edition)

Power on, Wi-Fi, BLE in less than 10 minutes

Page 85: Evangelizing Your Thing (Extended Edition)

Expect HTML based login screens, isolation mode to be turned on

Your “thing” must handle bad Wi-Fi gracefully, be useful regardless

Page 86: Evangelizing Your Thing (Extended Edition)

Tips & Tricks

Page 87: Evangelizing Your Thing (Extended Edition)

Pro-Tip: Bring your own Wi-Fi routers.

Page 88: Evangelizing Your Thing (Extended Edition)

Collegiate Wi-Fi tends to be terrible, infested with

HTML login screens.

Page 89: Evangelizing Your Thing (Extended Edition)

This makes it really hard to build hardware projects on

most devices.

Page 90: Evangelizing Your Thing (Extended Edition)

Make sure to also provide Wi-Fi at the end of the event during

project demonstrations.

Page 91: Evangelizing Your Thing (Extended Edition)

You can usually find open ethernet jacks.

Page 92: Evangelizing Your Thing (Extended Edition)

Pro-Tip: Load useful software onto USB sticks to

avoid large downloads.

Page 93: Evangelizing Your Thing (Extended Edition)

Start developers 30-50% of the way to their goal

Sample code and prefabs for common use cases

Page 94: Evangelizing Your Thing (Extended Edition)

Finished Projects = Happy Developers

This is the only marketing you need to worry about

Page 95: Evangelizing Your Thing (Extended Edition)

Ration hardware (conditional loans)Hardware is for teams who are building, not stuffing in backpacks

Page 96: Evangelizing Your Thing (Extended Edition)

Set up a supply tableExpect people to show up with nothing

Page 97: Evangelizing Your Thing (Extended Edition)

Document, share relentlesslyDon’t let your success disappear down the “memory hole”

Page 98: Evangelizing Your Thing (Extended Edition)

If it isn’t documented, it didn’t happen.

Collect team names, take pictures of *every* project built with your technology, save links to projects posted online. Hackathon success is

ephemeral, you need to keep a record of what happened or it will disappear.

Page 99: Evangelizing Your Thing (Extended Edition)

Offer prizes.

Page 100: Evangelizing Your Thing (Extended Edition)

Prizes should be geeky in nature, developers don’t want

money, they want fun toys and things to play with.

Page 101: Evangelizing Your Thing (Extended Edition)

Generally we spent $450 on three prizes for a team

of up to four per event.

Page 102: Evangelizing Your Thing (Extended Edition)

Prizes are important to motivate developers to use your products.

Page 103: Evangelizing Your Thing (Extended Edition)

Tell stories about your productBe prepared to inspire developers with ideas

Page 104: Evangelizing Your Thing (Extended Edition)

Developer Success = Your SuccessDeveloper success is the only metric

Page 105: Evangelizing Your Thing (Extended Edition)

Celebrate developers.

Use social media channels to reward developers with public recognition, doing this regularly leaves a strong positive impression

on your organization.

Page 106: Evangelizing Your Thing (Extended Edition)

Learn.

Ask developers to share their code, chances are solutions built by one developer will be needed by other developers at other events. Be

proactive about documenting solutions to common problems.

Page 107: Evangelizing Your Thing (Extended Edition)

Forketing

And read this.