Professional Case Study · June-July 2026
Centralizing a distributed ERP smoke testing and UAT program into one traceable, automation-supported operating system.
During a two-month contract through Actalent, I supported Molex Connected Enterprise Solutions as a Junior Project Manager. My work focused on the execution layer: turning thousands of test steps, dozens of scenarios, and four global teams into a shared workflow that could run continuously across time zones.
Public-Safe Scope
This case study is intentionally limited to my responsibilities, design approach, high-level scale, and selected interface views. The screenshots omit personal data, issue narratives, defect details, configurations, and proprietary business-process documentation.
Problem, Task, Solution
The value of the work came from connecting process design, workbook automation, tester usability, and live program coordination. Each problem had a practical operating task behind it, not just a reporting need.
Problem 01
Problem 02
Problem 03
Problem 04
The System
I designed the workflow around a simple principle: testers should update the work once, and the system should handle consolidation, status logic, reporting, and handoffs. The interface prioritized clear navigation while the automation worked behind the scenes.
Structured test plans, owners, steps, statuses, and issue signals.
Power Query standardized distributed inputs into shared progress views.
Office Scripts and Power Automate refreshed logic and triggered communications.
Dashboards and daily updates surfaced progress, ownership, and blockers.
Interface Design
The visual design gave testers direct routes to their schedule, current task list, issues log, meeting links, learning items, and production environment. Scenario navigation and color-coded task assignment made a large testing program easier to scan and operate under time pressure.
Screenshots are tightly scoped to interface design and workflow structure. No personal data, incident descriptions, defect narratives, or detailed test instructions are shown.
Execution
Aligned scenario data, ownership, and status fields so distributed teams could be compared without losing context.
Created user-centered navigation and responded to tester questions so the system fit the work instead of adding reporting burden.
Coordinated daily progress across global teams and maintained continuity as testing moved between time zones.
Worked through issue status, ownership, fixes, and retesting so active blockers stayed visible until resolution.
Automated refreshes, script execution, and Outlook communications while using Copilot to draft daily status updates from current testing data.
Outcomes
Distributed scenario data became a consolidated program view with visible ownership and status.
Scheduled refreshes, script execution, and Outlook workflows reduced repeated status consolidation.
A shared workflow helped teams continue testing across time zones without rebuilding context.
Clear navigation, current task lists, and tester support improved the quality and timeliness of status information.
What this experience demonstrates
I can enter a time-sensitive enterprise program, understand how people and data move through the process, build a practical technical system, and support adoption across multiple stakeholder groups. The value was not a single dashboard or script; it was the integrated operating workflow.
Explore More
Return to the portfolio for the Boeing 787 scheduling model, ERP/SCM dashboard, optimization solvers, and research work.