4 ms·
Let me be a little more specific, with one pretty obvious red flag. I see a lot of 1-on-1s, which is fine, but: 1. 30 minutes for a weekly 1 on 1 is pretty lo
by caeril 5y ago
Let me be a little more specific, with one pretty obvious red flag. I see a lot of 1-on-1s, which is fine, but:
1. 30 minutes for a weekly 1 on 1 is pretty long, almost certainly a waste of time.
2. There's nothing after these 1 on 1s along the lines of "Planning time block for resources requested by Team Member B and E" or "Escalation call with Director B to handle sticking point M" or "Handling requirements conflict with product manager C over feature Q"
There are plenty of other issues here, but this is one clear issue. It sounds like this guy is is a highly paid sounding board. There's nothing in this schedule to suggest he's actually acting on information communicated during any of these meetings.
- jms703 5y agoThis! ^ If you’re getting tons of info from these meetings, but have no time to do anything to solve or correct those problems/issues, then you’ve created a false expectation and will let down your employees. I prefer the open door policy, ping me when you want to chat.
- tomnipotent 5y ago> ping me when you want to chat Many people feel uncomfortable "bugging" higher-ups and "wasting your time" when you have "some many other things to worry about". I've discovered that most people will not initiate, and I need to be the one to reach out and make things happen. Some of my biggest career snafu's could have been avoided if I just hadn't been so insistent on figuring it out on my own (or letting others do the same).
- awsthro00945 5y ago>30 minutes for a weekly 1 on 1 is pretty long, almost certainly a waste of time. 30 minutes for a weekly 1 on 1 is borderline too short, IMO. It depends on the person, but 1on1s are by far the most valuable and productive meetings that I have, and they often stretch longer than 30 minutes if possible. >There's nothing after these 1 on 1s along the lines of "Planning time block for resources requested by Team Member B and E" or "Escalation call with Director B to handle sticking point M" or "Handling requirements conflict with product manager C over feature Q" I count several meetings on their calendar that seem like exactly these things. Some of these things might even be covered during the 1 on 1s which you think are a waste of time. >It sounds like this guy is is a highly paid sounding board. Sounding boards are incredibly valuable and useful. We have people at my company that are literally just 40-hour-a-week sounding boards that probably haven't actually "done anything" in years, and they are some of the most critical people in the entire company.