Diversity in Finance Teams Is Not About Being Nice. It Is About Seeing Risk Earlier.

by Henny Irniawan | Aug 14, 2026

Table of Contents

Diversity is not automatically a performance advantage

Diversity is often discussed as if its benefits were automatic. Put different people in one team, and better ideas will appear. Bring different backgrounds together, and innovation will happen. Increase representation, and performance will improve.

Sometimes that is true.

But in finance, I would be careful with any statement that sounds too easy. Diversity can create better performance. It can also create confusion if the operating system is weak. A finance team may include people from different countries, cultures, industries, functions, seniority levels, and professional backgrounds. That can be a strength because different people notice different things.

  • A controller may see compliance risk.
  • An FP&A manager may see forecast risk.
  • A treasury person may see liquidity risk.
  • A tax person may see exposure that others miss.
  • A shared-services analyst may see process failure before management sees the P&L effect.
  • A local finance manager may understand regulatory or customer realities that group finance cannot see from headquarters

That is the real value of diversity. It expands what the finance function can see. But visibility alone is not enough. The team still needs discipline. Because if everyone sees different risks but the organization has no common language, no clear standards, no escalation rhythm, and no decision ownership, then diversity becomes noise. The finance leader’s job is to turn difference into decision quality. This article proposes a practical framework for doing that.

The finance Challenge: diverse teams fail when the rules are invisible

Many diverse teams do not struggle because people are different. They struggle because the rules are unclear. This is especially true in finance, where much of the work depends on precision:

  • What does “done” mean for a reconciliation?
  • What evidence is enough for a journal?
  • When must an issue be escalated?
  • Who can approve an exception?
  • What is considered material?
  • Which number is the official source?
  • What is local flexibility, and what is group policy?
  • What is a timing issue, and what is a real risk?
  • What can be discussed informally, and what must be documented?

If these rules are not explicit, people will fill the gaps based on their prior experience. That is where misunderstanding starts.

  • One person thinks an email approval is sufficient.
  • Another expects workflow approval. One person believes a variance is too small to escalate.
  • Another considers it material because of pattern or risk. One country team waits for formal instruction.
  • Another escalates immediately.
  • One manager sees challenge as professional discipline.
  • Another experiences it as personal confrontation.

None of this means people are incapable. It means the operating model is unclear. In finance, inclusion does not mean lowering standards. It means making the standards visible enough that different people can succeed against the same expectations.

A practical framework: The Shared Standards Diversity Model

The Shared Standards Diversity Model has six controls.

  1. Define the non-negotiables.
  2. Separate style differences from control issues.
  3. Build one finance language.
  4. Design participation, not just attendance.
  5. Pair psychological safety with ownership.
  6. Convert different perspectives into earlier risk detection.

This framework is designed for finance leaders managing teams across countries, entities, systems, cultures, functions, and business units. It is especially relevant in multi-entity, multi-currency, transformation, shared-services, ERP migration, and group-reporting environments where finance must balance local reality with group discipline.

1 Define the non-negotiables

What must be the same for everyone?

A diverse finance team needs freedom in how people think, communicate, and contribute. But it also needs consistency in how finance work is performed. The leader must define the non-negotiables. In finance, these usually include:

AreaNon-negotiable standard
ReconciliationsMust tie to source, include explanation, owner, and aging of reconciling items
JournalsMust have support, approval, rationale, and correct period cut-off
ReportingMust use agreed chart of accounts, mapping, and reporting definitions
ForecastingMust separate fact, assumption, and management overlay
Variance analysisMust identify driver, not only movement
EscalationMust follow agreed thresholds and deadlines
ApprovalsMust follow delegation of authority
EvidenceMust be retained and reviewable
ComplianceMust follow IFRS, local statutory rules, tax requirements, and group policy
ControlsMust be performed, evidenced, reviewed, and remediated

This is where finance leaders must be very clear. People can have different styles. They cannot have different control standards. A finance team should never depend on hidden rules that only experienced insiders understand.

Hidden rules create uneven performance.

Visible rules create fairness.

That is why standards are not the enemy of diversity. They are what allow diversity to work.

2 Separate style differences from control issues

Is this a communication preference or a finance risk?

This is one of the most important leadership disciplines in a diverse team. Not every difference is a problem.

  • Some people are direct.
  • Some are careful.
  • Some speak quickly.
  • Some think before speaking.
  • Some challenge in meetings.
  • Some challenge afterward with a detailed email.
  • Some need context first.
  • Some go directly to the issue.
  • Some are comfortable with debate.
  • Some interpret debate as conflict until trust is built.

These are style differences. A good leader should not overcorrect them. If everyone is forced to communicate the same way, the team may become orderly but less intelligent. Control issues are different.

  • Unsupported journals are not a style difference.
  • Late reconciliations are not a style difference.
  • Unapproved discounts are not a style difference.
  • Missing evidence is not a style difference.
  • Delayed escalation is not a style difference.
  • Manual overrides without review are not a style difference.
  • Changing forecast assumptions without documentation is not a style difference.

Those are finance risks.

The leader’s job is to protect people from unnecessary judgment while protecting the business from unacceptable risk. A useful leadership rule is:

Respect the person. Adapt to the style. Enforce the standard.

That sentence sounds simple, but it prevents many leadership mistakes. Without respect, standards become fear. Without standards, respect becomes ambiguity. Finance needs both.

3 Build one finance language

Do we mean the same thing when we use the same words?

Diverse finance teams often use the same words but mean different things. This happens across countries, functions, systems, and seniority levels. For example:

WordPossible interpretations
ApprovedBudget approved, PO approved, contract approved, verbally approved, or system-approved
AccrualConfirmed obligation, estimate, placeholder, late invoice, or “month-end adjustment”
MaterialLarge amount, sensitive account, recurring issue, audit risk, or management attention item
ForecastSystem forecast, business owner forecast, finance-adjusted forecast, or management target
Cash issueCollection delay, liquidity constraint, dispute, banking restriction, or credit-risk concern
VarianceAccounting movement, operational driver, timing difference, or performance gap
RiskAccounting, tax, legal, operational, liquidity, reputation, or control risk

If these terms are not clarified, meetings become long and strangely unproductive. People think they agree when they do not. Or they think they disagree when they are simply using different definitions. The finance leader must create a shared vocabulary. A simple finance language can be built around eight questions:

Common finance questionPurpose
Does the number tie?Establishes reliability
What changed?Identifies movement
Why did it change?Identifies driver
Is it controllable?Clarifies ownership
Is it recurring?Improves forecast quality
Does it affect cash?Connects P&L to liquidity
What risk does it create?Supports governance
What action is required?Converts analysis into decision

These questions help different people work through the same logic. They also make finance more useful to non-finance leaders.

4 Design participation, not just attendance

Are we hearing the right signals from the right people?

A diverse team does not automatically produce diverse input. If meetings are poorly designed, the loudest voice dominates. The most senior person frames the conclusion. The quiet person with the most relevant signal may stay silent.

This is not just a cultural issue. It is a finance risk.

In finance, important information may sit with the person closest to the process:

  • the analyst who sees recurring invoice mismatches;
  • the credit controller who knows the customer always pays late after disputes;
  • the local finance manager who understands a regulatory delay;
  • the ERP specialist who knows the report mapping is wrong;
  • the operations finance person who sees cost behavior before group FP&A does;
  • the tax person who sees an exposure hidden inside a commercial structure.

If leadership only listens to volume and hierarchy, these signals arrive too late. The leader must design participation deliberately. Practical methods include:

  • send materials early enough for review;
  • clarify the decision required before the meeting;
  • ask by responsibility, not by personality;
  • invite challenge before the conclusion is finalized;
  • document open items visibly;
  • assign owners before closing the meeting;
  • follow up on quiet but relevant risk signals.

Instead of asking, “Any comments?” the finance leader can ask:

  • “Credit control, what are you seeing in aging?”
  • “Operations finance, is this timing or structural cost?”
  • “Reporting, any classification issue?”
  • “Tax, any exposure if we treat it this way?”
  • “FP&A, which assumption changes the forecast?”
  • “Local finance, is there a regulatory or customer context we are missing?”

That is not politeness. That is better risk sensing.

5 Pair psychological safety with ownership

Can people raise bad news early, and will action follow?

Psychological safety is important, but in finance it is sometimes misunderstood. It does not mean everyone is comfortable all the time. It does not mean weak performance is ignored. It does not mean issues are discussed endlessly without consequence. In finance, psychological safety means people can raise problems early without being embarrassed, punished, or politically exposed.

But once the issue is raised, accountability must begin. The balance is:

Safe to speak. Accountable to act.

If a team has accountability without safety, people hide bad news. If a team has safety without accountability, people keep discussing the same issue. A strong finance leader builds both. Examples:

SituationPoor leadership responseBetter leadership response
Analyst identifies reconciliation issue late“Why did you make this mistake?”“Thank you for escalating. Now let’s identify cause, owner, and deadline.”
Local team flags regulatory uncertainty“Head office needs the report anyway.”“Document the uncertainty, quantify exposure, and define what can be reported now.”
Business owner misses forecast“Your forecast is always wrong.”“Which assumption failed, what evidence changed, and how do we reset the driver?”
Control exception repeats“Please be careful next time.”“This is recurring. We need process redesign, not reminder emails.”

The point is not to be soft. The point is to make truth travel faster. Bad news reported early is a management issue. Bad news hidden until close is a governance issue.

6 Convert different perspectives into earlier risk detection

What can this team see that a uniform team would miss?

The best finance teams are diverse not only demographically, but also professionally. They contain different risk lenses.

Finance lensRisk detected earlier
ControllershipAccounting misstatement, cut-off issue, unsupported balance
FP&AForecast bias, driver weakness, margin trend
TreasuryLiquidity pressure, FX exposure, funding constraint
TaxCompliance exposure, uncertain tax position, structuring risk
Credit controlCustomer stress, collection delay, dispute pattern
Operations financeCost leakage, utilization issue, process inefficiency
Internal controlApproval breach, segregation weakness, evidence gap
ERP / systemsMapping error, workflow failure, automation risk
Local financeRegulatory, cultural, customer, or statutory issue

The CFO’s role is to integrate these lenses into one view of business reality.

  • If controllership dominates, finance may be accurate but slow.
  • If FP&A dominates, finance may be forward-looking but under-controlled.
  • If commercial finance dominates, finance may be business-friendly but too tolerant of risk.
  • If transformation dominates, finance may automate processes that should first be redesigned.

A mature finance leader does not let one lens become the whole truth.

The value comes from integration.

Practical tool: Finance Team Shared Standards Checklist

Finance leaders can use this checklist when leading diverse teams across entities, functions, countries, or transformation projects.

QuestionYes / No
Are finance deadlines clearly defined and visible?
Are reconciliation standards documented?
Are journal support requirements clear?
Are approval limits and delegation rules understood?
Are escalation thresholds documented?
Are key finance terms defined consistently?
Are reporting sources agreed and controlled?
Are local exceptions documented and approved?
Are meetings designed to hear from relevant process owners?
Are quiet risk signals actively invited?
Are issues closed with owner, deadline, and verification method?
Are recurring issues treated as process problems, not people problems?
Are cultural or communication differences respected without weakening standards?
Are control issues clearly separated from style differences?

If many answers are “No,” the team may still be diverse, but it is not yet operating as a disciplined finance system.

Practical tool: Style Difference or Control Issue?

This is a simple decision aid for managers.

SituationStyle difference?Control issue?Leadership response
Person prefers written follow-up before speakingYesNoAdapt communication channel
Person challenges directly in meetingYesNo, unless disrespectfulSet meeting norms
Journal posted without supportNoYesCorrect, document, and review control
Local team uses different aging definitionNoYesAlign definition and restate if needed
Analyst needs more context before analysisYesNoImprove briefing
Forecast assumption changed without evidenceNoYesRequire support and owner sign-off
Late escalation due to fear of blamePartlyYesFix culture and escalation rule
Reconciliation difference repeats monthlyNoYesRedesign process and assign owner

This tool is useful because it prevents leaders from over-personalizing process problems. Sometimes the problem is not attitude. Sometimes the process is unclear. But once the standard is clear, ignoring it becomes a performance issue.

Implications for the finance leader

Managing diversity in finance requires more than empathy. It requires system design. The finance leader must create:

  • clear standards;
  • shared definitions;
  • consistent escalation;
  • visible ownership;
  • reviewable evidence;
  • respectful challenge;
  • local context with group discipline;
  • psychological safety with accountability.

That is the operating model. Without it, diversity may become polite confusion. With it, diversity becomes a performance advantage. This is especially important in finance transformation. ERP migrations, workflow automation, process redesign, and shared-services models often fail not because the technical design is poor, but because different teams interpret the process differently. The leader must therefore manage both the human system and the control system. That is not HR work alone. That is finance leadership.

Conclusion: diversity works when the operating system is clear

Diversity in finance is not about being nice. It is about building a team that sees more risks, understands more context, challenges weak assumptions earlier, and makes better decisions. But different perspectives only create value when they operate inside shared standards. The finance leader must therefore protect both:

room for different people to contribute; and

discipline for the finance function to remain reliable.

That is the balance. Respect without standards becomes ambiguity. Standards without respect become fear. Finance needs neither. Finance needs clear numbers, clear rules, clear escalation, and clear ownership, delivered by people who are trusted enough to speak and disciplined enough to act. That is how diverse finance teams become stronger. Not because everyone thinks the same. Because they do not and the leader knows how to turn that into earlier truth, better control, and stronger decisions.

References

HennyIrniawan.com — Homepage

HennyIrniawan.com — Meridian Container Lines Case Study

IFRS — IAS 1 Presentation of Financial Statements

COSO — Internal Control Integrated Framework

OECD — Diversity and Inclusion

International Labour Organization — Diversity and Inclusion

Learn more on this topic

Related Blog Posts

No Results Found

The page you requested could not be found. Try refining your search, or use the navigation above to locate the post.

Join in the conversation

Leave a Comment

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Newsletter

Join to get Notified!