Doing the Right Thing in Financial Services: A Practical Guide

Most people who work in financial services don't set out to cause harm. Poor outcomes for customers, markets or colleagues usually come from a slower, quieter failure: a decision made under pressure, with incomplete information, where the "right" answer wasn't obvious at the time. Doing the right thing isn't about having perfect judgement in the moment — it's about having a method you can fall back on when judgement is hardest to trust.

Why Purpose and Values Matter Day to Day

Every firm has a stated purpose and a set of values printed somewhere in the induction pack. The gap between a values statement and actual behaviour opens up in the small decisions nobody reviews afterwards: whether to flag a pricing error that favours the firm, whether to push a sale that technically meets the rules but doesn't meet the customer's need, whether to stay quiet when a colleague cuts a corner. Purpose only means something if it shows up in these unglamorous moments, not just in the mission statement.

Understanding Stakeholder Impact

A useful habit before any consequential decision is to name who is actually affected — the customer, the firm, the market, colleagues, and sometimes people outside the transaction entirely. Financial decisions rarely affect only the two parties directly involved. A loan approved too generously affects the borrower's future financial health as much as the lender's balance sheet; a trade executed to hit a target can move a market that many other participants rely on. Naming stakeholders explicitly — even briefly — makes it much harder to rationalise a decision that quietly disadvantages one of them.

A Simple Decision Test

When incentives and customer interests conflict, a short decision test helps cut through the noise: would this decision survive being explained, in plain language, to the customer, to a manager, and to a regulator? If the honest answer requires euphemism or omission, that is itself the signal to pause. This isn't a legal test — it's a practical one, designed to be usable in the two minutes before a call or a trade, not just in a training module.

Escalation Without Fear

Ethical behaviour depends on people being willing to ask for a second opinion or flag a concern before a decision is finalised, not just report it afterwards. Escalation works only if the culture around it is genuinely supportive rather than merely tolerant — if raising a hand is treated as diligence rather than disloyalty. Staff should know, concretely, who they escalate to and what happens next, not just that "the door is open."

Documenting Judgement

Where a decision involves genuine judgement rather than a clear rule, a short record of the reasoning — what was considered, what alternatives were rejected and why — protects everyone involved. It creates a defensible trail if the decision is questioned later, and it forces a moment of reflection that catches weak reasoning before it becomes action.

Who This Is Relevant To

This applies across roles: customer-facing staff balancing a sales target against a customer's real needs, operations staff spotting a process shortcut that quietly shifts risk onto someone else, and managers setting the tone for how their teams handle grey areas. Nobody is exempt from the pull of incentives, hierarchy or time pressure.

Building the Habit

None of this works as a one-off training exercise. The decision test, the stakeholder check and the escalation habit only become useful once they are practised on real, low-stakes decisions so they are available under pressure when the stakes are higher. Firms that treat ethics training as a compliance formality rather than a working skill tend to find the gap between values and behaviour widens exactly when it matters most.

Frequently Asked Questions

Is this only relevant to customer-facing roles? No — anyone whose work affects customers, markets or colleagues, including operations, technology and support functions, makes decisions where this applies.

What if my manager is the source of the pressure? Escalation routes exist independently of the direct management line precisely for this reason — most firms provide alternative channels for exactly this scenario.

How is this different from a code of conduct? A code of conduct sets out the rules; this is about the judgement needed when the rules don't give a clear answer.

A Worked Example

Consider a relationship manager who discovers a pricing system error that has been quietly benefiting the firm on a class of accounts for several months. No customer has complained, and the error is unlikely to be noticed externally in the near term. The stakeholder check identifies the affected customers, the firm, and the firm's regulatory standing as parties with a direct interest. The decision test — would this survive being explained plainly to the customer, a manager and a regulator — makes clear that quietly leaving the error in place would not survive that explanation. Escalating immediately, even though it creates short-term cost and admin for the firm, is the action that passes the test.

Key Takeaways

Doing the right thing in financial services is rarely about facing a single dramatic dilemma. It is about consistently applying a simple, repeatable method — naming stakeholders, running the decision test, escalating early, and documenting judgement — to the many smaller decisions that make up most working days. Firms that embed this as a practical skill, rather than a values slogan, see the gap between stated values and actual behaviour close over time.

How This Fits Into a Broader Compliance Programme

Ethical decision-making sits underneath every other compliance control a firm operates — a strong monitoring system still depends on the individual judgement of the people using it. Firms that treat this as foundational training, revisited periodically rather than delivered once at induction, tend to see fewer conduct incidents originate from otherwise well-controlled areas of the business.

Does this apply to decisions made by AI or automated systems? Yes — the stakeholder check and decision test apply just as much to designing and overseeing automated decisions as to human ones.

Explore Learnsignal's wider CPD course library for more on building compliance capability across financial services teams, and see how auditor ethics and liability is approached in a related professional context.