Thread by @johncutlefish

Some quick tips for guiding your team to be more outcome focused.

1. Use the language of missions, bets, outcomes, etc. *alongside* whatever ppl are currently used to (output, dates, features, etc.). A trojan horse! No one will stop you. #proddev #ux #design

2. Periodically review outcomes...even for more prescriptive bits of work. Once a month is good. Invite everyone + tell good stories. Admit failures! No one will stop you. #proddev #ux #design

3. Very subtle...but use the statement order "Trying to [Outcome or bet] by [some intervention]". Keep hammering home the expected outcome. It'll start to stick. And ppl will realize the intervention is secondary. #proddev #ux #design

4. Small wins. Carve out one outcome/impact focused effort, and execute. Ppl default to output bc that is the currency of denial culpability AND tangible progress. You need to replace that with something better. #proddev #ux #design

5. Keep a "belief map" or "bet map" on the wall. Even when working on something prescriptive and output oriented, frame it as a bet that influences another bet that influences.... (you get the idea). #proddev #ux #design

6. Redo how you visualize work. On a reasonable level (missions, interventions, etc.) visualize a "measurement" column where work is percolating and getting tested. Reframing "done" is powerful (and subtle). #proddev #ux #design

7. Avoid pre-converging on solutions like the plague. Keep then problem-focused for as long as possible. If people ask for features, mention "candidate ideas" and that "we have more research to do". #proddev #ux #design

8. Take care of the basics: quality, flow, featuring-flagging, tooling, infrastructure, etc. No one can be outcome focused if the ship is sinking or if "the work" takes two quarters.

Hope that helps. #proddev #ux #design