4 ms·
Working with other middle managers to align resources for upcoming projects according to company goals. For example, if you know you need to implement a foobar
by jerkstate 7y ago
Working with other middle managers to align resources for upcoming projects according to company goals. For example, if you know you need to implement a foobar next quarter that will require another team to implement a bazblee that you depend on, they can work with the bazblee senior manager to make sure the bazblee gets done, instead of the plumbus being requested by another group (that is, if the foobar and bazblee are more important to the company's goals than the plumbus - otherwise, they'll do the plumbus and you won't get your bazblee - so you probably shouldn't work on your foobar project)
Convincing other managers of your project's alignment with company goals is usually not an exact science, so your middle manager's ability to get these things committed to and done can be highly variable, depending on their connections with other middle managers and their ability to influence.
You can tell if you have a good middle manager if things you need from the rest of the company tend to fall into place, versus constantly being disappointed when you ask for stuff from other groups in the company.
Of course this all requires skillful ICs and team managers to manage up and make sure the middle managers know what they are doing and what they will need from the rest of the company.
- spork12 7y agoThe plumbus is a true multi-purpose tool though. It should always come 1st.
- closeparen 7y agoInteresting. We design a project inside the quarter where we committed to build it, middle managers could not possibly be fighting for dependencies during the planning cycle because engineers haven’t looked yet to see what they are. I’ve long suspected we should be writing design docs and putting them on the shelf one or more quarters before committing to execute on them, but what do I know.
- ralmeida 7y agoAt middle-management levels, dependencies are probably more abstract than system-level dependencies. Imagine your product has no mobile app yet, but one is in the roadmap for next year. Then someone in marketing is in talks with Apple about a chance to do a demo in a keynote or something. This would bump up the priority for the mobile app for this year, but other features previously in the roadmap have to be moved around. So there’s a level of managers which will go around negotiating the options.