Challenging Decisions with Constructive Dissent

Firms often say they want staff who will challenge decisions, but the skill of doing so constructively — in a way that actually gets heard rather than dismissed or resented — is rarely taught directly. Most people default to either staying silent or raising a challenge in a way that triggers defensiveness rather than genuine reconsideration.

Knowing When to Challenge

Not every disagreement needs to become a formal challenge. The threshold is usually whether the decision carries meaningful risk to customers, the firm or compliance obligations — a stylistic preference doesn't need the same treatment as a decision that appears to breach a control.

Building the Evidence First

A challenge grounded in specific evidence — a data point, a precedent, a documented rule — lands very differently from one grounded only in a feeling that something is wrong. Taking a few minutes to gather the specific basis for a concern before raising it dramatically increases the chance it will be taken seriously.

Choosing Language That Invites Engagement

Framing a challenge as a question rather than an accusation — "can you help me understand how this fits with X" rather than "this breaches X" — often gets a more open response, without softening the substance of the concern being raised.

Escalating When Necessary

If a challenge raised directly doesn't resolve a genuine concern, escalating further isn't a failure of the first conversation — it's the correct next step for a concern that hasn't been adequately addressed. Knowing the escalation path in advance removes hesitation in the moment.

Documenting the Resolution

Whatever the outcome of a challenge, a brief record of what was raised and how it was resolved protects everyone involved, particularly the person who raised it, if the decision is questioned again later.

Staying Engaged After a Challenge Isn't Accepted

Not every challenge changes the outcome. Remaining engaged and professional even when a concern isn't acted on — while still preserving the record that it was raised — keeps the relationship and the culture intact for the next time a challenge is needed.

Frequently Asked Questions

What if raising a challenge damages a working relationship? A well-evidenced, respectfully framed challenge rarely causes lasting damage; how the recipient responds to legitimate challenge is itself a signal worth noting.

Should junior staff challenge senior decisions? Yes, when the substance warrants it — seniority affects tone and channel, not whether a legitimate concern should be raised at all.

What if I'm consistently the only one raising challenges? That pattern is worth reflecting on and discussing with a manager or mentor — it may indicate either an unusually sharp eye for risk or a communication style worth adjusting.

Related reading: Learnsignal's CPD catalogue and the course on auditor ethics and liability.

A Worked Example

An analyst disagrees with a senior colleague's risk rating on a transaction, based on a specific data point the senior colleague appears to have overlooked. Rather than saying "I think you're wrong," the analyst asks, "can you help me understand how this rating accounts for X" — raising the same substantive concern in a way that invites explanation rather than defensiveness. The senior colleague reviews the point, updates the rating, and the working relationship is unaffected by the exchange.

Key Takeaways

Constructive dissent is a learnable skill built on evidence, timing and framing, not a personality trait some people simply have and others don't. Escalating a legitimate concern that isn't resolved through direct challenge is a normal and expected next step, not a breakdown of the original conversation, and documenting the outcome protects everyone involved regardless of the final decision.

How This Fits Into a Broader Compliance Programme

A culture that supports constructive dissent is one of the most consistently cited factors in firms that catch problems early, rather than after external discovery. Training staff in the specific skill of raising a challenge well is a practical, teachable complement to the broader cultural commitment to encouraging it.

Does written challenge work as well as verbal challenge? Often better — a written note allows the recipient time to consider it fully and creates a natural record of the exchange.

Building This Into Team Practice

Teams that handle constructive dissent well typically share a norm that challenge is expected, not merely tolerated — new joiners are often told explicitly, early on, that raising a well-reasoned concern is part of doing the job properly, not a deviation from it. This framing, repeated consistently by managers rather than left as an unstated cultural assumption, meaningfully lowers the perceived risk of speaking up for people newer to a team or more junior in seniority.

Some firms formalise this further with a documented "challenge log" for significant decisions, capturing dissenting views even where the final decision goes the other way — this creates a durable record that a concern was properly considered, which matters considerably if the decision is scrutinised later.