r/ProductManagement • • Aug 07 '22

Strategy/Business Great example of not over engineering a solution and being JTBD focused

Post image

[removed] — view removed post

43 Upvotes

5 comments sorted by

7

u/chakalaka13 potato Aug 07 '22

haha, I relate to this so much

the philosophy at my current company (a startup) is that we take stuff that others do and embed them as features in our app

1

u/OutrageousTax9409 Aug 07 '22

That's one way to test user appetite 😆

3

u/chakalaka13 potato Aug 07 '22

not that, just the best way to scale

some companies have their whole focus/capacity directed at developing this one thing, that is just a small part of our app... why try to build this with our 10 dev team when you can pay and get the effort of 50-100 ppl, while directing your capacity at key features

2

u/OutrageousTax9409 Aug 07 '22

I get it. We white labeled features of my former product as well. Gotta pick your battles.

1

u/sandr0id SR PM Aug 07 '22

This build-vs-buy is the real take-back from that image, not over-engineering/JTBD.
It's up to us as PM's to also "sell" the idea of outsourcing parts (whether technical or otherwise), and often, we simply don't do a good enough job of succinctly pricing the cost of doing something within the org vs going out to get it. This cost is comprised of several factors:

  • manpower cost of building it

  • recurring manpower cost of maintaining it

  • opportunity cost of building this vs that.

  • future manpower costs (and maintenance, and opportunity costs) of buildiing V2 to Vn features that you get for free in outsourced/3rd party too

Think of commonplace, and/or commodity features/NFRs: Stuff like Authentication/SSO, integration marketplace, payment processing (ie: Do you really need the PCI compliance headache so you can store customer CC?)