Being right isn’t enough; you need to be heard.

Once you’re in the system and thinking deeply, you’ll start to notice inefficiencies and gaps. You might see decisions being made that feel wrong. But instead of putting your point across bluntly, it’s important to raise it thoughtfully.

What I’ve learned over the last decade is that tone often matters more than the content, at least at first. Challenge decisions, yes, but do it with kindness and clarity.

Don’t assume others missed something; assume they had different inputs. Frame your suggestions as additions, not corrections. It changes how they’re received.

When offering feedback or questioning a choice, be mild in tone but sharp in your reasoning. That sharpness must come from preparation; your suggestions should rest on data, not vibes. Here’s what “doing your homework” looks like:

• understand the context and constraints
• explore alternatives and their trade-offs
• anticipate counter-arguments and prepare responses
• cite metrics, issues, or past incidents
• keep it brief but loaded with substance
• state assumptions and ask clarifying questions
• tie your suggestion back to team or product goals

This detailing builds trust. Over time, your feedback won’t just be heard, it’ll be sought. You’ll be known as someone who elevates discussions, not derails them.

The goal isn’t to “win” arguments; it’s to move the team forward, together.