Edwards Event Operations

Enterprise medical events require more than a date and venue. Teams prepare agendas, invitations, certificates, attendee materials, and other event specific documents, then coordinate reviews, approvals, printing, and delivery across several roles.

When those steps are split between files, messages, and manual handoffs, the status of the event becomes difficult to trust. The design challenge was to create one system that could carry both the event and every related document from an initial brief to final production.

The platform needed to make progress visible without flattening a careful approval process.

I worked with Edwards stakeholders and engineers to trace the operational path from event setup through document selection, personalization, review, approval, print ordering, and delivery. Before designing individual screens, I defined the objects moving through that path, the states they could enter, and the role responsible for each transition.

The central constraint was traceability. A global enterprise workflow needs dense information and reusable templates, but it also needs clear ownership, governed approvals, version confidence, and predictable handoffs. I used task flows and shared status language to test whether each role could answer three questions: what is this, where is it now, and what happens next?

The available project evidence documents the resulting interface and workflow, but not formal usability sessions or post-launch analytics. I therefore treat the design rationale as documented process and the built product as shipped scope—not as proof of efficiency gains.

The first design deliverable was a lifecycle everyone could reason about—not a dashboard.

As the solo product designer, I structured the experience around a simple relationship: an event contains the operational details, the documents created for it, and the actions required to move those documents forward. That model kept planning and production connected instead of treating documents as unrelated files.

The product navigation reflects the lifecycle directly—events, drafts, approvals, print orders, templates, and billing—while the event workspace preserves the context between those stages. Shared status language makes it possible to understand whether work is still being prepared, waiting for review, approved, or already in production.

I led the product design independently and partnered with stakeholders and engineers as the model moved from flows and interface structure into a built enterprise platform. The verified result is the connected product scope: event planning, reusable documents, approval queues, print production, billing, and administration now share the same event and document lifecycle.

The strongest evidence is that the workflow exists as a coherent product across the screens shown here. I am not claiming time savings, error reduction, adoption, or business impact without product analytics. Those remain hypotheses to evaluate after teams complete real event cycles in the system.

Shipped scope is evidence of delivery; operational improvement still needs measurement.