32 projects. One year.
A prototype makes a discussion concrete. At AstraZeneca, I learned the workflows, wrote requirements, designed interfaces, and built prototypes the team could review. I revised them with business owners and engineers. ECS built the risk register from my requirements and released it in March 2026. Other examples here show prototype decisions, including services and approval rules that still needed to be connected.
Five closer looks at the work
Five illustrated stories from the work. The complete 32-entry index follows below.
View original Original prototype · sample data Launched
A risk register for US Oncology Compliance
- My contribution
- I wrote the requirements, prototyped the interface and coordinated business testing with the Compliance owner and ECS.
- Where it landed
- ECS built the first release in Power Apps. It went live in March 2026.
View original Policy review artifact Proposed
Record the decision. Don't make it.
- My contribution
- I specified intake and access rules, mapped two research-review processes and made prototypes for the open decisions.
- Where it landed
- The policy exception workflow had not been approved by my last spec.
View original Original frontend prototype · fixture data Working product
Designing review into AI-drafted slides
- My contribution
- I designed and built the shared frontend prototypes, narrowed medical use cases, shaped the backlog and put review points into the workflow.
- Where it landed
- The Workbench was a working product. These sample-data screens show the interface and review ideas I developed within it.
View original Retrospective design exploration Pilot
One prototyper, about ten engineering teams
- My contribution
- I gave engineers shared tokens and components, with rules for brand conflicts and a first pilot team.
- Where it landed
- Recorded adoption outside the system repository stayed small.
View original Original forecasting prototype Prototype decisions
AI prototypes as cheap tests
- My contribution
- I built interface prototypes to test a specific question before teams committed to a build.
- Where it landed
- For the forecasting prototype, the leads handed off the non-AI core and deferred its AI layer.
August 2025 — August 2026
Follow the work.
32 documented entries across project families, features and shared foundations. Pick a thread, inspect the work, then follow the decision behind it. These are not 32 independently shipped products.
32 of 32 entries
Compliance and governance5
Field and commercial experiences8
Assistants and operational tools6
Global Medical Affairs Workbench10
The shared foundation3
Slide builder
Jul to Aug 2026
Part of
Open full size My contribution
Designed review steps for the medical slide builder.
What this shows
This August 3 artifact shows prototype review gates. It does not demonstrate a connected scientific approval or generation service.
What moved forward
August 2025 to August 2026 · US Oncology, then Global Medical Affairs from May 2026
Mar 26Risk register released
I wrote the requirements and prototyped the interface. ECS built and released the Power Apps product.
See the risk register work43 / 32Observed, then fixed
Business testing logged 43 observations in four days. ECS fixed 32 during that window.
See the testing and release9 → 3A smaller demo recommendation
I estimated nine Workbench features at 14 to 26 person-weeks against about two available. I recommended building three. I have no record that the program adopted the recommendation.
See the Workbench decisions