liza-daly-cultivate-2015

65
Liza Daly CTO, Safari @liza Building an engineering culture Every business can be a technology business

Transcript of liza-daly-cultivate-2015

Page 1: liza-daly-cultivate-2015

Liza Daly CTO, Safari @liza

Building an engineering culture Every business can be a technology business

Page 2: liza-daly-cultivate-2015

June 2014 Tempe, AZ Confidential

I’m an engineer.

Page 3: liza-daly-cultivate-2015

June 2014 Tempe, AZ Confidential

I’m an engineer.I solve problems like an engineer.

Page 4: liza-daly-cultivate-2015

June 2014 Tempe, AZ Confidential

Turn a sales/marketing company into a technology company.

Page 5: liza-daly-cultivate-2015

June 2014 Tempe, AZ Confidential

Page 6: liza-daly-cultivate-2015

June 2014 Tempe, AZ Confidential

Page 7: liza-daly-cultivate-2015

June 2014 Tempe, AZ Confidential

Page 8: liza-daly-cultivate-2015

Other companies interviewed

Autopay

Etsy

Kitfox Games

Mapzen

+ 2 others

Page 9: liza-daly-cultivate-2015

June 2014 Tempe, AZ Confidential

1. Assess your tech culture. 2. Scale it. 3. Sustain and evolve.

Page 10: liza-daly-cultivate-2015

June 2014 Tempe, AZ Confidential

0. Culture wars.

Page 11: liza-daly-cultivate-2015

Bros? Ninjas? Rockstars?

Page 12: liza-daly-cultivate-2015

Tech culture

Page 13: liza-daly-cultivate-2015

Tech culture

Pull requests

Pairing

Code reviews

Rubber ducking

Page 14: liza-daly-cultivate-2015

“Help me make this better.”

Page 15: liza-daly-cultivate-2015

Good tech teams are extremely powerful collaborators—their efforts towards readable code, helpful comments, and "plug-and-play" systems go far beyond the necessary.”

Tanya X. Short - Director

Page 16: liza-daly-cultivate-2015

Assess your culture.

Page 17: liza-daly-cultivate-2015

Who is part of “engineering”?

Are the software engineers “rockstars” and the IT team “barriers”?

Page 18: liza-daly-cultivate-2015

Who is part of “engineering”?

Page 19: liza-daly-cultivate-2015

Make a bigger tent.

Page 20: liza-daly-cultivate-2015

Quality Assurance Professional and client services

Customer support

Page 21: liza-daly-cultivate-2015

Elise Wei - Engineering Director

My team’s work—client services—is not as simple to understand as the product team’s.

But we know the client voice is important.”“

Page 22: liza-daly-cultivate-2015

DevOps

Embrace methodologies that blur the lines between historically different teams.

Page 23: liza-daly-cultivate-2015

Embedded teams

Embedding individuals from one team into another as part of a rotation can build relationships and shared purpose.

It can also help technologists evolve their communication style into one which accommodates a range of backgrounds and experience.

Page 24: liza-daly-cultivate-2015

“I could proudly say I'd simultaneously helped

customers, improved my knowledge of the product, and befriended more than

a dozen coworkers through actual work.”

Page 25: liza-daly-cultivate-2015

“The support tour kicked my ass.”

Page 26: liza-daly-cultivate-2015

Continuous improvement

Page 27: liza-daly-cultivate-2015

Elise Wei - Engineering Director

Learning and teaching is part of our culture.

We have weekly meetings just for reviewing what people need help on.”

Page 28: liza-daly-cultivate-2015

Lara Hogan - Senior Engineering Manager

I feel happier if I can have success with others. I’d rather have a buddy. I really value having a team.”

Page 29: liza-daly-cultivate-2015

Diana Shkolnikov - Technical Team Lead

A low-functioning team might get work done, but it doesn’t know what it’s working towards.”

Page 30: liza-daly-cultivate-2015

Post-

Mortems

Page 31: liza-daly-cultivate-2015

Diana Shkolnikov - Technical Team Lead

As engineers, the only time we get feedback is when it’s negative.

You have to change this.”“

Page 32: liza-daly-cultivate-2015

Lara Hogan - Senior Engineering Manager

Culture is like web performance: When it’s going well you don’t notice it.”

Page 33: liza-daly-cultivate-2015

Scale it.

Page 34: liza-daly-cultivate-2015

Scale vertically

You can’t affect this change in the whole organization. You need buy-in from key people, as far up the chain as you can go.

Page 35: liza-daly-cultivate-2015

Kathy Keating - VP, Software Engineering

An entire company has to have agility. Everything starts at the top.”“

Page 36: liza-daly-cultivate-2015

You need lieutenants on the ground.

Scale horizontally

Page 37: liza-daly-cultivate-2015

Kathy Keating - VP, Software Engineering

When I mentor someone, I listen to how they do things and then tell them:

‘This is what you do today, but how can you do it better tomorrow?’”

Page 38: liza-daly-cultivate-2015

“Smart and gets things done.”

Page 39: liza-daly-cultivate-2015

Kathy Keating - VP, Software Engineering

Entrepreneurial leaders are the champions of someone else getting things done.”“

Page 40: liza-daly-cultivate-2015

How you know it’s working

“Your team is talking to each other!”

Page 41: liza-daly-cultivate-2015

Diana Shkolnikov - Technical Team Lead

Surround yourself with great thinkers. You’re the average of the 5 people you interact with the most.”

Page 42: liza-daly-cultivate-2015

Lara Hogan - Senior Engineering Manager

Having a diverse set of mentors has been crucial to my success.”“

Page 43: liza-daly-cultivate-2015

A healthy team has good affinities—they get each other’s edges. Everyone can’t have the same background.”

bethanye McKinney Blount - VP Engineering

Page 44: liza-daly-cultivate-2015

Tools of change.

Collaborative documents and team chat are often seen purely as planning and operational tools—

But they are tremendously powerful cultural drivers.

Page 45: liza-daly-cultivate-2015

CHMOD 777 *

Whenever possible, fail open.

Page 46: liza-daly-cultivate-2015

Morgan Evans - Learning and Development Program Manager

Engineers are familiar with post-mortems, and engineering failures have lots of facts—chat logs, commit messages. It’s harder to get to blamelessness with other teams.”

Page 47: liza-daly-cultivate-2015

Patches welcome.

A “pull request” has broad and powerful implications:

“I’m asking for feedback. I’m unafraid of doing that publicly. I’m expecting respectful criticism.”

Page 48: liza-daly-cultivate-2015

Diana Shkolnikov - Technical Team Lead

A dysfunctional team might do code reviews only when they have something to show off, not when they have a problem to solve.”

Page 49: liza-daly-cultivate-2015

Elise Wei - Engineering Director

I love when people code review me. I don’t think anybody’s timid about it.”“

Page 50: liza-daly-cultivate-2015

Evolve it.

Page 51: liza-daly-cultivate-2015

Onboard early and often.

Onboarding is critical in establishing, maintaining, and growing a culture.

Is new employee training a part of everyone’s responsibility?

Are they asked to meet with a diverse audience in the organization early on to build relationships?

Page 52: liza-daly-cultivate-2015

“Welcome, $HUMAN”

Page 53: liza-daly-cultivate-2015

Treats others with respect

Is always candid; always kind

Helps others

Invests in incremental self-improvement over time

Shares bad news early

Uses Safari for 10 minutes every single workday

Provides feedback to help their manager improve

Participates in every meeting or else declines

Avoids work outside of tickets

Always practices empathy

“Everyone at Safari…”

Page 54: liza-daly-cultivate-2015

Disenfranchises others due to identity, abilities, or location.

Is ever more than 2 minutes late without telling the organizer before the meeting starts.

“No one at Safari…”

Page 55: liza-daly-cultivate-2015

Reward craftspeople.

Engineers seek to improve their craft, and are naturally open to mentorship and continuous learning in a culture where those

activities are valued. Culture needs to be crafted.

Reinforce the value of “non-productive” activities like onboarding, training, and experimentation.

Page 56: liza-daly-cultivate-2015

The structure that the company puts in place is going to bias people towards different behaviors.”

Morgan Evans - Learning and Development Program Manager

Page 57: liza-daly-cultivate-2015

“Minimum Viable Bureaucracy”

Page 58: liza-daly-cultivate-2015

Diana Shkolnikov - Technical Team Lead

Avoid process for the sake of process. You’re striving for process for the sake of progress”

Page 59: liza-daly-cultivate-2015

Deploy continuous improvement.

Embrace continuous change and constantly re-evaluate processes and interactions.

What works early on may not work 6 months later.

Page 60: liza-daly-cultivate-2015

Tanya X. Short - Director

Make sure that each team member also has an emotionally safe way to regularly express anxieties, uncertainties, and criticisms of processes.”

Page 61: liza-daly-cultivate-2015

I don’t want everyone to be striving 100% of the time, but they should have enough imagination that they want something more. In aggregate we all get lifted up.”

bethanye McKinney Blount - VP Engineering

Page 62: liza-daly-cultivate-2015

Small pieces, loosely joined.

Establish a culture of timeliness.

Ask for feedback from people under you in the org chart.

Establish a world-writeable culture.

Fail open.

Page 63: liza-daly-cultivate-2015

Kathy Keating - VP, Software Engineering

How do you know if a culture is flourishing?

Does it feel right?

Are we making progress?

Are we happy?

Page 64: liza-daly-cultivate-2015

bethanye McKinney Blount - VP Engineering

Be brutally honest about what your company is: ‘This is what we do well & what we don’t do well.’

Now imagine a better version of that and plot a course.”

Page 65: liza-daly-cultivate-2015

Liza Daly @liza

Thank you

SAFARIBOOKSONLINE.COM