That’s a good point. I did deploy an early version for my team of developers, and it helped me understand what each one was working on without constant status updates. It also surfaced context that was usually lost across Slack and meetings.
The challenge now is that I’m only one data point. I’m trying to figure out whether this pain is common enough outside my own team, and if so, who feels it the most—engineering managers, tech leads, or someone even outside tech (like finance or something).
When I had this problem, I mostly looked for better engineering analytics and developer productivity tools, but nothing really gave me how work was actually happening. That’s the hypothesis I’m trying to validate now. Let me know if you know of ways to reach these kind of audience that might potentially use this product
