Selected work

The engagement

During a long-term engagement with a global enterprise client, I served as Technical Lead for reporting and analytics initiatives across Finance and Order Management. The work called for more than responding to requests for data: each team needed clarity on the decision it was trying to make and where the supporting capability belonged.

Finance: choosing where to reconcile

One Finance question was where to reconcile accounts across primary and secondary ledgers. Working with ERP and Finance teams, I helped guide a shared decision to keep that process in the cloud ERP rather than create complex custom data pipelines. The Finance Technology Director approved the approach, and another team took it forward for implementation.

Order Management: building daily visibility

Order Management faced a different problem: under the client's order-allocation setup, orders could be allocated against inventory that was not yet available. I designed and built a solution that brought together data at multiple levels to show open-order quantities alongside item-level on-hand balances. The dashboards entered production and became part of the team's daily planning. In one initiative, the best choice was to use the system already responsible for the work; in the other, it was to build new visibility the team would use every day.

The challenge

When I stepped into the Reporting Lead role, the workstream was behind and the project record did not provide a reliable view of the work ahead. Items, dates, and design inputs needed to be brought into one accountable plan.

My role and decisions

I led an onshore analyst and directed an offshore development group through its manager. I consolidated deliverables and owners, reset the timeline, and introduced twice-daily calls with the offshore team to surface progress and dependencies. I also decided that work would not begin until requirements were documented and the client had signed off. I managed offshore staffing and workload throughout the recovery.

What was delivered

Over roughly three months, the team launched the agreed suite of 30 reports and dashboards in the go-live window our leadership needed to meet. The new reporting was available to support the client's financial operations. I rolled off soon after launch, so this account ends at delivery rather than making claims about longer-term use.

What it illustrates

When a delivery plan cannot be trusted, restoring ownership and decision rules is part of the technical work.

The challenge

During a move from internally built incentive-compensation systems to a cloud platform, risk and compliance teams needed to examine employee payment calculations and identify transactions meeting defined exception criteria.

My role and decisions

As Reporting Lead, I led the governance reporting effort with leads from other program workstreams. I worked regularly with a senior compliance and risk leader on requirements, progress, constraints, and approvals. The platform's standard email delivery did not fit the client's communication protocols, so I brought in the workflow lead to design a custom route for the data and notifications.

What was delivered

The team built reports and dashboards exposing calculation detail and defined exceptions, along with automated notifications to the stakeholders responsible for follow-up. The client approved the capability, and I observed the custom workflow's notifications working. These components supported the client's audit and governance activities.

What it illustrates

Useful governance requires more than visibility: information must reach the people who can investigate and act within the organization's operating rules.

The need and what I built

I wanted to make order tracking easier for my wife's personal shopping business. Using ChatGPT, Claude, and Gemini as tools in the process, I designed, built, tested, and put an order management app into production. She now uses it to operate her business.

What it illustrates

The project gave me a chance to put my interest in AI and practical technology to work outside a client setting: start with a real need, build something usable, and keep responsibility for how it works after launch.