Most finance transformation problems stay abstract for too long.

Workstreams move forward.
Decisions feel “aligned.”
Design gets implemented.

But the system doesn’t behave as expected.

I make problems tangible by taking one granular example and tracing it end to end through the system.

I don’t start with frameworks or requirements.

I start with a concrete scenario.

One business event.
One expected outcome.

Then I trace it through:

  • how it should be treated

  • how the system processes it

  • what actually shows up in reporting

That’s where the issue becomes visible:

  • inconsistent logic

  • unclear ownership

  • or decisions that were never fully defined

Once the logic is clear, the fix is straightforward.

Examples

of where this approach has worked:

  • Cash flow statement design
    → traced individual movements to expose classification gaps

  • Trading partner derivation
    → mapped logic end to end and translated it into a working design

  • Currency translation
    → separated transaction currency and local currency logic to enable consistent reporting views

  • Chart of accounts structure
    → redesigned account logic to align balance sheet and P&L behavior