Teacher certification is a high-stakes, regulated journey where confusion directly impacts trust and enrollment. At Teachers of Tomorrow, I led the implementation of strategic recommendations into scalable layouts, reusable backend modules, and clearer certification pathways that could be realistically built, maintained, and evolved over time.
Role: Website & UX Manager
Scope: Experience execution, UX systems, governance
Platform: WordPress + Advanced Custom Fields
Users: Prospective teachers navigating multi-state certification
Focus: Turning strategy into scalable, shippable systems
Teachers of Tomorrow supports alternative teacher certification across multiple states, each with its own eligibility rules, timelines, and documentation requirements. For many candidates, this represents a major career shift involving time, cost, and personal risk.
We work with an external UX agency on a comprehensive audit to identify friction points across the certification journey. The challenge was no longer identifying issues, but ensuring those recommendations translated into improvements that teams could actually ship and sustain.
Legacy layout
Improved structure and clarity
The audit identified opportunities. My responsibility was deciding what changed, how it shipped, and what scaled. My role was to translate the audit findings into a phased implementation plan that balanced clarity, feasibility, and long-term system health. The goal wasn’t a disruptive redesign, it was meaningful improvement that delivered value quickly while reducing future UX and development debt.
To do this, I created and led the UX Audit Implementation Roadmap, aligning experience priorities with engineering capacity, marketing needs, and compliance constraints.
Audit Insights
Experience Decisions
Reusable Systems
Cross-functional synthesis used to align priorities before execution
This shifted the work from recommendations into systems teams could actually build and maintain.
To reduce development cycles and support long-term scalability, I partnered with engineering to define reusable backend modules using WordPress and ACF.
Rather than treating certification requirements as static content, the experience was reframed around candidate confidence, helping users understand what was required, what to do next, and whether they were ready to proceed.
WordPress + ACF
Reusable Modules
Certification Pages
Experience decisions were embedded into layout rules, CTA logic, and content hierarchy, allowing marketing teams to move faster without reintroducing friction or trust issues.
Certification journeys were redesigned using modular layouts that clarified steps, requirements, and actions. Shared structures ensured consistency across programs while allowing for state-specific variation.
Layouts were refined to surface critical information earlier and clarify next steps, supporting conversion without urgency or pressure.
WordPress Core
ACF Modules (Fields & Blocks)
Certification Page Layouts
Pattern Area
CTAs
Rule
Field-driven content
Content hierarchy
Requirements before benefits
Layout spacing
Consistent vertical rhythm
Accessibility
Contrast and focus states
Pattern Area
Before
After
Certification
Variability by State
Experience Strategy & UX Systems
Experience improvements were designed in close partnership with engineering to ensure solutions were technically feasible, maintainable, and scalable.
By aligning UX patterns with backend capabilities, we reduced rework, accelerated iteration, and created a foundation for future improvements without increasing technical debt.
Governed
UX Patterns
Compliance
Requirements
Modular
Certification Layouts
Engineering
Capacity
Marketing
Velocity Needs
Constraints
Outputs
Reusable
ACF Modules
Immediate clarity and risk reduction
Focus: Reduce confusion and friction without disrupting active enrollment
Phase 1
This phase prioritized changes that could ship safely and deliver immediate value.
Optimization Readiness
Focus: Create a foundation for continuous improvement
Phase 3
This phase ensured the experience could evolve without requiring repeated redesigns.
Why this approach worked
Systemization and scale
Focus: Enable faster iteration while reducing development overhead
Phase 2
This phase shifted improvements from one-off fixes to repeatable systems.