UOA engaged our team to define and validate a product concept intended to reconnect modern online browsing behavior with the in‑office eyewear experience delivered by local optometry practices. While the engagement was executed under an agency structure, I led the initiative as product and engineering head, operating effectively as a fractional CTO. I directed strategy, research, experience design, and technical planning while managing a small cross‑functional team responsible for execution. The central challenge was not building a novel app. It was designing a system that aligned consumer behavior, business incentives, and operational realities in a way that could scale beyond a prototype.
Strategic Context
The eyewear market presents a structural tension. Consumers increasingly expect the speed and control of digital browsing, yet final purchasing decisions remain physical and experiential. Fit, comfort, and professional guidance are still best delivered in person. Independent practices, however, often lack a compelling digital discovery layer, which causes prospective patients to begin and sometimes complete their journey outside the local ecosystem.
The opportunity was to design a product that strengthens the in‑office model rather than competing with it. The risk was investing in an attractive concept that would collapse under workflow, data, or adoption constraints. Our mandate was to validate the opportunity and design a viable path forward.
Leadership and Scope
Although this was a freelance engagement, it was executed as a coordinated team effort. I managed the initiative end to end, aligning stakeholders, guiding research, directing UX strategy, and shaping the technical model. Designers and developers worked alongside me, but I owned the product direction, architectural decisions, and the trade‑offs that defined scope.
My responsibility was to ensure the product made sense strategically, worked operationally, and could be built responsibly.
Research and Insight Development
Discovery focused on two core audiences: end users and participating practices. The objective was to reduce risk early and ground decisions in observable patterns rather than assumption.
From the consumer perspective, the strongest signals centered on clarity and efficiency. Users wanted to narrow options quickly, save preferred selections, and feel confident that their browsing would translate into a meaningful next step. Convenience alone was insufficient; the experience had to increase confidence.
From the practice perspective, innovation was welcomed, but adoption hinged on operational alignment. Any solution that introduced excessive manual effort, unreliable data, or unclear economic value would struggle to sustain participation.
These insights reframed the initiative. Instead of expanding features, we focused on reliability, simplicity, and measurable impact.
Product Strategy
I structured the product around a single guiding outcome: moving a user from digital exploration to an intentional in‑office visit. This framing acted as a strategic filter for every decision. If a feature did not directly reduce friction or increase confidence on the path to an appointment, it was deprioritized.
By maintaining this discipline, we avoided drifting into full e‑commerce complexity. The product was positioned as a bridge between browsing and fitting, not as a replacement sales channel. That distinction clarified positioning and reduced unnecessary operational burden.
Experience Architecture
The user experience was designed to feel efficient, familiar, and purposeful. The interaction model emphasized rapid filtering, shortlist creation, and a clear transition toward a physical visit. Each step was structured to maintain momentum while minimizing cognitive load.
Design decisions were evaluated not only on aesthetic merit but on behavioral outcome. The question guiding the team was consistent: does this interaction meaningfully increase the likelihood of a confident in‑office visit?
Balancing user expectations with practice workflows required iterative collaboration between design and technical planning. The system had to feel seamless to the user while remaining feasible for participating offices.
Operational and Technical Validation
A substantial portion of the engagement focused on feasibility. Early product initiatives often fail because operational realities are deferred until late in the process. We deliberately stress‑tested assumptions around data integrity, workflow integration, and scalability.
I guided architectural decisions toward models that minimized manual overhead, reduced the risk of broken expectations, and allowed performance to be measured clearly. The technical approach was shaped as much by adoption strategy as by engineering preference.
MVP Definition and Rollout Strategy
The MVP was defined with precision. Rather than pursuing breadth, we prioritized credibility. The phased plan emphasized launching a focused, reliable version, observing real behavior, and iterating based on evidence.
Speed was important, but trust was foundational. In a system that connects digital discovery with physical appointments, reliability determines long‑term viability.
Outcomes
The engagement concluded with a validated product direction supported by structured research, a coherent value proposition for both audiences, a disciplined MVP scope, and a practical roadmap for phased execution.
Most importantly, the initiative moved from abstract concept to operational clarity. Stakeholders were left with a defensible strategy that aligned consumer behavior, business objectives, and technical constraints into a unified growth model.
Reflection
This case reflects how I operate when leading early‑stage initiatives within a team structure. I translate ambiguity into structured direction, manage cross‑functional execution, and make trade‑offs explicit before they become liabilities. My focus is not simply shipping features, but building systems that can withstand real‑world pressure and scale responsibly.
