- I think my brain has achieved Friday flatline. 10 hours ago
- "Undaunted by data, I went forward anyhow." is my favorite phrase today. 14 hours ago
- RT @jmbronoel: Nice quote from Jenn: “A reference shouldn’t be something that lives in a database.” buff.ly/1lwO8Sr http://t.co/Mjsf… 2 days ago
- Join the Bay Area B2B Advocate Marketing Group. Our first meeting is April 9th in SF. Check it out and RSVP! - vip.infl.tv/r/1jz-399 3 days ago
- RT @RecruitLoop: [New Blog Post] 7 Ways to Really Conduct a Reference Check ift.tt/1q1tI4D 3 days ago
Can they actually be led?
Are you a bottleneck?
January 15, 2013Posted by on
Is your staff frustrated? Do you feel like they’re all inefficient? Is there a line every night out your office door and a long queue of email from your team awaiting your reply? If so, I have news for you – the problem probably isn’t your geeks. The problem is mostly likely you.
You have become a bottleneck.
You probably meant well. Or maybe your team is new. Or maybe you suck at documentation (heck, I sure do). You probably have great reasons for it, but it’s still an issue – geeks get incredibly frustrated when their boss becomes a bottleneck.
Honestly, it’s going to take significant effort to stop being a bottleneck. However, it’s entirely worth it – your team will be happier, your stress will be lower, and everyone will get a heck of a lot more done. Here’s what you need to work on:
- Trust. Look, you have to trust your geeks. You have to trust that they’ll do their jobs, and you have to communicate that trust to them. Yes, this means you have to accept that they might not do things exactly the same way you will, but if you don’t trust, well, get used to having to hire replacements.
- Communicate. Your geeks must be clear about your expectations, or they’ll constantly double-check things with you. Proactively communicate about what you expect to see from their work.
- Establish Patterns. If each project has a different reporting mechanism, you’ll get stuck telling everyone how to report on each new task. You’ll also get stuck double-checking their work, since they’ll never know what constitutes acceptable results and reporting.
- Teach. Giving someone step-by-step instructions differs from truly teaching someone. Spending extra time making sure your geeks understand why they’re doing what they’re doing, how you think about problems like the ones they’re trying to solve, and what success looks like means that they can pattern-match for subsequent tasks. And that means that they won’t queue outside your office as much.
Investing this time will certainly help with frustration, stress, and constant questions. You should note, however, that you’ll still need a good way to keep tabs on projects and problems once your geeks no longer ask you about everything. The best advice I’ve ever read on how to do that is in The One Minute Manager Meets the Monkey. It’s a quick read, and totally worth it (even if it’s not on Kindle yet. Grrrrr.)!