Slide 1

Slide 1 text

Rob Harr RUNNING AWESOME DISCOVERY PROJECTS @robertharr

Slide 2

Slide 2 text

No content

Slide 3

Slide 3 text

#DaytonStrong

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

We are hiring! https://seesparkbox.com/jobs Tangent!

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

YMMV!

Slide 8

Slide 8 text

Websites are software.

Slide 9

Slide 9 text

Determining scope on software projects at the beginning is irresponsible and impossible.

Slide 10

Slide 10 text

Reason 1: Determining scope on software projects upfront is impossible because: Clients are really bad at describing their actual needs.

Slide 11

Slide 11 text

We are bad at estimating work because we are optimistic. Reason 1: Reason 2: Determining scope on software projects upfront is impossible because: Clients are really bad at describing their actual needs.

Slide 12

Slide 12 text

We are bad at estimating work because we are optimistic. Reason 1: Reason 2: Determining scope on software projects upfront is impossible because: Clients are really bad at describing their actual needs. Business needs change over time. Reason 3:

Slide 13

Slide 13 text

Project don’t fail for technical or design reasons, they fail because of the people involved.

Slide 14

Slide 14 text

I believe the biggest risk for software projects is building the wrong thing.

Slide 15

Slide 15 text

No content

Slide 16

Slide 16 text

Running Awesome Discovery Projects DISCOVERY PROJECTS

Slide 17

Slide 17 text

What are Discovery Projects?

Slide 18

Slide 18 text

What problems are we trying to solve?

Slide 19

Slide 19 text

Committing to a large spend.

Slide 20

Slide 20 text

Trust.

Slide 21

Slide 21 text

Finding a the right client.

Slide 22

Slide 22 text

Training our clients how to work with us.

Slide 23

Slide 23 text

Reducing Risk.

Slide 24

Slide 24 text

A well defined problem, a set of goals, & determining the correct first step. GO AL

Slide 25

Slide 25 text

“We’ll know more about your project tomorrow than we do today.”

Slide 26

Slide 26 text

Client Happiness = A small delta between project expectations and project reality.

Slide 27

Slide 27 text

Client

Slide 28

Slide 28 text

Managing Client Expectations

Slide 29

Slide 29 text

Setting Client Expectations

Slide 30

Slide 30 text

Research Vendors Vendor Selection Negotiation Project Expectations Set

Slide 31

Slide 31 text

Research Vendors Vendor Selection Negotiation Project Expectations Set Expectations Managed

Slide 32

Slide 32 text

Selling Discovery Projects

Slide 33

Slide 33 text

“I don’t know enough to estimate this right now, I don’t think that anyone does.”

Slide 34

Slide 34 text

“There is no commitment to continue on with us”

Slide 35

Slide 35 text

Take the risk out of the project.

Slide 36

Slide 36 text

Initial phone call and gut feel estimate.

Slide 37

Slide 37 text

Estimating Discovery

Slide 38

Slide 38 text

No content

Slide 39

Slide 39 text

No content

Slide 40

Slide 40 text

Large Discovery: 3 - 4 weeks $40,000+

Slide 41

Slide 41 text

Medium Discovery: 2 - 3 weeks $25,000

Slide 42

Slide 42 text

Small Discovery: 1 week $10,000 or less

Slide 43

Slide 43 text

Running Awesome Discovery Projects RUNNING THE PROJECT

Slide 44

Slide 44 text

All projects should be designed as human experiences.

Slide 45

Slide 45 text

Prework In-person Meetings Wrap-up

Slide 46

Slide 46 text

Prework In-person Meetings Client Excitement Agreement Wrap-up

Slide 47

Slide 47 text

#1 Prework

Slide 48

Slide 48 text

Interviews

Slide 49

Slide 49 text

No content

Slide 50

Slide 50 text

Who to interview?

Slide 51

Slide 51 text

Feeling Heard.

Slide 52

Slide 52 text

Sample Questions

Slide 53

Slide 53 text

Tell us about your role and how it ties into the project. Exam ple

Slide 54

Slide 54 text

What are the primary business objectives with the project? Exam ple

Slide 55

Slide 55 text

Who will measure the success of the project? Exam ple

Slide 56

Slide 56 text

How we will measure the success of the project? Exam ple

Slide 57

Slide 57 text

Almost always the last question: (In your opinion) what will keep this project from being successful? Exam ple

Slide 58

Slide 58 text

Research

Slide 59

Slide 59 text

Content Audit

Slide 60

Slide 60 text

Competitive Analysis

Slide 61

Slide 61 text

User Interviews

Slide 62

Slide 62 text

#2 In-person Meetings

Slide 63

Slide 63 text

Who?

Slide 64

Slide 64 text

Studio Team

Slide 65

Slide 65 text

The controller & anchor

Slide 66

Slide 66 text

The pusher

Slide 67

Slide 67 text

The closer

Slide 68

Slide 68 text

Other smart people.

Slide 69

Slide 69 text

This is a giant trust exercise. Story

Slide 70

Slide 70 text

Home or away?

Slide 71

Slide 71 text

Designing the Meetings

Slide 72

Slide 72 text

No content

Slide 73

Slide 73 text

No content

Slide 74

Slide 74 text

No content

Slide 75

Slide 75 text

No content

Slide 76

Slide 76 text

Setting Ground Rules

Slide 77

Slide 77 text

Parking lot!

Slide 78

Slide 78 text

Stick to your schedule.

Slide 79

Slide 79 text

We always start with goals.

Slide 80

Slide 80 text

What makes a good goal?

Slide 81

Slide 81 text

Do not have implementation details.

Slide 82

Slide 82 text

Can be measured.

Slide 83

Slide 83 text

“Have an interactive, human website that shares relatable stories and reaches millennial and gen Z candidates.” Exam ple

Slide 84

Slide 84 text

“Increase how often and deeply users engage with our content.” Exam ple

Slide 85

Slide 85 text

“Increase revenue from new sales while maintaining renewals.” Exam ple

Slide 86

Slide 86 text

Don’t forget to have fun.

Slide 87

Slide 87 text

Our clients are wanting to be collaborated with.

Slide 88

Slide 88 text

Embrace the unknown.

Slide 89

Slide 89 text

It is ok to not have all of the answers.

Slide 90

Slide 90 text

“That is a great question, let me get back to you with an answer.”

Slide 91

Slide 91 text

We always end with prioritization and phasing.

Slide 92

Slide 92 text

Other ideas http://goodkickoffmeetings.com/

Slide 93

Slide 93 text

Don’t forget to share what the process will look like after you leave.

Slide 94

Slide 94 text

Prework In-person Meetings Client Excitement Agreement Wrap-up

Slide 95

Slide 95 text

#3 Wrap up

Slide 96

Slide 96 text

Prework In-person Meetings Client Excitement Agreement Wrap-up

Slide 97

Slide 97 text

Deliverables

Slide 98

Slide 98 text

Project Brief

Slide 99

Slide 99 text

Technical Strategy

Slide 100

Slide 100 text

Experience Strategy

Slide 101

Slide 101 text

Collaborative Estimate

Slide 102

Slide 102 text

No content

Slide 103

Slide 103 text

No content

Slide 104

Slide 104 text

A well defined problem, a set of goals, & determining the correct first step. GO AL

Slide 105

Slide 105 text

Running Awesome Discovery Projects CLOSING THE DEAL

Slide 106

Slide 106 text

Prework In-person Meetings Client Excitement Agreement Wrap-up

Slide 107

Slide 107 text

Keep it simple.

Slide 108

Slide 108 text

Negotiation

Slide 109

Slide 109 text

Know where you stand.

Slide 110

Slide 110 text

Running Awesome Discovery Projects THINGS I THINK I HAVE LEARNED.

Slide 111

Slide 111 text

Don’t write code. Don’t create wireframes. Don’t design anything.

Slide 112

Slide 112 text

RFPs

Slide 113

Slide 113 text

No content

Slide 114

Slide 114 text

Rob’s two basic rules for happiness in business:

Slide 115

Slide 115 text

Life is too short to work with people you hate. Rob’s two basic rules for happiness in business: Rule 1:

Slide 116

Slide 116 text

If you ever become annoyed by a client, it is only because you’re not charging them enough money. Life is too short to work with people you hate. Rob’s two basic rules for happiness in business: Rule 1: Rule 2:

Slide 117

Slide 117 text

THANKS! @robertharr [email protected]