|
|
|
|
|
by tyre
2474 days ago
|
|
I think the challenge with this is what happens when you’re in a growing product org. At a certain point it makes sense to have product managers. Maybe for a while you keep optimizing for developer usecases, but that’s no longer your customer (even if they are most of your users.) Larger revenue deals come from teams with more people and those are the ones that need more manager-focused features or where there manager is the buyer. From a go-to-market standpoint, you might put a ceiling on your revenue if you limit the addressable market to those teams that are still product managed by developers. Not that that’s bad! Just a thought. |
|
Club house has done a great job of organising information into stories, epics, milestones, projects.
All task manager products have some variation on these components but I've found clubhouses organisation of them to be the best.
It allows you to very quickly view the data differently depending on the context: stand up, sprint planning, PM trying to figure what's going on and what should be next.
My gut is that it turns out the way developers want to organise there work is actually a really sensible way of doing it, and so it scales up the management stack well.