Content
@
0 reply
0 recast
0 reaction
✊ Mert from GodmodeHQ
@mmd
It is very difficult to figure out if you need to build a product that covers multiple tasks of a job or if it is a trap. Any good question anyone has to validate/test it?
3 replies
0 recast
0 reaction
eric.base.eth 🔵
@ericbrown.eth
What feature depth is required for each task? If you try to cover multiple will your product meet the specific needs of each task? Are there 1+1=4 scenarios where combining tools amplifies their respective value via shared workflows, data or insights? Is combining nice to have or meeting a burning need?
2 replies
0 recast
1 reaction
✊ Mert from GodmodeHQ
@mmd
Do you have a concrete way to understand this or an example where you made the distinction?
1 reply
0 recast
0 reaction
eric.base.eth 🔵
@ericbrown.eth
Feature depth: ensure you know the full problem space of the target user. Is there a standalone tool that can do it better than you if you combine features? 1+1=4: break the user need into its base components. Are some components being utilized by both (e.g. data)? Is duplicative work being done if they’re separate?
0 reply
0 recast
1 reaction