Related Posts
This is why I secretly avoid 1:1s with my manager!

More Posts
Job grades in Nokia??
Bain & Company Hello, I received an offer as a Senior Practice Manager at Bain. The profit sharing range is 0-12% in the offer letter. Is it typical to receive the midpoint (6%)? Also, what do the annual salary increases typically look like? Any insights are much appreciated. Bain & Company Boston Consulting Group McKinsey & Company
Need your suggestion on career choice Current role: business analyst (VBA automation) Y.o.e 9 years , relevant experience: 4 years CTC 8.25lpa Offer 1: TCS : 16.5 lpa Role : business analyst -payments domain (sdlc) Offer 2: Exl : 19 lpa Role: business analyst - process automation (not SDLC) Offer 3 Jp morgan (in pipeline) :expecting 20lpa Role: documentation specialist (not BA) - 601 Please suggest which one to chooseTata Consultancy JPMorgan Chase EXL
Additional Posts in Big Law
Have any GT offices other than NY matched?
New to Fishbowl?
unlock all discussions on Fishbowl.




You seem new to managing people. It’s not crazy for someone to send work product up to the person directly above them for review. If you don’t need/want to review, just tell them “No need for me to review unless you have any questions; can go directly to X!”
If they’re a first-year or something, it can be the nice mentor/coworker thing to do to provide some feedback the first few times they ask—sending things to partners is scary as a junior. But if you really don’t have time, just tell them….. it’s not hard to say “I won’t have time to review before you send to X, but let me know if there’s anything you need me to weigh in on.”
The fact that there is a one-year difference doesn’t mean much with out more context. Are they a new lateral? Have they worked with this partner before? Do you have more experience with this type of project?
I’m a 3rd year and sometimes even more senior associates will send me work to review, just because I happen to have more knowledge about the client / work stream.
Reading through this thread, I don’t get why there’s so much hesitation to just give feedback.
This is so surprising to me. As a mid-level, I require seeing all junior work product before it goes to a partner on my deals, and I think my partners’ assumption is that I have reviewed before something lands on their desk. Wonder if it’s a group/cultural thing
Same here. I’m a junior, but the assumption of every junior in my group is that whenever you do anything, you send it to the next person up the chain (whether that’s directly to the partner or to a mid level, depending on how the deal is staffed). Skipping over the mid level without being previously told you should would be disrespectful and insubordination haha
Mentor
Damn, relax. The junior is probably looking for some sort of mentorship from you/feels comfortable enough to make sure things look right.
Fair enough. I just want to respectful (not micro manage), transparent, and have a cohesive team.
“Unless you have specific questions for me, I don’t need to review.”
+1 on this not being catty at all. I’m a first year and a mid level or senior has told me the same. I had never worked with them before and wasn’t sure if they were the micro managey type who needed to have eyes on everything before it goes up the chain of command (have a different senior and a junior partner who is like this) or were okay with me sending directly to partner
Subject Expert
Ah the ol’ reverse delegation
Yup lol. Dunno whether to just fwd midnight email to partner and say “please see X’s draft attached. Let me know if you want me to compile drafts into one doc.”
This is weird. At my firm you generally send work to everyone up the chain regardless of whether it’s explicitly mentioned. If a partner tells a junior to do something and the junior sends it to the partner, 100% the partner thinks I’ve reviewed it already haha
Coach
Who is lead on the matter? I find this strange. In my group, someone is typically the lead associate and, yes, they will review another associate’s work. If there is no lead, we work collaboratively and suggest changes to each other.
Subject Expert
Hmm thats your job right? You need to review their work and bill for it if this is a junior (1st or 2nd year)
Even if it’s for someone my level or a year or two above, when we’re both on a case w a partner that I’m tight with and know their style, I’ll definitely review. I’m not spending hours and redlining every sentence, but giving general feedback if it’s not up to partner’s standards. I view my job as to make the partner’s lives that I work for easier — it’s an easy lift in these types of circumstances, where someone is literally hand-delivering you the opportunity.
Subject Expert
Just say “no need to send this to me first, ok to send directly to [x]”.
You probably want to clarify with the partner beforehand that you aren’t reviewing junior’s work product though.
I would verbally let the junior know that unless they are asking me a specific question, I'm not going to spot check everything for them. Then if you're worried and need an email trail: "Thanks. Let me know if you have something specific you would like feedback on, otherwise please send it on to XX for review."
I’ve been a 5th year, with a 4th year, third years and juniors under me at the time (terrible deal). It was fully expected that I review all their work before it goes to the partners. In situations where a deal I’ve been on had two seniors due to amount of work, it was clear which senior was responsible for managing and reviewing which workstreams. It may not be clear to this 4th year that the two of you are working parallel to each other instead of them below you? Would just gently convey your understanding is that you’re both acting as standalone midlevels on the matter and are expected to present your own work product directly to the partner.