Portfolio

Projects

Multi-site Railcar Operations Automation

Context
A multi-site enterprise application (Hamilton → Montreal, planned expansion) to digitize railcar intake: capture weight & photos, generate tickets, and centralize operational data for operations and logistics teams.

Role & team
Agile Product Owner / Product Manager scope — led discovery, roadmap, and delivery.
Team: Cross-functional (Operations, Logistics, IT, Security); 4 Engineers, 3 QA analysts, 1 Designer.

Problem
Manual railcar processing required operators to transfer data by hand and create tickets manually. This produced delays, data quality issues, and safety risks (manual photo capture in hazardous locations). Operations lacked real-time visibility.

Hypothesis
If we automate weight/photo capture and ticket generation and provide site-configurable deployments, then we will reduce manual work, lower safety risk, and give operations real-time status tracking.

Discovery

Conducted site visits and shadowed operators across shifts.
Interviewed operators, loaders, and site managers to map current workflows and failure modes.
Analyzed historical ticket logs to quantify time spent on manual tasks and error rates.

Solution & Execution:

Implemented automated weight & photo capture with ETL imports and automated RECY ticket generation.
Built map-based UI for railcar visibility and role-based access controls.
Designed site-configurable sensor/camera integrations and offline/ retry logic.
Implemented CI/CD pipeline and phased rollout plan with training and runbooks for each site.

Outcomes:

Saved ~90 minutes per shift previously spent on manual data transfer.
100% elimination of manual ticket creation for RECY tickets.
Reduced safety risk by removing manual photo-capture in hazardous areas.
Improved operational visibility: real-time status for operations managers and loaders.
Improved observability: runtime/connectivity errors logged in Azure for faster support and audits.

Key learnings / next steps

Add product analytics to track throughput and adoption month-over-month.
Test alternate UX for fast identification (A/B test) and extend integration with supplier billing for automated reconciliation.

Finance Process Automation & Claims Workflow

Context
A bilingual (EN/FR) claims platform to centralize and automate claims and AR workflows across AIM Recycling sites in Canada (and support for US instances).

Role & team
Product Owner: led requirements, feature design, and phased deployment.
Team: Cross-functional stakeholders: (Finance, Traders, Operations, IT); 1 Engineers, 1 QA analysts.

Problem
Claims and approvals relied on email/manual coordination and ad-hoc communication tools, causing slow decisions, higher backlog, and reduced collections visibility.

Hypothesis
Introducing role-based workflows, batch approval/rejection, and dashboards will accelerate claim resolution, reduce manual effort, and improve collections follow-up.

Discovery

Mapped existing approval flows and approval pain points with finance and trader interviews.
Measured average resolution time and backlog size to set baselines for improvement.

Solution & Execution:

Delivered bilingual claim workflows with role-based access and batch approval features.
Implemented phased deployments with CAB reviews and stakeholder trainings.
Built dashboards for aging, backlog, and claim status monitoring.

Outcomes:

Faster claim decisions and follow-ups → improved collections efficiency (add % or time saved if available).
Reduced manual effort through batch processing and automated notification flows.
Scalable platform supporting multi-region RECY instances and potential reuse for AP/AR workflows (refunds, credit notes, vendor creation).

Key learnings / next steps

Expand to AP workflows and connect automated reminders to collections KPIs.
Instrument analytics to measure direct impact on collections and cash flow.

B2B Commerce & Field Operations Digitization

Context
A B2B digital platform for catalytic converter transactions: grading, valuation, cart creation, pricing, tolling, and reconciliation. Web + mobile apps support internal account teams and external sellers.

Role & team
Product Owner (end-to-end): defined features and led mobile/web delivery.
Team: Cross-functional stakeholders: (Traders, Operations, IT); 4 Engineers, 2 QA analysts, 2 Designer.

Problem
Field teams used WhatsApp and manual processes for grading/negotiations, causing slow reconciliation, poor audit trails, and limited seller self-service. Mobile users needed to operate in low-connectivity, gloved conditions.

Hypothesis
Mobile grading with integrated messaging and offline capabilities will reduce ad-hoc communications, speed reconciliation, and increase seller-initiated transactions.

Discovery

Collected usability feedback for gloved operations and low-connectivity flows.
Ran 20 field interviews and multiple in-field tests.

Solution & Execution:

Implemented mobile offline mode, cart creation, pricing & crate management, and integrated messaging/notifications.
Designed UI for gloved interactions and quick capture; coordinated RFCs and CAB for backend upgrades (session persistence / Java migration).
Managed sprint planning, backlog grooming, and CAB approvals for usability and security changes.

Outcomes:

Reduced manual ad-hoc communication by ~80% through integrated messaging.
Improved cart reconciliation & payment turnaround by ~60% with on-site grading and validation.
External sellers now initiate ~40% of cart transactions (increased seller engagement).
Improved traceability and auditability across transactions; mobile supports low-connectivity field operations.

Key learnings / next steps

Instrument conversion funnel (seller → cart → payment) and run experiments on pricing logic.
Track LTV of buyers acquired via mobile to quantify ROI of field digitization.

Employee Ticket Management Platforms

Context
An internal platform to digitize ticket requests, approvals, and distribution for employees; replaced legacy email-based processes.

Role & team
Product Owner and Business Analyst: led requirements, UAT, and rollout; created support guides and training materials.
Team: Cross-functional stakeholders: (HR, IT); 1 Engineer, 1 QA analyst.

Problem
Legacy email workflows produced lost requests, slow approvals, and poor auditability.

Solution & Execution:

Built a role-based, secure ticketing application with import templates, validation, and activity logs.
Managed UAT, soft launch access, and organization-wide rollout with training.
Created support documentation and templates for bulk uploads.

Outcomes:

100% elimination of manual email handling for ticket requests and approvals.
~50% faster approval turnaround due to automated workflows and role-based routing.
Improved auditability—every action logged and traceable.
Scalable design to support multiple venues and configurable approver lists.

Key learnings / next steps

Add analytics to measure long-term adoption and identify opportunities to expand to other HR/internal services.