How do you build a bare minimum feature?

Post by _3u10 » Sat, Nov 13, 2021, 4:57 AM UTC

Jugurtha wrote: post #4

_3u10 wrote: post #2

> Do you find it difficult to ship? Not really. Every successful company I’ve ever been at has sold the product before building it. Small companies do it directly with customers, large companies do it with focus groups or A/B testing. You can also do it with ads, make a lead gen ad for your feature, call the people who enter their info and sell them. The goal on any call is to close. Either you sell them on your feat…

Hi, do you have a blog or some place where you write about these topics?

Post by shavin47 » Tue, Nov 23, 2021, 5:53 AM UTC

tata71 wrote: post #14

latchkey wrote: post #13

Earlier quoted context omitted.

Another 'tool' I've used in the past: We had customers that wanted 'permissions' for their "sub" accounts so they could have fine grained access to features. They would threaten to not use our system until this was implemented. Implementing this feature was a lower priority and more difficult to implement for us then other revenue generating features (also a good way to prioritize things). The interesting bit is they…

How do you avoid promising or implying shit you don't intend to deliver? I'm going through this right now — people trying to use super-fine permissions (dozens of points!). Besides role-based groupings, there's no chance this fixes more issues than it causes in my case (less technical managers and workers using an SaaS). Any ideas and insight appreciated!