How does a software engineering team determine the value of a feature? My answer in thread #startup #product #softwareengineering
The value of a feature can be determined by three variables:
Effort required (the lower, the better)
Alignment with company’s goals (the more aligned, the better)
Shelf life (the longer, the better)
Effort required (the lower, the better)
Alignment with company’s goals (the more aligned, the better)
Shelf life (the longer, the better)
Let’s compare two examples below:
A - A landing page that is going to take 5 weeks to build but will only be available for a week. The reason for the page is to announce a new product offering, as per company’s goals
A - A landing page that is going to take 5 weeks to build but will only be available for a week. The reason for the page is to announce a new product offering, as per company’s goals
B - A small improvement to a CTA button on homepage that is going to increase signups (company’s goal) and will take 1 day to implement
The verdict: B is going to be more valuable than A.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
