Managers are supposed to work on the system, at least in theory. 1on1’s are for the manager like server metrics are for the SRE. An early warning system of future problems. Ideally you can fix issues before the problem blows up into an alarm.
I'm not sure that is accurate. As a manager, I have a bunch of production metrics on my people. I can tell who's getting work done, who isn't, who has high defect rates in their work, who makes fewer defects, who is positive ROI, and who is not paying their keep. Where the one on ones are useful is when they are informed by the metrics, and those conversations don't take anywhere near one hour every two weeks. They take 10 minutes - 15 minutes, max.
Sometimes you gotta kick people to go take a vacation lest their mind/body takes an unplanned vacation for them. Even if the raw numbers are looking great. You’d prefer to have a planned outage wouldn’t you?
And hey, if you don’t need a full hour, it’s okay to make 1on1s shorter! Few people will complain about getting more time back in their lives.
But be warned: The good stuff usually comes out 5min before the end of a meeting when an employee says ”Oh yeah one more thing that’s been on my mind …”. It takes time to relax into that area of concern that’s a little scary to bring up.
No matter how explicitly you state it, ask for it, overcommunicate that you're approachable even if seemingly busy... people are averse to the impression that they're interrupting their management even when they have something important to discuss. When you create the space and have even that quick 10 to 15 minute chat every couple of weeks, you're creating space for your people to have your attention without worrying about getting your attention. And people often take advantage of that path of least resistance.
So many of the most important conversations to have with the team are less about their output and more about things they've got going on or need to know _despite_ their output. All the standard sprint metrics are just one piece of the puzzle.
"so, last week you had a -23.5% contribution... You usually are on the positive side, so what's up?" and the employee tells me that their lead stuck them on a project where they hand no experience, and didn't have time to learn how to do x or y before getting thrown at a ticket... or, "I'm having some issues with <personal>..."
Stuff as a manager you can sometimes help a lot with... and other times, well, you can be supportive. Just because numbers are involved does not mean we have to be cold and heartless... At the same time, I've found managing without numbers to just lead to cliqe-y political culture where people's ability to schmooze is rewarded more than their contribution to the team and that drives away the most effective contributors.
> And hey, if you don’t need a full hour, it’s okay to make 1on1s shorter!
Agree... I think I just realized that the exception should be a long 1 on 1. Just because I schedule 15 minutes doesn't preclude taking more time if there's something in the 1 on 1 that should take longer.
I've been doing engineering management for ten years and I've never seen a set of metrics that can tell you these things.
What software engineering metrics tell you who has positive ROI?
This is why when a cashier at the supermarket tells me that instead of waiting in line I can use the self check-out lanes, I tell her "I don't want to help a robot take away your job."
Usually they don't understand. But sometimes you can see them start to think about what's happening.
In the local grocery store at rush hour, cashier lines are long and self-checkout tends to be quicker for buying 3 items. Taking a whole cart into self-checkout is slower than a cashier, because the self-checkout has like a 5% chance per item of going into "assistance needed" mode.
get those good old shopkeepers to do it while you stand with your list out front.
I just want to pay for my items and get out of the store, in whatever way works.
I find places with scan as you shop apps way better than waiting in a checkout line. I get a running total of what I have in the cart, and when I'm done, I just leave without a line.
As pxl97 said, I preferred being able to scan things as I shopped and not have to stop at the checkout except to pay, but the one place around here that had that discontinued it a few months ago.
We need to push back hard against the idea that automation is "stealing" people's jobs; the promise of automation has always been that of more money for less work. We need to remind everyone of that, and reverse the trend of automation simply putting more and more money in the pockets of the already-wealthy at everyone else's expense.
Of course, this gets into UBI territory and making sure that as a society we are not just replacing menial jobs to then abandon the people who would have had those jobs.