product engineering @ transferwise

18
Alvar Lumberg @ TopConf Nov 20th 2014 PRODUCT ENGINEERING @ TransferWise

Upload: alvar-lumberg

Post on 02-Jul-2015

940 views

Category:

Leadership & Management


0 download

DESCRIPTION

Slides for a talk first delivered @ TopConf Tallinn 2014. Highlights cultural values of TransferWise and what practices we apply based on the values.

TRANSCRIPT

Page 1: Product engineering @ TransferWise

Alvar Lumberg @ TopConf Nov 20th 2014

PRODUCT ENGINEERING @ TransferWise

Page 2: Product engineering @ TransferWise

CULTURE

PRACTICES

PEOPLE

4

Page 3: Product engineering @ TransferWise

CUSTOMERS > TEAM > EGO

-­‐  no  politics,  no  career  ladders,  everybody  is  part  of  a  team,  everybody  contributes.    - pushing back ego very important for honest feedback   - a very small number of people who don’t directly affect customer happiness, mostly important admin functions

Page 4: Product engineering @ TransferWise

KPI driven vertical teams

7

I CAN FOCUS ON WHAT’S IMPORTANT FOR ME

I KNOW OWN MY KPIs AND I CAN MOVE THEM

IT MAKES ME FEEL STRONG & EMPOWERED

Page 5: Product engineering @ TransferWise

BRUTAL MVPs

6

Every change must serve a purpose

Test small, THEN polish and scale

PROJECTS AND FEATURES ARE INPUTS - NOT OUTPUTS

Page 6: Product engineering @ TransferWise

BLAMELESS CULTURE

8

DO FIRST, APOLOGIZE LATER

* People close up when blamed

* Fear stops learning and taking initiative

* Pushing people out of their comfort zone is hard anyway

Page 7: Product engineering @ TransferWise

PRODUCT CULTURE

7

They don’t let CxO/board tell them what to build

People are PASSIONATE about product

Build the right culture & it will build the product for you

- we have a very tight customer->product team feedback loop, pulling even tighter with metrics/dashboards

- we’re all responsible for providing input

Page 8: Product engineering @ TransferWise

CULTURE

PRACTICES

PEOPLE

4

Page 9: Product engineering @ TransferWise

7

WE STRUCTURED

OUR TEAM

AND ARCHITECTURE

FOLLOWS

WEAK OWNERSHIP

MODEL

KPI

TEAM

COMPONENTS

CONWAY’S LAW "organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations” - Melvin Conway, 1968

Page 10: Product engineering @ TransferWise

ROLES

We don’t believe in "enablers"

- no testers - no project managers

…but…

- automation - testing in teams - code reviews - pair programming - cross-functional teams

3

Page 11: Product engineering @ TransferWise

Loads of metrics(and not just metrics of loads)

-­‐ Cannot  change  what  you  don’t  track  

-­‐ Visualization  really  helps  kick  things  off

Page 12: Product engineering @ TransferWise

Payments  by  platform  vs  last  week

Page 13: Product engineering @ TransferWise
Page 14: Product engineering @ TransferWise

Issues by team

Page 15: Product engineering @ TransferWise

A bit on releasing

- planned releases daily - urgent fixes ca 1h cycle time

Page 16: Product engineering @ TransferWise

CULTURE

PRACTICES

PEOPLE

4

Page 17: Product engineering @ TransferWise

7

CULTURE WON’T SURVIVE

BAD APPLES,

ESPECIALLY IF GROWING SO

FAST

GROWING THE TEAM IS

EVERYBODY’S BUSINESS

ATTITUDE IS PARAMOUNT

SKILLS WILL BE LEARNED

BUILDING THE TEAMA CLASS PEOPLE HIRE A CLASS PEOPLE

Page 18: Product engineering @ TransferWise

PRODUCT CULTURE @ TW

CUSTOMER > TEAM > EGO

VERTICAL TEAMS with CLEAR KPIs

FEATURES ARE INPUTS, NOT OUTPUTS

BLAMELESS ENVIRONMENT

CONWAY’S LAW

VISUALIZE

[email protected] @alvarlumberg

5