8 ms·
The idea that 1:1s with devs adding very little value to the team is… pretty wild. If you think 1:1s don’t add value, your slice of the reality of what even mo
by mercutio2 4mo ago
The idea that 1:1s with devs adding very little value to the team is… pretty wild.
If you think 1:1s don’t add value, your slice of the reality of what even modestly sized teams need to operate smoothly is so far from my experience I don’t think we’re likely to bridge the divide.
But to make a good faith effort: what is the job you think line managers are supposed to be doing, if not listening to devs, going to meetings you would prefer not to sit through, and writing up carefully documented feedback for the under-performers you seem convinced surround you at every turn?
- DanHulton 4mo agoYeah, honestly, as one of those managers with calendars full of 1:1s, I was kinda surprised at this. They’re frequently the most-useful meetings I have all week. The first ten minutes are usually kinda whatever, just catching up or chatting, but at around the halfway point, the REAL shit comes out. The things that were bothering them, or the task they were stuck on, or the team that’s been blocking them, or in better weeks, the ideas that have been really exciting them, or the people they’ve really been enjoying working with, or the tools they’ve been having success with, that kind of thing. All of that stuff is INSANELY actionable for me. Sure, I can do project-steering work until the cows come home, but all these “little things” I find out in 1:1s that let me reduce friction or create opportunities, that’s gold.
- JohnMakin 4mo agoWhy does this have to take place in a meeting? Why can't it be in a team slack? What value gain do you give talking an engineer through what's bothering them? Are they not capable of that independently of you? A middleman's value is quite limited, of course as a middleman, you don't see it that way, but I find these meetings extraordinarily unproductive, even anti-productive, depending on how bad the "manager" is.
- solumos 4mo agoYeah, if blockers are coming out in 1-on-1 meetings, that’s a really bad sign
- thih9 4mo agoFor the company, yes. But not for the manager - who now has insanely actionable stuff.
- dieselgate 4mo agoUsually people clam up and are not vocal during group meetings. I am not one of them but it's super common. 1-1s allow people to be more candid.
- JohnMakin 4mo agoI am not against 1 on 1's, but making that a regularly scheduled thing as if that adds value is kind of what I am arguing against. If people don't feel comfortable voicing something unless it is in private to their manager, that suggests to me two things - the manager/leadership is not fostering a collaborative environment, or the person needs to work on that (with the assistance/support of their manager), which I see as a manager's primary value gain, empowering their employees. Managing via 1 on 1's sounds (to me) like a complete waste of everyone's time and a little bit toxic. It also can create an environment encouraging people to go around each other and backstab rather than collaborate. I have been in a lead position before, I'd be very concerned and probably have a series of chats with any dev that sat on something like a blocker until we spoke one on one, or only felt comfortable speaking one on one. Some things do need to be spoken privately, and they should feel comfortable doing so/scheduling it, but a regularly scheduled thing as a way of managing, unless I am completely misunderstanding GP comment, is crazy to me. Of course I am speaking strictly manager/lead -> developer. A manager managing managers is probably quite a bit different and does require scheduling 1 on 1's regularly to align and adjust, but I wouldn't really know, because I've never been in that role.
- lovich 4mo agoYou are working against human nature if you think most people are not going to feel more comfortable talking about private matters in a 1:1 vs a public environment. You're also an asshole manager if you're giving any sort of negative feedback on a person in a public setting. You could always just schedule a meeting when someone needs a course correction, but then your employees who are clever little humans, will quickly figure out that any ad hoc meeting is going to be a problem for them and then have anxiety about those, even if its going to be a positive meeting for once. Have you never heard people joke that their boss asked them for a quick chat and they thought they were getting laid off?
- KaiserPro 4mo ago> Why can't it be in a team slack? Only a few people can adequately explain themselves through slack. It doesn't help that a lot of managers are _bad_ managers, and don't/can't/don't know how to run a tight 1:1. the point of the 1:1 is to provide a high bandwidth way of getting worries and steers from employees to management and direction back to employees. if there is nothing to talk about then cut the meeting short.
- mystifyingpoi 4mo ago> Why does this have to take place in a meeting? Conspiracy theory (which I believe in): because calls or in office meetings are not persistent and they are not recorded, but chat messages are persistent. Anyone can say they didn't say something, it gets harder in writing.
- habinero 4mo agoThat's not a conspiracy theory, that's intended behavior. You want your reports to feel safe to tell you things, you (or they) can always shift to written later.
- Aurornis 4mo ago> The first ten minutes are usually kinda whatever, just catching up or chatting, but at around the halfway point, the REAL shit comes out. I worked at a range of startups before joining my first corporate style company. This 1:1 meeting ritual was hard for me to adapt to. At the startups, particularly the high performing ones, issues were addressed immediately. If a problem arose you talked to the people involved quickly. If it needed a meeting you got everyone together as soon as they were available or you messaged your manager to get it in front of the right people quickly. If you saved things up for the next recurring meeting then it was a problem. When I joined a corporate-style company, that immediate and direct communication style was discouraged. Everyone was so busy with their meeting schedules that you were burdening them by bringing something up out of the regularly scheduled time slot. The 1:1s had a performative agenda you had to follow with the classic ten minutes of obligatory chit chat or ice breakers before it was acceptable to bring up the work issues that you had been holding on to for 3 days for this scheduled meeting where it was permissible to bring it up. All of the managers thought it was such a brilliant invention that this 1:1 format was surfacing the “REAL shit” that was “INSANELY actionable”, as if this was the only way to communicate. It seemed so absurd to me, having come from high performing startups where everyone just communicated to get their job done and was coached if they weren’t. Now I had to queue up all the issues and then follow the weekly ritual of chit-chat first, business second before I had a chance to bring it up in the culturally acceptable time slot. I think these rituals are really comforting and provide a sense of routing and predictability that some people like, but I also think it can become a performative replacement for good communication when it becomes THE acceptable way to surface the real issues.
- Sharlin 4mo agoThe thing is, "everybody just communicates" really does break down when the size of the organization grows past some limit. Everything is easy in a ten-person company, but that absolutely does not scale to a 1000-person company.
- Aurornis 4mo ago1:1s are designed for 1000-person communication. They're used by small groups of people like a manager and their team.
- MagicMoonlight 4mo ago[dead]
- eudamoniac 4mo agoFunny how high performing startups delivering real value don't have these meetings and they sort of appear out of the ether after the 1000th employee is hired.
- ewidar 4mo agoIn startups with less than 50 people (and I am being generous on the number), everyone talks to everyone all the time, so there is no need for these moments to extract key info to fix/improve situations, identify topics to push, ... But once the company is just large enough, there is no way you're going to interact with everyone in a meaningful manner (n^2 relationships and all that), and the simplest solution is intermediaries and 1-1s. [also, being sarcastic is unhelpful.]
- eudamoniac 4mo agoBut 1 on 1 meetings are not crossing team boundaries, they are always within the team which is pretty much always smaller than 50. There's no reason the team cannot "talk to everyone all the time" just because other teams exist. But instead this communication is replaced by meetings even though the ability to talk hasn't changed.
- estebandalelr 4mo agoBeautiful thought but really hard in real life. Do you talk to all members of the family, deeply, every day? Most would say no, so you need to open the spaces to do so.
- sumeno 4mo agoManagers DO cross team boundaries though, their peers are other managers. I can't talk to the 100 people in my department every week, but my manager can talk to their 9 peers, who each talk to their 10 reports.
- thelittlenag 4mo agoPrecisely! And this is true not just for managers but also higher-level ICs. Its ok for Senior and below to be team focused, but moving to the next level means broadening scope and that means talking with people, regularly!, outside your immediate team.
- Aurornis 4mo ago1:1s add value to a point, but I’ve worked at one company where the fixation on 1:1s started replacing useful communication. Like you’d try to talk to someone about an urgent issue and you’d be told to save it for your upcoming scheduled 1:1 on Thursday because they don’t have any time until then. Why don’t they have any time? Because they have so many 1:1 recurring meetings scheduled each week that they don’t have time for anything else. 1:1s started as a good way to formalize manager to report communication on a predictable schedule. This is good if the team isn’t regularly talking organically. Some company cultures take it too far and turn it into an excuse to make recurring meetings the focus of all work. I was requested to set up 1:1s not only with my team, but with each of the other teams we interfaced with, team leads on those teams, designers, stakeholders, interns, product managers who wanted to interface with us, the security team, and an endless list of other people. All the managers were just shuffling from one 1:1 to the next. Many never had time to deal with issues from the 1:1s because they were so busy moving on to the next 1:1. Middle management was always congratulating themselves on the success of their 1:1s because they said it was when they heard about all of the real issues they didn't know about. They didn't realize that by making themselves unavailable except for the 1:1s they were forcing this result. It was even worse when the problems involved multiple people or teams, which was almost always the case. Now you had to wait until Thursday to talk to your manager about it, who promised to add it to the agenda for his 1:1 with other team the following Tuesday. Then in that 1:1, the other team lead would say he'd bring it up with his schedule 1:1 with the person the Friday after that. It was like every communication queue only got processed once a week, so each hop added more delay. The managers would always tell is it wasn't supposed to be like that, but trying to direct would get you hit with "Let's talk about this in our next 1:1" The worst were the managers who had silly agendas for every 1:1, like my manager who blocked out the first 10 minutes for us to talk about our weekends with each other in a performative manner, 5 minutes per person. I could be dealing with an urgent issue in prod and he’d get angry if I tried to rush past the forced chit chat about our weekend to get back to business. If you haven’t seen calendars stuffed to the gills with performative 1:1s then this is all probably hard to believe, but it happens. Some companies got so fat with middle management that performative meeting rituals were the primary use of everyone’s time and you would be chastised if you tried to break the mold.
- 4mo ago
- watwut 4mo ago1:1 adds value if the managers spends most of the time actually managing and 1:1 is a place where he gets part of input for that. 1:1 with lead that spends most of the time doing 1:1 is pointless > what is the job you think line managers are supposed to be doing, if not listening to devs, going to meetings you would prefer not to sit through, and writing up carefully documented feedback for the under-performers you seem convinced surround you at every turn? Actually managing. The listening to devs and sitting on meetings is pointless if you are not actively using those meetings to organize, prioritize, plan and execute parts of plan.
- wrxd 4mo agoWith most of my managers 1:1 have always been a way for them to catch up with what I’ve been working on, despite doing a standup every single day so that the team knows what each other is doing.
- harrall 4mo agoI have standup every day so my manager knows what I am doing so my 1:1s are: - General sentiment about problems with the team and company that bother me but that I don’t have a solution to yet or decided how to bring it up with the team. - Fun / interesting projects I unilaterally decided to dedicate my working hours towards that I never asked permission to work on. Sometimes it ends up being something cool that my manager wants to join in on or promote to a bigger effort. - About our lives and what's going on.
- cebert 4mo agoSo basically useless unless you need to schedule a meeting with them
- tclancy 4mo agoThat's assuming an awful lot, mainly about how we no longer need human connection or context with other people to be able to succeed as a team. When I took over as an engineering manager, it took a couple of 1:1s per person but actually being interested in them as fellow humans made a huge difference. One of my reports, a former teammate who I really liked and got along well with, was carrying serious depression around every day. Learning that gave me a chance to help him out, discuss my experience so he knew he wasn't alone and let me make space for him to breathe. Which made him a more productive cog in the machine fellow human-bot!
- watwut 4mo agoNothing says human connection as much as scheduled meeting and necessity to have scheduled meeting to get or provide context. If the general mussings about a company, causual fun project and a little small talk about life require scheduled meething, you dont have those human connections with the team. Did you considered that people understand difference between human connection, relationship and being one of mandatory duties/meeting with someone who is actually apart and disconnected?
- lowbloodsugar 4mo agoAny good thing can be done wrong, and if it can be done wrong, the it will be done wrong.
- JsonDemWitOster 4mo agoI have a fraught relationship with 1:1s. Some days I curse the MBA who came up with this. Some days I'm rather ambivalent. Doesn't help that I'm naturally introverted and 1:1s is just a leech on my limited social battery. It's rather telling that IME 1:1s are the first meetings to be cancelled when the schedule tightens up. I'm not outright saying they are useless but 1:1s won't make a bad manager good and they're a nice bonus when your manager is competent. In the latter I actually get career and professional guidance.
- deleted 4mo ago[deleted]
- deleted 4mo ago[deleted]
- aprdm 4mo agoReally depends on the team etc. I don't think every team needs to have 1-1, certainly not weekly as a mandate. The best cultures I worked at didn't have 1-1 series by default