>As a manager it's very hard to get everyone else on board with this
If management was easy then everyone would do it.
How about this for a start? You taking total control of your direct report's calendar. They have read only so can see what meetings you have scheduled they should attend. You book the meetings.
Anyone who wants a meeting has to disturb the manager (so there will be fewer requests) and pushback will have more force.
It's not whiny engineer saying they can't attend the meeting. It's the manager saying they are too busy.
You could also send just 1 report to a meeting instead of the whole team. Since you control the calendar you can choose who goes.
>manager-types try to come up with metrics to measure programmer productivity.
Plenty can. The CFO types look at profit per commit/schedule whatever.
A lot of middle managment types look at activity per commit.
The real issue here is that mangement by productivity data. Means most management is deadweight that can be replaced by a spreedsheet with the ability to send form emails to those falling behind on the metrics.
Anywhere else would be downsized, but management has enough power go protect it's own existence at the expense of the company.
>a SPOC that can filter all meeting requests by the email / 5 minutes / required vs inflated attendees / agenda / etc criteria before they even happen.
That's the project manager's job. The more meetings they allow. The more the project suffers. The more that are missed. The less poltical power. So they need to focus on fewer quality meetings for the ICs. More meetings for the PM.
>The problem is that when you do this, and then don't go to the meeting, and then a decision is made that you don't agree with, you are told, "well you had a chance but you didn't come to the meeting".
I would have if the item, I cared about was on the agenda.
This is why agenda are a) important b) should be sent out 24 hours or more before the meeting c) should be rigdly followed.
Anything else is either poor communication or a waste of productivity.
This gives everyone time to review the agendas. Making a decision which is worth attending,which is worth escalating.
Beside the manager should be representing you anyway.
>if you clearly weren't busy, because they don't equate coding with being busy. Sitting at your desk == not busy in their mind.
Coding yes. A skype meeting would be busy in their mind.
“UK-issued Renewable Guarantees of Origin and Guarantees of Origin for combined heat and power will no longer be recognised in the EU. If an existing contract with an EU countries’ electricity supplier or trader requires an EU-recognised Guarantee of Origin, it is possible that the contract could be compromised”
If management was easy then everyone would do it.
How about this for a start? You taking total control of your direct report's calendar. They have read only so can see what meetings you have scheduled they should attend. You book the meetings.
Anyone who wants a meeting has to disturb the manager (so there will be fewer requests) and pushback will have more force.
It's not whiny engineer saying they can't attend the meeting. It's the manager saying they are too busy.
You could also send just 1 report to a meeting instead of the whole team. Since you control the calendar you can choose who goes.