I’ve been having trouble even starting to write about this topic because it’s such an interesting topic and something I’ve learned quite a bit about over the years — and continue to grow and learn about as I take on new teams!
As I’ve advanced in my career, I’ve gone from feeling like I need to learn every new technology or programming language (and getting overwhelmed and feeling inferior by the impossible feat) to realizing it’s impossible to know everything well. In the spirit of ruthless prioritization, I have to prioritize what it is I choose to know deeply (where I get in the weeds) and what I choose to only know at a surface level (usually relying on or deferring to the expertise of someone else who is in the weeds).
This approach to staying on the surface works really well when you can to defer to a colleague who you respect as an expert on their work (e.g. I understand we use XYZ technology but for any additional detail, talk to my colleague Jane in Engineering). And often times, a colleague will see this for what it is: trust that you will mind your own business because they’ve got their area under control!
It gets much more difficult when you need to do this with people who might report directly into you. Stay at surface and don’t know enough about their work? You seem out of touch (and isn’t it their job to “manage up” anyway?). Get in the weeds about everything they are working on? Now you are the dreaded micro-manager.
So how do you decide when to go deeper? There are tactics I’ve employed over the years that can help.
Continue reading “How to Decide When to Get in the Weeds”