Case Study
A product-led operational transformation that replaced fragmented spreadsheets and manual handoffs with a centralized internal system for loan, inventory, and service operations.
HeyEV had a distributed operational stack of Google Forms, spreadsheets, and manual updates that made loan administration, inventory tracking, and service coordination hard to scale. The goal was to translate those workflows into a practical internal system and deliver an MVP that teams could use immediately.
Work moved through disconnected tools and manual handoffs. Operations teams spent more time reconciling data than using it, and service leaders lacked a consistent picture of what was happening on the ground.
The project began with deep discovery across operations, servicing, inventory, and finance teams to capture how work actually flowed and where decisions stalled.
Workshops and shadowing sessions surfaced high-priority friction points, aligned stakeholders on scope, and established the smallest useful system for the first rollout.
Operational Scale
Operational Centers
Active Users
Monthly Collection Transactions
Monthly Service Tickets
Operational Google Sheets Replaced
Assets Managed Monthly
Before vs After
Product development journey
Capture operational needs, clarify ownership, and identify the most urgent workflow gaps.
Document current processes and surface the handoff points that caused the most friction.
Translate workflows into structured states, validation checks, and coordinated operational paths.
Iterate on a usable interface that reflects actual operational work rather than abstract features.
Validate constraints, confirm scope, and align the system plan with the delivery strategy.
Build the MVP with a focus on the core workflow, data integrity, and operational handoffs.
Exercise the workflow with real data, capture issues, and ensure the system mirrored actual team behavior.
Validate the new process with frontline users and adjust the release based on operational feedback.
Deploy the first version to operational teams while monitoring adoption and early issues.
Refine the system with regular feedback loops and expand the solution to adjacent processes.
Product Artifacts
These artifacts capture the evidence, decisions, and alignment that drove the system from discovery to implementation.
Mapped existing operational workflows across inventory, loan and service operations to identify bottlenecks, handoff failures and process inefficiencies.
Defined operational states, transitions, ownership rules and validation checkpoints before development.
Translated workflows into interface concepts and reviewed requirements with stakeholders before engineering implementation.
Conducted requirement walkthroughs and KT sessions to align implementation with business expectations and technical feasibility.
Tracked defects, validated workflows and supported user acceptance testing before production rollout.
Key Outcomes
Inventory processing time reduced through clearer workflow states and validation checks.
A centralized internal system reduced duplicate spreadsheets and created a single source of truth for operations.
Defined clear ownership for each workflow state so teams could move work forward with accountability.
Structured workflow stages improved handoffs and helped the team manage work consistently.
Operational reporting became more reliable, making it easier to spot bottlenecks and service issues.
What This Project Taught Me
Stakeholder alignment matters more than feature quantity.
Operational adoption is as important as technical implementation.
Shipping a focused MVP creates momentum faster than pursuing a perfect system.
Workflow clarity reduces downstream complexity.
Iterative feedback improves product quality significantly.
Role & Responsibilities
Workflow transformation
Move through the operational story one stage at a time, from the pre-system workflow to the core problems and finally the centralized solution.
Operational friction
Duplicate tracking, delayed handoffs, and fragmented reporting slowed the business and masked the real workload.
Manual updates caused inconsistent status and accountability.
Service teams could not easily prioritize tasks or queue work.
Stakeholders lacked a single operational view of blockers.
The approach was rooted in workflow mapping and systems design. Rather than chase an ideal system, the goal was to identify bottlenecks, clarify handoffs, and define the smallest useful version of a centralized operational tool.
Workflow output
Flow diagrams, step-by-step process maps, and clearly defined operational states shaped a system that could support loan, inventory, and servicing teams consistently.
Development collaboration centered on feasibility checks, implementation constraints, and knowledge transfer. Regular KT sessions kept the team aligned and helped shape a reliable scope for the first release.
Engineering alignment
Shared wireframes, review sessions, and developer walkthroughs ensured the MVP matched both user workflows and technical delivery cadence.
The launch was intentionally phased: validate the core workflow, capture user feedback early, and iterate before expanding to adjacent processes. This kept the first release focused and operationally useful.
Phased delivery
Initial focus areas included loan status tracking, inventory visibility, and service task coordination with clear handoff points.
Testing was integrated into the rollout plan. User acceptance testing, bug reporting, and live feedback sessions helped refine flows before wider adoption.
Validation process
Validation included operational walkthroughs, issue tracking, and iterative updates based on frontline user feedback.
Key learnings
Start with the actual workflow, not the UI. The system works when the process is clear.
Regular alignment with engineering keeps scope realistic and release-ready.
Phased rollout and UAT make operational systems easier to adopt across teams.