What your supervisor doesn't see
Under-communicating is the number one mistake new hires make. Here is what your silence looks like from the other side of the table, and the system that fixes it.
New hires assume the supervisor sees everything. They do not. Your supervisor has their own workload, their own manager to keep happy, and very limited visibility into the details of your work. What they have is a meeting at four o’clock where a partner will ask how your workstream is going.
Here is the test, and it is the only one that matters. If your supervisor cannot confidently present what you are doing at any given moment, you have a communication problem. You may be doing excellent work. From where they sit, the two are indistinguishable.
Five principles for communicating upward
1. Share answers, not efforts. Share insights, not data. Your supervisor does not need to know you spent four hours cleaning a dataset. They need to know what the dataset revealed. Lead with the insight and let them ask about the process if they want it.
2. Be to the point. Summarise and highlight the key message. If you can show it visually, show it. A chart with one clear tagline beats a paragraph every time.
3. Communicate solutions, but raise problems you cannot solve. When you surface an issue, bring a proposed next step. “The client data is incomplete; I suggest we request the missing fields by Wednesday and work with a proxy until then” is infinitely more useful than “the data is incomplete.” When you are genuinely stuck, escalate explicitly: “I have problem X. I tried this and that, it did not work. Have you seen this before?” (sidenote: the well used phrase "don't bring me problems, bring me solutions" is utter b******t. If you could solve it, no supervisor would be needed. so solve what you can, and escalate what you cannot. Credit to Ben Horowitz's must-read book 'The Hard Thing about Hard Things')
4. Seek input when you need it. Owning the answer does not mean producing it alone. Frame the ask clearly: “I need your view on X because it affects Y.” A precise ask gets a precise answer in two minutes. A vague one gets a meeting.
5. Communicate early and often, especially when something changes. A quick message saying “heads up, this is taking longer than expected, new ETA is Thursday” prevents surprises and builds trust. It costs thirty seconds. The alternative is your supervisor finding out on Thursday, in front of the partner.
The habit underneath
Estimate how long things will take, and flag early if you will be late. This sounds basic, but it is consistently one of the most valued behaviours supervisors report. It lets them plan, and it lets them manage expectations upward with the partner and the client.
It has a second effect that is less obvious and more useful to you. Your supervisor usually has a good instinct for how long a task should take. If your estimate is very different from theirs, that gap prompts a conversation, and that conversation surfaces a thinking error or an unknown before you spend six hours going the wrong way.
So keep an ordered list of your tasks, written down, with time estimates. Check things off. Re-order it frequently. When your supervisor asks, you should be able to give your key priorities in order, the steps needed to finish each one, and how long you expect them to take.
They may reshuffle it, which is their job. The fact that the list existed does more for their confidence in you than the work itself.
What good rhythm looks like
A workable default for an associate:
• Morning, two lines. What you are working on today and anything that could block you.
• Whenever something changes. New ETA, unexpected finding, dependency that did not arrive. Immediately, not at the check-in.
• End of day, if anything landed. The one insight worth knowing before tomorrow, in a sentence. If nothing landed, send nothing.
• Weekly or bi-weekly check-in. The structured conversation about progress, priorities and your own development.
That is perhaps five minutes of communication a day, and it removes almost every unpleasant surprise a supervisor can have.
The proactive half
Proactivity is the other half, and it is what separates an associate who is easy to manage from one who is genuinely useful.
Get meetings into calendars early. “I need your input today after lunch; do you have 15 minutes?” is a better sentence than waiting for the check-in and losing a day. Identify problems before they escalate and propose solutions. If a deadline is at risk, flag it before it breaks. If the team is missing an analysis, raise it.
And manage the information flow deliberately. Ask what your supervisor needs from you, by when, in what format, and what input they need to make their own decisions. Then plan what to bring to your check-ins to drive those decisions efficiently. Making their life easier is not servility, it is the mechanism by which the whole team moves faster.
Side-effect: When you tell the supervisor if you did something well (good client interaction, cool model), they will see this and often perceive it in a different light. You shape your story significantly. Don't assume, just because you think you did well, that everybody is aware.
START THIS WEEK
1. Write your task list down tonight with a time estimate against every item. Tomorrow, when anyone asks what you are working on, read it out in priority order.
2. Send one heads-up message you would previously have swallowed. A slipping ETA, a dependency at risk, an assumption you are unsure about. Notice how it is received.
3. At your next check-in, ask what format your supervisor prefers for updates and how often. Almost nobody asks, and everybody has a preference.
If your supervisor cannot confidently present what you are doing at any moment, you have a communication problem.