Transform me, but please don't change anything

Transform me, but please don't change anything

4cdaa757e8db4ada5334a4187fff4c90?s=128

Gabrielle Bufrem

May 24, 2019
Tweet

Transcript

  1. Transform me, but please don’t change anything GABRIELLE BUFREM

  2. Every company is now a tech company

  3. The Rise of Digital Transformers

  4. The Rise of Digital Transformers

  5. Start-ups, you’re on the hook too

  6. Problems YOU ARE PROBABLY NOT SMALL YOU ARE PROBABLY NOT

    NIMBLE YOU ARE PROBABLY NOT AGILE YOU ARE PROBABLY SCARED OF THE STARTUP NEXT DOOR THAT JUST EMERGED TO EAT YOUR LUNCH YOU ARE PROBABLY WORKING ON YOUR DIGITAL TRANSFORMATION STRATEGY
  7. If those don’t apply to you, here are some more

    YOU ARE PROBABLY LOOKING FOR PRODUCT-MARKET FIT YOU ARE PROBABLY IN LOVE WITH YOUR PRODUCT YOU ARE PROBABLY SCALING UP AND NEEDING TO QUESTION EVERYTHING YOU THOUGHT WAS TRUE YOU ARE PROBABLY ALSO SCARED OF THE STARTUP NEXT DOOR THAT JUST EMERGED TO EAT YOUR LUNCH YOU ARE PROBABLY WORKING ON YOUR TRANSFORMATION STRATEGY
  8. It’s okay, this talk is actually for you

  9. YOU NEED TO BE WILLING TO CHANGE

  10. How to not do it @work @gbufremsays TODAY TOMORROW AGILE

    LEAN DESIGN THINKING MAY 30th, 2019 BURNOUT … Your team now hates you MAY 31st, 2019 MAY 2020
  11. The way not to do it @life @gbufremsays

  12. Manager, Product Management @Pivotal Data geek Coffee snob Travel lover

    Grab me for a during the conference and let’s keep the conversation going @gbufremsays Hi, my name is Gabrielle Bufrem
  13. Recommendations from the field 8 things you should actually do

    @gbufremsays
  14. Do the work! Buzzwords don’t solve real problems @gbufremsays

  15. Build a culture of psychological safety @gbufremsays Being able to

    be wrong is imperative for transformation Enable your team to be wrong and start rewarding for learning and experimentation instead of rewarding for being right Encourage your team to ask “How might we?” and enable them to place bets
  16. Pick one problem, build your island @gbufremsays

  17. @gbufremsays

  18. Decouple exploration from execution OUTCOME KPIs PROBLEM PERSONA FEATURE #1

    FEATURE #2 FEATURE #3 OUTCOME KPIs PROBLEM PERSONA FEATURE #1 FEATURE #2 FEATURE #3 EXPERIMENT #1 SUCCESS METRIC HYPOTHESIS EXPERIMENT #2 SUCCESS METRIC OUTCOME PERSONA EXPERIMENT #1 SUCCESS METRIC HYPOTHESIS EXPERIMENT #2 SUCCESS METRIC OUTCOME PERSONA Exploration Execution FEATURE #4 FEATURE #5 FEATURE #4 FEATURE #5
  19. Measure exploration based on learning and not being right SUCCESS

    METRIC KPIs ≠
  20. Ditch timelines @gbufremsays NOW NEXT LATER WAY LATER OUTCOME OUTCOME

    OUTCOME OUTCOME OUTCOME OUTCOME HYPOTHESIS HYPOTHESIS HYPOTHESIS HYPOTHESIS HYPOTHESIS
  21. Fund the problem, not the solution @gbufremsays

  22. Find a "shade of grey" that works for you Waterfall

    Agile @gbufremsays
  23. • Fund the problem, not the solution • Develop a

    culture of psychological safety • Pick one problem at a time • Find a process that works for you • Do the work • Decouple exploration from execution • Evaluate exploration based on how much you learn • Ditch timelines PROCESS CULTURE MONEY Cheat sheet @gbufremsays
  24. STAY IN TOUCH: @gbufremsays gbufrem@pivotal.io https://www.linkedin.com/in/gabriellebufrem/