Speaking Up: When and How to Raise Concerns
You'll learn: How to recognize when concerns require escalation and navigate the appropriate channels to raise technical, ethical, or quality issues effectively.
When to Speak Up
Not every disagreement requires escalation, but certain situations demand it. You should raise concerns when:
- Safety or security risks threaten users or systems
- Ethical violations conflict with professional codes or harm public welfare
- Quality compromises will create significant technical debt or future harm
- Process failures repeatedly prevent teams from meeting standards
- Legal or regulatory issues expose the organization to liability
The key question: "If this goes wrong, could I justify staying silent?" If the answer is no, you have a professional obligation to act.
How to Escalate Effectively
Start local and move up gradually. Like debugging, try the simplest solution first:
- Direct conversation with the person or team involved (often resolves 80% of issues)
- Your manager for team-level or project concerns
- Skip-level or cross-functional leads for broader organizational issues
- Ethics committees, legal, or compliance for serious violations
- External reporting (whistleblowing) only as a last resort when internal channels fail
Document everything: Keep clear records of what you observed, when you raised it, and the responses received. This protects both you and the organization.
Be specific and solution-oriented: Instead of "This code is terrible," say "The authentication module lacks rate limiting, exposing users to credential stuffing attacks. I recommend implementing exponential backoff."
Separate facts from opinions: Lead with objective observations, then share your professional judgment.
Protecting Yourself
Speaking up can feel risky, but staying silent when harm is foreseeable violates your professional duty. Know your organization's whistleblower protections and document your concerns in writing if verbal discussions fail.
Key Takeaway: Escalate concerns when silence could cause harm; start with direct conversation, document thoroughly, and use clear, solution-focused language to navigate up the chain responsibly.