Stakeholder and executive leadership
Build cooperation. Make decisions clear. Follow through.
These examples show how I work across teams and with senior leaders to resolve friction, address risk, and support delivery.
Standard BioToolsProcess ownership and cross-functional adoption
Give Finance and IT a shared way to deliver reporting.
IT-controlled reporting limited Finance’s flexibility, while IT needed consistent calculations and governed data.
How I handled it +
My actions
- I initiated discussions to understand the friction and designed shared responsibilities for request intake, data-model design, validation, and reporting.
- Finance defines the requirements and star-schema model. IT reviews, implements, and tests the data, then returns validated tables for the governed semantic layer. I build the Power BI reports and dashboards.
Outcome
Finance and IT adopted the process, combining flexible Finance reporting with agreed responsibilities and IT oversight of common calculation logic.
Read the wider case study ↗Standard BioToolsCross-team and cross-cultural collaboration
Help Finance and Accounting work toward the same outcome.
Friction between Finance in Toronto and Accounting in Singapore made collaboration more difficult.
How I handled it +
My actions
- I initiated conversations to understand the Accounting team’s needs and address their data requirements.
- I brought my VP into the discussion to build understanding across teams and cultural differences.
- I paired the relationship work with automated ERP data handling to support smoother month- and quarter-end processes.
Outcome
Finance and Accounting gained clearer shared reporting requirements and a more cooperative working relationship.
Read the wider case study ↗Munich Re CanadaStakeholder expectations and follow-through
Rebuild trust with a frustrated business partner.
Data-quality problems created additional manual work and recurring complaints from a claims partner.
How I handled it +
My actions
- I listened to the concerns and acknowledged the issues affecting the partner’s work.
- I recommended practical fixes, set realistic timelines, and maintained transparent follow-up.
Outcome
The relationship became a productive partnership, supported by clearer expectations and communication.
Read the wider case study ↗Munich Re CanadaExecutive communication and operational judgment
Escalate a material risk with options and a path forward.
During a pressured data load, I found valid claims records being dropped by the orchestration engine.
How I handled it +
My actions
- I stopped the affected loads and validated with claims specialists that the records were legitimate.
- I independently initiated the investigation and developed solution options, presented the findings and trade-offs to the COO, and led development of the fix.
Outcome
A hotfix was implemented within one week. The issue carried potential multimillion-dollar impact; this is not a claim of measured financial savings.
Read the wider case study ↗