An iPad app showing leadership whether the organisation is ready for AI, before anyone judges the return. Shaped with leadership and portfolio managers, designed and coded by me, and now with the development team for a native build.
A large UK enterprise
Lead designer and builder, from discovery to a signed-off, working prototype. Research, strategy, UI, motion, accessibility and the AI build.
Leadership, portfolio managers and the people using AI day to day. QA tested the prototype before development began. Handed to the development team for the native Swift build.

From first stakeholder conversation to a working app
Stakeholders tapped through it with realistic data, not static screens
Testing started before development did
States audited
Then I went where the work happens. One-on-ones and deep dives with portfolio managers and the people using AI every day.

Two findings changed the brief. The people being trained weren't the people actually using AI. And some were reaching for tools the organisation never provided, like Gemini, for quick fixes. Why, when they'd been given their own? That's still the question I'd most like answered.
So I built it. Mostly by briefing AI the way I'd brief a designer.
Claude was where I thought: strategy, structure, every touch decision settled before building. The look took shape in Claude Design. When a tweak was quicker to show than describe, I made it in Figma and sent the screenshot back with comments. Claude Code built every screen.
Rough sketches and reference shots for layout. GIFs and short clips for motion. A picture got there faster than a paragraph.

Every problem a review caught became a rule, and every rule became a check.

A smoothed chart line peaked at 54.19 when the real maximum was 53. Now no curve can overshoot its data.
Early on, Targets said 3 of 4 targets were on pace. Those run rates had been typed in.

Once the build derived them from quarterly history, one target fell behind. The headline dropped to 2 of 4.
Straight from the one-on-ones. Two populations, measured two ways. The gap between them is the finding.

Raw totals always crown the biggest team. Per active user, the smallest portfolio leads. So it's a switch, not a footnote.


A native iPad app also runs on Apple Silicon MacBooks, so one build covers both. No control depends on hover, so it works the same with a finger or a trackpad.

Leadership chose readiness first. The sponsor signed off on something they could use, not a picture of it. Manifest is now with the development team for the native build.
With Manifest, every portfolio lead will see what's holding them back and who owns the next step.
More Case Studies
E-Commerce at 35,000 feetProject type
Platform that Saved £0.25M annuallyProject type