Executive Summary
The Problem
Workers sat through hour-long generic orientation sessions with illegible paper forms while project teams wasted 20 minutes per session supervising the process. When emergencies happened, finding worker contact information meant frantically flipping through binders of handwritten forms — if the information was even legible. Safety managers spent 30 minutes per site per month manually counting paper forms for compliance reports. The system was broken, but nobody had a better solution.
The Solution
Built a digital worker orientation platform that started as a simple Google Forms MVP, survived a catastrophic platform failure affecting 200–1,000 workers, and evolved into a JotForm-based system with 15 trade-specific microlearning video tracks, QR code access, and automated reporting. Personally configured all workflows, conditional logic, video integrations, and data pipelines.
The Impact (4 Years of Operation, 52,000+ Workers Processed)
Project team time + automation + worker efficiency
(1 hour → 40 minutes)
(20 min → 1 min per session)
(Manual → Automated)
(Hours → Minutes, used 3-5 times in real incidents)
Across 60+ construction sites
Looking Back — The Discovery: At the time, I thought I was just solving a safety problem. I was trying to make orientation more efficient, worker information more accessible, and compliance reporting less painful. I didn't have language for what I was doing.
Looking back now, I can see I was applying MVP methodology, platform evaluation, user-centered design, crisis management, and iterative development. I was doing product management — I just didn't know it had a name yet.
Part 1: The Paper Chaos Nobody Questioned
The Morning Bottleneck
Picture this: 6–10 construction workers filing into a trailer conference room at 7 AM. They're antsy to get to work because they're paid by the hour and sitting in orientation means they're not making money. Someone fumbles with a USB stick trying to get the orientation video to play on the TV. Or worse, they're trying to pull up YouTube on their phone to cast to the screen.
The video finally loads. It's 45 minutes long, generic, covering every hazard on every type of construction site. The concrete crew watches a section on steel erection that doesn't apply to them. The cleaning crew sits through fall protection details they'll never use. Everyone knows this is a waste of time.
Then comes the paper form. A two-page document with tiny print asking for:
- Worker name, address, phone number
- Emergency contact name, relationship, phone number
- Acknowledgment of site rules, PPE requirements, hazard awareness
- Signature confirming they watched the video and understood the content
Some workers struggle with the language. Some can't write legibly. Some don't know how to spell their street address. The project team member running the orientation ends up filling out half the forms themselves, asking questions, spelling things out, pointing to where signatures go.
The whole process takes about an hour. Then the workers finally get their orientation sticker and head out to the jobsite.
This happened every single day, on every single site, for every single new worker.
We were processing 10,000–15,000 workers per year this way.
The Emergency Nobody Wanted to Think About
But the real nightmare scenario wasn't the wasted time. It was the emergency contact problem.
When a worker gets seriously injured on a construction site, you need to notify their family. Fast. You need a name, a phone number, and ideally some context about the relationship.
With the paper system, this meant:
- Locating the worker's orientation form from a binder (which binder? which year?)
- Deciphering handwriting that might be illegible, in a language you don't speak
- Hoping the phone number was written correctly
- Hoping the relationship information made sense
- Hoping there actually WAS emergency contact information filled out
I've seen this happen. I've watched safety managers flip through binders frantically while an ambulance is on its way, trying to find contact information. It's a situation where minutes matter.
And the compliance nightmare was just background noise on top of it all. At the end of every month, someone had to hand-count orientation forms from 5–10 sites to create a compliance report. Flipping through binders. Recording numbers. Hoping the math was right.
30 minutes per site per month. Gone. Just... gone.
This was the status quo. Inefficient. Dangerous in emergencies. Tedious to track. But it was what we had.
The Realization: The traditional safety approach here was to add MORE process. More training on "fill out forms legibly." Stricter enforcement on "complete all fields." Better filing systems. But nobody was asking the real question: Why are we collecting this in a way that's hard to use, hard to read, hard to find, and hard to report on?
Why This Project Matters for My Career Transition
This orientation platform was the first project where I was doing product management without knowing it. I:
- Identified a real user problem — not compliance, but operational efficiency and safety
- Built an MVP — started with Google Forms, tested with real users, learned what worked
- Iterated based on feedback — moved to JotForm when Google Forms failed, added video tracks, built QR code access
- Measured impact — tracked adoption, worker time, project team efficiency, compliance reporting
- Scaled strategically — grew from 1 site to 60+ sites without losing the core value
- Managed through crisis — when the platform failed catastrophically, I stabilized it and built a better version
- Proved business value — $171K annual ROI is not a compliance metric, it's a business metric
This is product management. I just didn't call it that in 2020.
The Awakening: Years later, after the hot work permit system, I looked back at the orientation platform and realized: I've been doing this the whole time. This was my first product launch. This was where I discovered I love solving problems by building better systems, not by enforcing harder.
What This Case Study Demonstrates
- Authentic discovery story — I didn't decide to become a PM and then look for projects. I solved a problem with product thinking and later realized that's what I was doing
- Product management fundamentals — MVP, iteration, user-centered design, metrics-driven decisions, crisis management, enterprise scaling
- Construction domain expertise — Understanding jobsite constraints, worker diversity, field conditions, compliance reality
- Impact at scale — 52,000+ workers processed, 4 years of operation, $171K annual value, zero paper holdouts
- Building products, not processes — This wasn't about adding compliance burden. It was about making the right thing easier than the wrong thing
Most importantly: This case study shows someone who discovered their calling by solving real problems in a real business context, not someone trying to jump into tech because it's trendy.