timdaub on Warpcast

timdaub pfp

As a tech lead, how do you balance between the big picture roadmap and iterating on user feedback? I seem to always get stuck on either side 😔 E.g. Kiwi News has tons of issues on the low level APIs (users tell me). I could fix all of those vs. I could build a web UI and render them less relevant. What is best?

10 replies

0 recast

2 reactions

timdaub pfp

E.g. For neume.network, there were high risk/reward tasks, but I got bogged down in the daily iteration madness. But sometimes big picture roadmap in a big code base are insane edits that can take weeks to complete too. The more I think about it, I probably should just hire someone haha

1 reply

0 recast

0 reaction

Bayram pfp

Quota system: you define quota for major features vs bug fix vs user feedback. The exact split depends on project stage: early stage are more like 80-10-10; mature - 50-30-20

1 reply

0 recast

0 reaction

chrsmaral pfp

how I would takle it: 1.have a working core, just a single bare way to use it 2.make a general todo list and define contribution guidelines etc. so users who test can fix aswell 3.takle one major milestone which brings you the most gain-time ratio 4.get a feel for priorities and go on

2 replies

0 recast

0 reaction

notdevin pfp

What do you want, personally, as a power user?

1 reply

0 recast

0 reaction

Dan Romero pfp

We have: 1. Long term goal: 1B DAU using the Farcaster protocol 2. 6 month plan with goals and roadmap; expect a lot of change but good for accountability 3. Weekly — break things up into 1-week projects that "ship" and iterate on roadmap based on feedback / new data; avoid multi-week projects

1 reply

0 recast

0 reaction

Mac Budkowski ᵏ pfp

Mac Budkowski ᵏ

It might be controversial but I think at the early stage majority of user feedback is irrelevant. People will try to use your app in 100 different ways and every one of these ways will have some issues or some 'that would be cool to have', features. It's a distraction from the primary use case you should deliver on.

1 reply

0 recast

0 reaction

Nicholas Charriere pfp

Nicholas Charriere

This is a really hard question and a very good one. It’s because the answer isn’t obvious that there is a range of quality of tech leads. I like the saying that “it’s not data OR intuition, it’s data AND intuition”, and sometimes you have more of one that the other but both matter.

0 reply

0 recast

1 reaction

WebOfTrust pfp

Are you building something new or enhancing /adding module to already existing solutions. For new- user(most) feedback does not matters. Set long term, well defined goal, focus on feedback closely related towards achieving that goal while keeping an eye on critical feedback .

0 reply

0 recast

0 reaction

Tony D’Addeo pfp

holding them both in your head at the same time is the way

0 reply

0 recast

0 reaction

Fran pfp

I mentally separate bugs from user stories. A bug is something that truly does not work as intentioned / prevents using the thing. These should be fixed asap. A user story is basically a new feature request or preference. For these you prioritize based on difficulty and how much that user represents your target user.

0 reply

0 recast

0 reaction