what google learned about creating effective teams – live blogging from qcon

What Google learned about Creating Effective Teams
Speaker: Matt Sakaguchi
See the list of all blog posts from the conference

In software, we hire the best people, put them together and hope for the best. In sports, we focus on positions and teamwork.

Google was in NY Times for Quest to Make Effective teams

Matt talked about his path to Google. He was a police officer for 7 years until he got injured and physically couldn’t do it anymore. He then worked in retail. Then Matt upgraded the network to be faster and liked tech. THe CEO would “just randomly come and scream at people”. Had to leave toxic environment so went to Sony has manager of security guards 5am-2pm shift. Keep showing up; keep grinding; something will happen. Recognized as being underutiized and asked to look at operations to detect theft. Did that for a few stores. Still not making much money but doing something useful.

Recognized as being good at solving “weird problems” so Sony sent him to teams weird problems and fixing them. Had 27 people under him and an admin. Then moved to Walmart managing system admins and engineers. Got to learn basics of UNIX. First time managing engineers. Then BEA -> Oracle and Nexttag managing websites. At Postini, got to build a team. Postini got acquired by Google.

“snuck in the back door of Google, but still at Google”

Diagonsed with cancer. Greatful because helped realize what is important. Passionate about making work better. “We spend a lot of time at work we spend a lot of time in teams.”

Think about

  1. What kind of team are you on?
  2. What kind of teammate are you?
  3. What kind of learder are you?

On average

  1. 8.8 hours working
  2. 7.8 hours sleeping
  3. 1.2 hours caring for others

Diversity problems result in people not being able to be whole self at work (gender, race, orientation). Shouldn’t have to pause who you are for 8 hours.

With police, “if you aren’t scared, you aren’t human”. Good application to speaking and other “scary” things.

Everything is measured at Google. Even the placement of the tea/water/red bull/coffee. Example: moved M&Ms away from coffee machine, then hid it and then replaced with 100 calorie packs and measured reduction in calories.

Best teams

  1. Effectiveness – means results to executives, ownership/vision/goals to team leads and team culture for team members
  2. Tried to find algorithm for perfect team. Looked at dependendabiity of team, structure, extoversion, manageable worklowad, # of top performaers, tenure, co-location, impact of work, averge eel of team members ,consensus-drriven team, psychological safety, etc
  3. Most important five from most important to least importantL
    • psychological safety – knowing it is safe to make mistakes. Ok to take personal risks. Ok to bring up concerns. Know will be respectful open discussion
    • Dependency: can depend on teammates to do their part
    • Structure and clarity – enough to know what doing
    • Meaning – is work meaningful to you
    • Impact -is work important

Want a championship team, not an all star team.How a team works matters more than who’s on the team.

Components of psychological safety

  • Voice – am I heard. Are people just nodding or actually listening with respect
  • Trust – can I say anything without it being repeated?
  • Inclusion – not just inviting all people to the party, but making sure everyone has a good time

Set tone for psychological safety

  • Frame work as a series of learning problems; not execution problems – don’t just want to grind away DOn’t learn much in a performance environment because always on
  • Model curiosity and ask more questions. If team sees you ask “dumb” questions, everyone learns the answer and that ok to ask questions.
  • Admin your own failliblity. “Here’s my plan; tell me what’s wrong with it”

Tips

  • If team too negative, first question must be “how can we make this work”. Helps change mindset.
  • If you are the leader, try not to speak much if not running meeting. Putting your opinion out there too soon makes it harder for more introverted folks to state theirs
  • What are the top 3 things you enjoy doing outside of work. Make sure to spend time doing those things. Helps appreciate life. Do not cheat yourself

“The road to someday leads to a place called nowhere”

Fun talk to start the day! Matt is a great story teller. He had the Mac “machine name” screensaver in the background.When he showed the stats, I like how he just put them on the screen in silence rather than reading them. It really called attention to them.

here be dragons; container security – josh bregman

This is part of my live blogging from QCon 2015. See my QCon table of contents for other posts.

Risks

Need to prevent

  • “good” containers calling you accidentally
  • “good” containers calling you without your permission
  • “bad” containers calling you

production only workflow is an anti-pattern. network security isn’t enought

DevOps is about veleocity. Security and Risk Management can put on the brakes

Pod suurounds separation of concerns. Each actor (security, dev, etc) has own space

Can organize containers into layers

At event, can have ticket in advance or “will call” where show id. The later is like dynamic tokens.

Use host factory when provisioning

Impressions: the original speaker is sick and the subtitute has been at the company five weeks. I wouldn’t have know if he hadn’t mentioned it. I think I don’t know enough about containers though because some of this went over my head.

developing cultural inteligence – daniel seltzer – qcon

This is part of my live blogging from QCon 2015. See my QCon table of contents for other posts.

people aren’t logical. need to understand people; not just technology

with kids, you are creating a culture in your family. it’s about what you do, not what you say. modeling behavior. nice to see it played back to you as kids grow.

culture matters because:

  • shapes how people work togther
  • makes comanies great
  • to blame when people not doing right things anymore
  • powerful tool for new solutions

people need to be empowered and responsible

nobody should be allowed to treat others badly

culture in tech is creating shared expections for behavior

when something bad happens, does someone say not ok. if not, it becomes ok. culture is the accumulation of lessons like this

No manual on culutre. So learn to recognize, reason about and affect culture around you. In time, you gain the confidence to develop culture.

Conway’s law – structure of the architecture comes to reflect the organization of the company.

rules not written down, but we all know about the culture where we work

culture happens in real time – boundaries between people/groups, unexpected challenges, discovering the rules, rituals that reinforce, fear/anger/surprise/punishment/reward, stories are repeated

leaders set culture whether good or bad. if you set the culture, you became the leader

Once show dialog in team, info starts to flow in different ways.

“need to know” means “you aren’t going to know”

If had an API for culture:

Upper bound (ideal)

Attribute Default value Upper bound (ideal)
Control Centralized Distributed
Information Private Shared
Emotion Ego Empathy
Responsibility Avoidance Empath
Dissent Unacceptable Encouraged
Motivation extrinsic intrinsic
Planning risk based reality based
Humor serious playful
recognition taking credit giving credit
org structure static dynamic
collaboration fraught efective
risk avoid engage actively
truth to power dangerous supported

What can you do?

  • What is your personal culture
  • Choose positive culture over other rewards
  • Ask about culture on interview
  • Develop confidence to speak up when group and personal culture conflict.Thereare other places to go
  • Choose people for culturl fit. Model values you want to establish. Avoid ambiguity

Q & A

  • How handle public situations? People can only change so fast. “Let’s talk about this later.” Discuss one on one. Explain why a larger issue as group. Values group embodies are in conflict with your action. Choice of bringing closer to those values or looking for something new to do. Can progogate message via someone else on team in a softer/less direct way.
  • What do if team culture is in conflict with org culture? Doesn’t matter; have to be prepared to leave as leader to endorse values – those values are that important. Will cause conflict with values/goals of organization.
  • Culture takes time to develop. What if planting wrong seeds and waiting 6 months to find out? Takes time for person, but can still get team results faster. If inherit group, can take time. Will probably lose most of those people
  • When culture improves, people still have bitterness about past. How deal with that? Harder when not starting from scratch. Bigger organization limits how much one person can change. Even if CEO. Hard to change. Person has to want to change.
  • Fluid org structure. How switch teams when different culture on different teams? More about adapting over time. In startup, rate of change is so high, that changes daily/weekly. Don’t want people who will be upset if job/job title changes.
  • How balance against getting super talented engineers? So hard to find tech talent that becomes a moot question. Better to get lesser skilled engineer who will be productive and a good fit. Want someone who will pair rather than impeed team work.
  • What ask at interview to judge culture? Look at body language – eye contact, body language, flushing skin, talk to team members not just managers. Or ask, what would you do if X or tell me a story about X.
  • How “infect” organization to change? Person who cares ,know what is important, talks about it, etc. If people want it, they infect others as well. If in conflict with org values, need top down change