Project case study
Operator Exam Platform
Certification and examination system
Certification and examination system replacing a legacy Access application, covering employee records, certifications, exam building, assignments, scoring, historical migration, and administration.
- Certification
- Exams
- Legacy replacement
Principles demonstrated
- Documentation is part of the product
- Build systems, not fixes
- Data drives decisions
Executive summary
The Operator Exam Platform is a certification and examination system designed to replace a legacy Access application.
It includes employee records, certifications, exam construction, assignments, scoring, historical migration, and administrative workflows.
Trigger
The Access application became a maintenance and risk liability as records, scoring rules, and administrative needs grew.
Problem
Legacy exam tools struggle with durability, multi-user administration, and safe historical continuity when certification records matter long term.
Who was affected
- Employees taking exams or maintaining certifications
- Administrators building and assigning exams
- Leaders needing certification visibility and history
Why the previous process failed
Access systems and informal processes do not scale concurrent administration, reliable scoring workflows, or confident migration of institutional history.
My role
Defined product requirements and solution approach for replacing the legacy examination and certification process.
Product decisions
- Treat historical migration as a first-class delivery concern
- Design administrative workflows as core product surfaces
- Keep scoring and assignment rules formal and reviewable
Build-order rationale
Protect historical data and establish employee/certification records before layering exam-building complexity.
Architecture
Core capabilities
- Employee records
- Certification tracking
- Exam building
- Assignments
- Scoring
- Historical data migration
- Administrative workflows
Technical stack
Constraints and tradeoffs
- Must replace a legacy Access application
- Must support historical data migration
- Must support administrative exam and certification workflows
Challenges
Business impact
Concrete project facts
Lessons learned
Certification systems must protect historical truth. Migration is product work, not a cleanup task after launch.
Current status
Future roadmap
Screenshots and artifacts
Named media slots are ready for production assets. Placeholder frames stay intentional until real screenshots are supplied.
Hero view
Screenshot slot
Product overview
Architecture diagram
Screenshot slot
Architecture diagram
Related Bobby Playbook principles
- Build versus buy
Legacy Access replacement with migration as delivery work
- Definition of success
Historical truth must survive the modernization