Project Meridian

From specialist knowledge to a product people could use

The product began with deep domain expertise, but no defined product, user experience, or technical system. The owner understood the problem space, its users, and the underlying methodology. My responsibility was to translate that knowledge into a coherent product.

Domain decisions remained with the owner. I led product discovery, clarified requirements, challenged ambiguity, and turned complex knowledge into product strategy, user journeys, interaction models, and an executable delivery plan.

Building the first product from nothing

There was no inherited product model or established delivery team. I structured the proposition, mapped the primary family and caregiver journeys, designed the information architecture and visual language, and built the first working experience.

The MVP made the core loop testable: establish a baseline, record observations over time, surface patterns, and turn those records into evidence that could be understood and shared. It gave the domain owner something concrete to evaluate rather than a collection of ideas.

The MVP proved the idea; the next system made it real

A testable MVP was only the first milestone. As the lifecycle expanded, the product needed proper account states, family and caregiver permissions, consent history, report processing, operational support, analysis access, and data-rights workflows.

The product was restructured into native iOS and Android experiences, a client website, a staff operations dashboard, and a separate analysis surface. Shared backend services, domain contracts, asynchronous jobs, and infrastructure definitions now connect those experiences as one system.

One experience across five connected surfaces

The design responsibility extended beyond customer screens. A family’s action in the app could change a report state, create an operational task, affect what a caregiver was allowed to see, and determine what anonymized information could reach an analyst.

I designed these relationships as complete journeys rather than isolated pages. Nineteen documented flows connect onboarding, recurring records, reports, family access, notifications, settings, governed sharing, and account deletion across consumer and operational surfaces.

Designing, engineering, and reviewing at system scale

My role grew from product and interface design into technical architecture and hands-on delivery across native clients, React applications, ASP.NET services, data contracts, local cloud infrastructure, automated tests, and release planning.

Agents increased implementation capacity, but did not own product direction. Work was driven through written specifications, adversarial review, delegated implementation, independent audit, and human verification — especially where permissions, private records, deletion, or report accuracy were involved.

A real product system, with an honest release boundary

The platform works end to end in a production-shaped local environment. The clients, APIs, worker processing, identity, queues, databases, artifact storage, and operational tools run together against locally simulated cloud services.

It is not presented as a production launch. Cloud environments are the next controlled stage, deliberately gated behind end-to-end validation and infrastructure checks. The evidence here is the transformation from zero to MVP, and from MVP to a coherent product system ready for that next step.

Beyond financial products

My earlier experience was concentrated in banking, wealth management, and fintech. That work taught me to design within regulated environments, handle complex information, and create systems that remain consistent at scale.

This project broadened both my domain range and my design responsibility. It required working closely with a specialist without pretending to replace their expertise, then carrying that knowledge across strategy, service design, native and web experiences, operations, governance, architecture, implementation, testing, and release planning.

The result is a broader practice: bringing the rigour developed in financial services into a new domain, learning its constraints, and turning specialist knowledge into a coherent product system.