But my point is that stuff like Aha, at a smaller startup, can articulate business goals / customer stuff to individual issues on Github/Pivotal Tracker. That in itself is a software solution that supervises itself.
Not every startup fits that. But I think if they were open to it they'd like it. There is a downside though, it's 74/mo per user. Ugh. That cost.
https://www.aha.io/product/pricing
But agreed on blockchain in itself not making much sense in this case. The only times I've seen it intertwined with issues was with open source, cryptocurrency places like Gitcoin.
> Other than that, it either falls into micro management or into a tech lead role. As soon as a manager starts getting involved in technical decision it usually goes against the tech lead of the team or architect. If a manager asks for status updates constantly it's pure micro management and against the Project Manager.
You articulated this a lot better than I could. This is where I've seen manager's occasionally can harm more than they help.
I share your experiences at large firm and startups . What I feel is that tech leads, Architects or Sr. Engineers have lot of stress to deal with when they have bad managers which is ultimately bad for the team , company and individual development.
I think my question should have been phrased a bit differently as some level of mgmt especially at Director or Sr. Manager level should be sufficient to take care of hiring/firing, budgeting etc. Also with better tooling , conflicts can also be minimized as they are caused by egoistic views which are not based on data (think pros/cons of a solution etc).
So in short first level managers and Project manager roles can be minimized and/or their roles adjusted as shared resources across teams, not as product owners and team managers which is a mostly redundant role.
You need a manager to resolve conflicts between peers, to hire/fire people and to report to upper level. That alone takes a lot of pressure off a team... I've had experiences on both sides, management and individual contributor. Being a manager is pretty stressful for these 3 reasons. Other than that, it either falls into micro management or into a tech lead role. As soon as a manager starts getting involved in technical decision it usually goes against the tech lead of the team or architect. If a manager asks for status updates constantly it's pure micro management and against the Project Manager.
In other words, conflicts between peers, firing/hiring people and giving status updates on all the major issues is something that is hard to automate. We do need managers, but we need them to stick to these 3 things and that's it.