Related Posts
How do you all deal with the guilt of leaving a comany/ team? I have been working at Microsoft for 1 year now, and seriously considering moving. I find the code base to be very legacy and I mostly work on obscure bugs that I spend so much time on, mostly due to navigating this large code base and not having much docs to refer to. Hence I find the job slightly unsatisfying, and that I could learn more elsewhere. However, I love the wlb, the team and company culture. The guilt stops my applying.
How did you all get into PM?
Layoffs at Ogilvy NYC...
Additional Posts in Consulting
Shots fired. Your move Deloitte.

Curious: is CSR metal or plastic?
New to Fishbowl?
unlock all discussions on Fishbowl.



Create a checklist of the usual mistakes and refer to them before sending it out perhaps
If it was always client ready when you sent it to him, he has no purpose. Reset expectations with him.
Have someone else on your team review first as well.
I would resist time pressures a little bit if it means catching mistakes. Most of the time, an extra 30min is not going to make a huge difference to your manager but gives you enough time to double check your work. If mgr is really tight on time, they'll probably come ask what's taking so long, then you can say it's done but you're double checking. If they don't want to wait, then you can send it to them but they know it hasn't been checked. Usually though, they'll probably give you that extra 15-30min to finish checking.
Review everything 3 times before showing it to others.
Checklist is the best suggestion -- OP you'll get better/faster at going through the checklist as time goes by. Make sure mistakes you've recently made are the first things you check for; you'll look the worst for being called out for the same thing repeatedly
Read it backwards. Weird but it works.
Delay delivery by 10-15 mins and then revisit
This may not go over well with your manager, but when I finish something, I review, I step outside, take a 10 minute walk, then go back print my shit and review on the hard copy
Printing it helps me so much - I will always catch things on paper that I miss on screen. Also, reading out loud (or under your breath, whatever). Helps you catch dumb typos/word switches, etc.
I don't have this problem when there's someone else junior on the team, right now I'm sending stuff out directly. And my mgr wants everything to be client ready when I send it to him.
Find a peer. Set up peer reviews for each other's work.
These are all helpful, thanks. How do you manage this with time constraints? I have a checklist but never have time to run through the whole thing. I just can't tell if it's me or a general thing analysts struggle with Bc we're not fully trained yet
+1 @D4. Letting things genuinely sit before a final personal review is usually a great idea. Even if it's a short duration. Things are important, but nothing's worth risking an avoidable ding on your rating.