Should my strategy be different for building something user's wont enjoy using?

[Albert]

Should my strategy be different for building something user's wont enjoy using?

Currently I'm building a training tool for people studying a specific hobby/career path. However, the training tool is pretty grindy if not really un-fun. Its pretty similar to leetcode to give you an idea.

The training tool should show positive results in the specific skills it trains after a few months; but I'm worried most new users aren't willing to use a new grindy training tool for several months to even prove it out.

I'm currently planning to follow the ycombinator basic advice in terms of product strategy (build fast, ship to users immediately, and get feedback quickly).

submitted by /u/nojobnoproblem
[link] [comments]