The hardest part of my job is the latitude of freedom I have to “do the right thing”. I love the feeling that my opinions really matter, that my work really counts towards a certain tangible outcome, but at the same time, it’s taken me a lot of effort to become comfortable with so much ambiguity – so much so that I almost wish that on some days, especially when the work is high-stake, someone can just come and tell me exactly what to do.
In my first year, the fear of “making a mistake” was often paralyzing. I would literally spend days flipping through my research and meeting notes, and delaying producing a deliverable until the very last minute. Then with amazing gusto and whatever genius was leftover from my grad school essay-writing days, I would pull all-nighters to pump out the deliverable, meet the deadline, and keep the clients happy.
Over time, it’s become clear to me that this kind of behavior is not sustainable. While I can’t change how I’m being managed (both up and down in the organization), I can change how I work. Below are several key understandings I’ve come to amass while on the job. I think on some level it’s such a fitting reflection of how we decide to live life as well.
1. More freedom really does mean more responsibility
More responsibility – this means more balls to juggle, and differently sized ones, too. This requires that you perfect your planning skills to effectively balance the meeting of immediate deadlines and how to drive results home long-term. If you keep your eyes too focused on the immediate present, as you execute through time some part of the project will fall through the crack, and the results may be unsalvageable. Or worse, you may not end up recognizing a key opportunity.
The biggest trick here is to never forget that no one is going to walk behind you with a whip, telling you when to do what. As you take a proactive stance to own a project, you become accountable for its outcome – if it doesn’t go well, you may still end up being the person to blame even if some part of it was never your fault in the first place.
2. Be your own critic
Very often, in a situation where you’ve been managing a project, you will know it best – where all the moving pieces are, what their statuses are, what are the pain points and contingencies. While others’ feedback are important, you can provide yourself with much more useful and objective feedback on how you did. Just because your boss says you did a great job doesn’t necessarily mean it’s 100% reflective of your developmental needs. Just because your boss says you did a terrible job doesn’t necessarily mean you’re useless.
Don’t shy away from this self-reflection process – critically examine your performance and be honest with yourself. Perhaps you’ll have trouble benchmarking your performance objectively – try to speak with your peers and learn how things are done in their companies, and how things can be done better where you work. Keep a library of “golden” deliverables for reference and consistently hold yourself up to that standard of work.
3. Pace yourself and delegate
The opposite of not owning the outcome is to let yourself work to death and own every outcome. I know this is something I personally struggle with – I have trouble “checking work at the door” when I get home, I have trouble saying “no” to a new project because I get so excited about adding value to something new and full of potential, and I have trouble accepting the limits of my capabilities (because sometimes I feel I have no limits).
Overtime I realized there are two types of people: the type who can do, and the type who can tell others what to do. If you think of this as a Venn Diagram, the part where the two circles meet, you get your “effective leader”. I used to think that it’s easier to tell others what to do, because there is the common misconception that if this happens, you’re not really doing any work.
This could not be further from the truth. If you’re really good at telling others what to do, you first need to have a big picture understanding of what needs to be done, then break this down to execution steps, then communicate it to the person doing the work including your expectations of the outcome and why doing a good job is important .Then you must let it go, take a step back and not micromanage. Then, chances are the outcome won’t be exactly as you’d anticipated, so you’ll have to go back and forth and make iterative changes, while not making it seem like you’re an obsessive compulsive asshole manager with no regard for other people’s feelings.
But you must learn how to do this, because no man is an island. Just relying on your own capabilities might be easier temporarily – you’ll be extremely efficient, focused, and your life will be simple and uncluttered. But over the long run you will be exhausted, and this is neither good for the company nor for yourself. Better to learn how to leverage resources around you, because this is actually how the world works. Trust me, I’ve learned this the hard way.
4. Don’t forget what’s truly important – the people around you
When you’re fairly junior in the workplace, like an analyst in some firm, your role is mostly just an Excel/PowerPoint monkey. This is fine as it builds fluency in the technical competencies from the ground up – after all, we all need to pay our dues somewhere. That being said, don’t get caught up in solely the technical competencies, because one day something else will become a much more important skill set for you – how you deal with people. How to amass the right team, make them work effectively together, communicate your expectations and lead them to the finish line, and motivate them and engage them along the way. Your time is limited, which is exactly why you shouldn’t focus solely on task execution – make the time to stay in touch with your network, talk, talk, and talk some more.
XXXX
That’s all for now, folks. I feel very strongly about this piece because I’m still in the office and trying to stay afloat Monday Madness, so this piece really serves as a sound reminder to myself as well. Hope your Monday was indeed a Funday, and not ironically.
Love,
V.