@pigeonflight @tkimnguyen Perhaps a simpler way to think of it is
Feature/Effort -> Benefit + Audience -> Sellable [1-5]
Where benefit is just the inverse of user problem. Every benefit has user group/Audience.
Sellable is a prediction and is going to depend on how in demand a benefit is, how many different types of users the benefit is for and how unfulfilled that need is currently (ie is it a USP). Things that are hard to describe are also hard to sell.
There are also high value vs low value benefits... the ability to get insights into customer engagement is probably going to be worth more than giving more control over layout to content editors. In fact the kind of customers who care about engagement are probably going to have tightly controlled themes and would lock down something like mosaic if it was available so content editor control over layout might be a negative for them.
Not sure if this is easier to write out but here is a go.
- Mosaic
- Content editors control over layout = Webmaster type sites, intranets, smaller organisations
- 2
- Easier to learn/less support (via remove default pages and display views) = Webmaster type sites, intranets, smaller organisations
- 2
- Content editors control over layout = Webmaster type sites, intranets, smaller organisations
Anyone else?