Lessons from a Consulting Panel
I sat in on Deloitte’s “Real Talk” panel at Cornell recently — a Q&A with consultants about life at the firm and their recruiting process. I came away with a notebook full of advice that has little to do with case interviews or “why Deloitte.” It turns out that a room full of people whose job is communicating, scoping work, and managing relationships has a lot to say about how to work well in any field.
Here are the takeaways that stuck.
Make the connection for your audience
The panel’s most-repeated point: recruiters read every word of an application, but they will not do the work of figuring out why your background fits the role — that’s your job. “Tell us why what you’re doing is synonymous with client management” — or, generalized: don’t hand a reader a list of experiences and hope they connect the dots. Say it outright: “My X taught me Y, which transfers to your Z.”
This applies to grad-school applications, grant proposals, job applications, even pitching an idea to a collaborator. Assume your audience is busy and won’t infer; make the bridge explicit.
Have a specific, non-generic “why”
“Why Deloitte?” is really “why this, specifically?” The panelists could tell when an essay was written for any firm, the same way admissions officers can tell “why I want to go to college” from “why Cornell.” The fix is to ground the answer in something concrete and personal — a person you talked to, a specific initiative, a particular problem you want to work on. Generic enthusiasm is detectable and reads as low effort.
Give structured, memorable answers
One panelist always answered “why Deloitte?” with three numbered reasons. She watched her interviewer write “1. culture, 2. …” into a notebook — literally transcribing the structure she wanted him to remember. Structure is a gift to your listener: it makes your answer easy to follow and easy to repeat back. If you want someone to walk out of a room carrying a specific message, hand it to them pre-packaged.
Demeanor and recovery matter as much as content
One panelist made two arithmetic mistakes in a row during an interview and still got the job. The lesson wasn’t that mistakes are free — it’s that your recovery is what people actually evaluate. Staying composed, keeping the logical thread, and not spiraling signals credibility more than never stumbling. In a real team setting the same holds: what matters is how you and your team keep trust when something goes wrong in front of a client (or a committee).
Relationships can be systematized
The panel’s top relationship tip was almost comically mechanical: keep a log. Write down the personal details people mention — a kid’s milestone, an upcoming trip — and reference them the next time you talk. It sounds robotic, but it’s exactly how thoughtful people behave at scale, and it works on advisors, mentors, and collaborators just as well as on clients. The deeper point: the people above you are humans, not pedestals. The panelists’ biggest misconception as students was that senior people would be intimidating; universally, they found the opposite.
Be a good teammate by sharing context
On projects, team members split up and cover different meetings, then reconvene. The high-value move is to pass along what you learned — “heads up, this person likes agendas,” “don’t try to end this meeting early.” No handbook requires it and no one audits it, but it compounds: people choose to work with people who set them up to succeed.
Raise things early
This was the sharpest point of the whole panel. You don’t get in trouble for raising something that turns out to be a non-issue; you get in trouble for not raising something that turns out to be real. The failure mode they see most often is someone silently overcommitting — saying yes to a request that’s out of scope, or hiding a concern until it becomes a crisis. The fix is embarrassingly simple: tell someone. “Hey, this person asked me to do X — should I?” is innocent; staying quiet until it blows up is not. Underneath that is a scope instinct: you can’t say yes to everything, because your time and energy are finite — so flag it when a request goes beyond what you’re actually on the hook for. Or, as one panelist put it, surface the problem and you “make the conflict someone else’s problem, someone who’s paid more to deal with it.”
Manage up when something is unrealistic
The best story of the night was about a “strategy sprint” where a team analyzed a mountain of data overnight and presented it the next morning — only to find real errors the same day. The lesson they drew: when a deadline is unrealistic, say so early, even to a partner. If you can’t say no, at minimum flag it — “draft,” “still validating” — rather than letting flawed work go out under the team’s name. There’s almost always a way to protect integrity without being insubordinate.
Don’t procrastinate — work snowballs
In school you can pull an all-nighter and still turn in the essay. At work, if you get a task Monday that’s due Thursday and decide you have time, Monday’s “free hours” get eaten by things that emerge. The workload isn’t predictable the way a syllabus is, so the habit that transfers is the opposite of the college habit: use slack when you have it, because it won’t be there Thursday.
Communicate your boundaries and keep your rituals
People can’t accommodate what you don’t tell them. “I take a 7 AM workout class, so don’t bother me in the morning — I’ll stay late for your deliverables” is a reasonable request, but only if you actually say it. In a fluid, busy role, anchoring your day with small personal rituals is what keeps the ambiguity from becoming chaos.
Choose environments where collaboration is rewarded
Once you’re in, the panelists said, the competition fades — what’s rewarded is being someone people want on their project. That’s worth probing for when you evaluate labs, teams, or companies: does the place reward collaboration, or rank-and-yank? The panelists’ answer is a decent litmus test for any org you might join.
Find your niche inside a big organization
One panelist loved that a giant firm felt small once she found her “population health” community. The generalized version: in any large institution, find (or build) the smaller group aligned with what you care about. It’s the difference between feeling like a number and feeling like you have people.
The unpolished stuff (workplace street smarts)
Alongside the polished advice, the panelists let slip a handful of grittier, “how it actually works” details. These were the most honest parts of the evening:
- You can quietly drop people you don’t like working with. In a big org, if you don’t click with someone, you never have to talk to them again — the place is huge. It sounds cynical, but it’s freeing: you’re never stuck with anyone.
- Juniors have more access than they realize. Partners clear their calendars for interns and answer cold calls from someone in their first week. There’s a newcomer pass — use it while you have it.
- Use your downtime to stay visible. Consultants call the time between projects “bench time,” and they use it to reconnect and remind people they’re available. Some keep quarterly calendar invites with everyone they enjoy working with. Staying on people’s radar is maintenance work, not luck.
- Internalize feedback after the first correction. Making a mistake once is fair game; making it twice, after someone has already shown you the fix, is not. The distance between “junior” and “trusted” is measured in how fast you stop repeating errors.
The through-line of the whole evening, compressed into a sentence: say explicitly what you want, why you fit, what you need, and what’s going wrong. Consulting turned out to be a surprisingly good lens for that, because it’s a job that is mostly communication and relationship management — but the lessons travel everywhere.