
When you work in product management for a data-intensive company, it’s all about prioritization. Striking this balance between "keeping the lights on" and new feature development was my greatest challenge. Monitask provided me with the numbers to be able to do that. I use it to see how my team’s time is spent across core responsibilities. For instance, I create projects for “Platform Reliability,” “Client-Specific Data Requests,” and “Q3 Product Roadmap.” When we saw the 40% of our time on sprint being eaten away by ad-hoc data investigations it was epiphany -- no longer a gut feel but a measure. This enabled me to lobby for a dedicated data support position. The clean, project-based reports are what I use in QBRs to show exactly how engineering investment is aligned with strategic goals. Review collected by and hosted on G2.com.
Adding any form of tracking to a high-autonomy engineering team needs thoughtful change management. The first reaction was that it indicated a lack of faith in their expertise. We solved this problem by treating the data as completely transparent to the squad and only ever using it to improve systemic processes, never for individual performance assessment. On a technological level, the tool does have issues with context. If a developer is pair-programming, reading API documentation or drawing a system architecture in whiteboarded scribble inside a whiteboard app, that valuable time isn’t all necessarily recorded accurately as “productive.” We have to use the manual notes feature a lot, learn to flag such periods. Review collected by and hosted on G2.com.
The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.
Validated through LinkedIn
Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.




