How to Respond to Feedback in Investment Banking

Banking teams review work closely because small errors can undermine an analysis or reach a client. Comments on a model, presentation, or email are therefore normal quality control—not necessarily a judgment about your potential.

Your first responsibility is to understand the correction. Listen without interrupting, take notes, and avoid explaining every decision. Even when there was a reasonable basis for what you did, leading with a defense can make you appear resistant. A simple acknowledgment keeps the discussion productive.

Some feedback is precise: change a formula, update a source, or align formatting. Other comments, such as “make this page sharper,” require clarification. Ask focused questions that demonstrate judgment rather than transferring the entire problem back to the reviewer.

Confirm the expected output, scope, and timing. If one comment may apply elsewhere, ask whether you should make the change throughout the document. When several revisions arrive at once, repeat the priorities back so you do not spend an hour polishing a low-priority page while a senior banker waits for a critical analysis.

• What specifically needs to change?
• Does the comment apply anywhere else in the model or presentation?
• When is the revised work needed?
• Should you send individual pages for review or complete the full revision first?

Fixing the marked item is only the minimum. Determine the underlying rule and check the entire work product for similar issues. If a reviewer identifies one inconsistent decimal place, inspect every relevant table. If a transaction date is wrong, verify dates across the analysis rather than correcting one cell.

Maintain a personal error log or checklist. Record recurring comments such as inconsistent units, stale market data, unsupported assumptions, broken links, or failure to follow the team’s formatting conventions. Review that list before submitting future work. The goal is not perfection on day one; it is to make each mistake less likely to recur.

For consequential corrections, slow down and recheck the revised output. A rushed fix can create new errors, especially when formulas, links, or presentation layouts change.

You will occasionally receive feedback that seems inconsistent, subjective, or based on incomplete context. Do not argue reflexively. First make sure you understand the requested outcome. Then raise relevant facts calmly, especially if the change could create an analytical error or conflict with another senior banker’s direction.

Frame your concern around the work rather than your pride. You might say, “I can make that change. One consideration is that this would differ from the methodology used on the summary page—would you like me to update both?” Once the decision is made, execute it unless it creates an ethical, legal, or compliance concern. Those issues should be escalated through the appropriate firm channels.

When you return the work, summarize what changed and flag anything still unresolved. Keep the update brief: reviewers need confidence that comments were addressed, not a long account of your effort.

The strongest response to feedback appears in the next assignment. Apply the lesson proactively, use your checklist, and ask for a quick review of your progress when appropriate. If feedback is broad—such as needing stronger attention to detail—request one or two concrete examples and agree on observable improvements. Consistent follow-through builds trust faster than repeated apologies.

1. Acknowledge the feedback.
2. Clarify the scope and deadline.
3. Correct the issue everywhere it appears.
4. Review the revised work for new errors.
5. Confirm completion and apply the lesson next time.

• Listen, take notes, and acknowledge feedback before offering context.
• Fix the underlying pattern across the full work product, not only the marked item.
• Use an error log or checklist to prevent repeated mistakes.
• Disagree calmly, focus on the work, and demonstrate improvement through follow-through.