ttTolendi Tastybaydata & ai product manager
back to work

Enterprise finance and reporting platform

A standardized enterprise platform and five-phase rollout that improved workflow conversion, submission speed, and reporting performance.

Center for Strategic Initiatives2023 — 2025Senior Product Manager · scope, roadmap, rollout, experimentation20-person cross-functional team · 12 engineers · 3 design/analysisproduction across 5+ deployments
33%workflow-conversion lift
30%faster submissions50%faster report queries1,250training attendances

The workflow problem

Manual budgeting and approval processes, slow report retrieval, unclear requirements, and inconsistent regional implementations reduced completion and trust.

Bookkeepers, department approvers, directors, and executive stakeholders managing finance and approval workflows.

My leadership scope

  • Defined product scope, technical roadmap, and rollout milestones
  • Led a 20-person cross-functional delivery team
  • Translated executive and operational needs into prioritized specifications
  • Designed A/B-tested workflow changes from product telemetry
  • Ran 25 user-training sessions across five-plus deployments

Instrument before redesigning

decision sequence

Instrument first, then redesign the highest-friction workflow

eventworkflow_started

Establish entry and user context.

eventapproval_viewed

Locate the highest-friction stage.

eventsubmission_completed

Measure conversion and completion time.

eventrepeat_session

Connect rollout changes to adoption.

What the data changed

Telemetry exposed the highest-friction steps. A/B-tested workflow changes, standardized architecture, and a five-phase rollout aligned engineering delivery with executive readiness.

Instrument before redesigning

Track active usage, submissions, drop-off, and repeat behavior before changing flows. Telemetry identified where users actually abandoned approval and reporting workflows.

Alternative considered: Redesign from stakeholder opinion or optimize backend speed alone.

Trade-off: Instrumentation delayed visible UI work but made prioritization defensible.

Standardize the platform

Use a shared architecture and configurable modules across deployments. Standardization reduced delivery risk and made rollout readiness measurable.

Alternative considered: Continue building one-off regional deployments.

Trade-off: Regional teams accepted less customization in exchange for faster, more reliable launches.

The before-and-after

beforeafter
query timebaseline50% faster
submissionbaseline30% faster
33%workflow-conversion lift1,250 training attendances · 5+ deployments

Workflow conversion, submission speed, query performance, and rollout readiness were managed as one product system.

Outcome

Conversion

A/B-tested workflow changes increased conversion by 33%.

Speed

Submission time fell by 30% and report-query performance improved by 50%.

Rollout

The team delivered five-plus deployments and 1,250 training attendances through a three-month, five-phase launch.

measurement notes

Definitions and sources are shown so every result can be examined in an interview.

33% conversion lift

Before/after workflow conversion measured through granular product telemetry.

30% faster submissions

Post-launch pilot comparison of completed submission time.

50% faster queries

Before/after report-retrieval performance after query and reporting improvements.

1,250 training attendances

Attendance across 25 user-training sessions and 5+ deployments.

The product improved when rollout readiness, user behavior, and technical delivery were managed as one system rather than separate workstreams.