I think Sriram Krishnan does not like the Jobs To Be Done framework

For more context don't miss our full conversation 👇

@sriramk not a huge fan of how I’ve seen JTBD implemented but this take ain’t it. 1) every framework can be mis-implemented 2) JTBD doesn’t force you to not reckon with metrics trade offs 3) the Amazon ex is one of the most obnoxious decisions I’ve seen from a “customer obsessed” company

@sriramk

@sriramk A classic issue of "process zealotry." Every framework/process/methodology taken to an extreme isn't going to work. Either it reduces the work to checklists or it creates pointless circular arguments about "that's not how we do things."

@sriramk This is some insane editing

@sriramk @zacgoods is a master

@sriramk Lol. Tend to agree except for very different reasons. Also the switch method interviews that are part of JTBD are extremely useful.

@sriramk not sure Sriram has the right context on this @bmoesta explicitly calls out that without understanding how customers make tradeoffs, you never really know enough about the Job to design the product experience

Bad take imo. If you look at the proverbial S curve in the life cycle of a product, tradeoffs such as the one Sriram mentioned in this video will only matter much after PMF. Tradeoffs are a form of optimization. JTBD forms the basis for creation. Missing the forest for the trees, this POV.

@sriramk You have started an internet war Lenny 🤣

@sriramk 🫠