12 Ways To Improve the Web Developer & Account Manager Relationship

Post on 22-Jan-2018

1.904 views 0 download

Transcript of 12 Ways To Improve the Web Developer & Account Manager Relationship

@chrisgetman

Can’t We All Just Get Along?

12 Ways to Improve The Developer + Account Manager Relationship

@chrisgetman

Who’s here?

@chrisgetman

What are we talking about?

@chrisgetman

Dev & Accounts

• Greater knowledge gap between these teams

than others

• Greater personality gap between these teams

than others

• Greater opportunity for improvement

@chrisgetman

Communication

Personalities

Expectations

@chrisgetman

Empathize.But first…

@chrisgetman

Why did the developer leave

the restaurant?

@chrisgetman

Because of the table layout!

@chrisgetman

How many account managers does

it take to screw in a lightbulb?

@chrisgetman

Is it too late to make the bulb neon?

@chrisgetman

Same Team, Man.

Same Team.

@chrisgetman

Same projects.

@chrisgetman

Same goals.

@chrisgetman

Same team.

Different planets?

@chrisgetman

AM’s Job

• Schedule

• Scope

• Budget

Developer’s Job

• Build

• Solve

• Make Complex = Simple

@chrisgetman

The Conflict.

@chrisgetman

AM: “The client wants [insert request].”

Developer: “That will take 1,800 hours and/or is impossible.”

AM: “That’s a terrible solution.”

Developer: “You’re a terrible solution.”

@chrisgetman

Tips for Developers(How to help a marketer out)

@chrisgetman

Don’t be so logical.

@chrisgetman

A developer heads to the grocery store

with a note from his roommate…

@chrisgetman

“Get a loaf of bread,

and if they have eggs,

get a dozen.”

@chrisgetman

The developer comes home with a

dozen loaves of bread and says..

@chrisgetman

“…they had eggs.”

@chrisgetman

@chrisgetman

Sometimes nuance is

lost in translation.

@chrisgetman

And sometimes AMs don’t give

developers enough details

to pick up on the nuance.

@chrisgetman

So ask the AM:

“Is this really what you’re asking for?”

@chrisgetman

Empower your AM.

@chrisgetman

AM: “The client wants [insert ill-informed request].”

Developer: “That will take 1,200 hours and/or is impossible.”

AM: “That’s a terrible solution.”

Developer: “You’re a terrible solution.”

Opportunity(to educate the AM)

@chrisgetman

Empathize.

@chrisgetman

What are the goals?

When is the deadline?

What’s the client situation like?

@chrisgetman

No. It’s not your job.

@chrisgetman

But it will go a long way.

@chrisgetman

Tips for Account Managers(How to make your devs happy)

@chrisgetman

Empathize.Involve Devs Early

@chrisgetman

Q: How early is too early to bring

a developer into a project?

@chrisgetman

A: It’s never too early.

@chrisgetman

“I would love a project I know nothing

about dropped in my lap.”

-No One Ever

@chrisgetman

Advantages of Early Dev Involvement

• Better scoping

• Ownership from dev

• Less friction during project

• More face time (not kidding)

@chrisgetman

Empathize.Care about how

things are made.(Not just how the finished product looks)

@chrisgetman

“Just make it do this…”

@chrisgetman

If AMs better understood how

projects were built, they could:

• Add more value upfront

• Be more understanding of dev issues

• Better forecast and plan

@chrisgetman

Empathize.Don’t pass the stress.

@chrisgetman

Account managers are stressed.

@chrisgetman

All. The. Time.

@chrisgetman

Give your team a protected

space to do their jobs.

@chrisgetman

Empathize.Devs Don’t Know Everything.

(And that’s ok.)

@chrisgetman

When you ask a dev a question…

@chrisgetman

@chrisgetman

Developers are problem solvers.

@chrisgetman

Give them time to research.

Give them all the details about the issue.

@chrisgetman

Empathize.Devs aren’t IT.

(Just re-start your computer)

@chrisgetman

Seriously. Just re-start it.

@chrisgetman

*Pro Tip for Devs

Never fix anyone’s computer at the office.

Not even once.

@chrisgetman

Empathize.Leave them alone.

@chrisgetman

Headphones on?

@chrisgetman

Leave them alone.

@chrisgetman

Leave this dude alone.

@chrisgetman

It takes 23 minutes to return to the

original task after an interruption.*

*The Cost of Interrupted Work: More Speed and Stress, Gloria Mark, University of California

https://www.ics.uci.edu/~gmark/chi08-mark.pdf

@chrisgetman

Do the math.

@chrisgetman

4 Interruptions = 1 Hour Lost

@chrisgetman

(I’m looking at you Slack)

@chrisgetman

“Your team sent a total of 11,400 messages last week (that's 2,103

more than the week before). Of those, 5% were in channels, 7%

were in groups and 88% were direct messages.”

@chrisgetman

If you want your project done:

• Get the developer some time

• Leave them alone

• Make everyone else leave them alone

• Give them snacks

@chrisgetman

Empathize.How to work

better together.

@chrisgetman

Create a DLA(Department Level Agreement)

@chrisgetman

The DLA States

• The development team’s expectations of how work should be assigned to them.

• The account team’s expectations of how work should be approached.

• Ideal collaborative scenarios.

• Unfavorable collaborative scenarios.

@chrisgetman

Cross Department Presentations(Quarterly)

@chrisgetman

The more we know about the

other team, the better.

@chrisgetman

Dev presents to accounts.

@chrisgetman

Accounts presents to dev.

@chrisgetman

@chrisgetman

Hang out.

@chrisgetman

Talk about non-work things.

@chrisgetman

Strive to create real relationships.

@chrisgetman

End.