BLOOMBERG D.A.P.
A phase-aware portal for Bloomberg Philanthropies' Digital Accelerator Program — UX lead, full design system, developer-ready handoff in 90 days.
- Problem
- A multi-phase program for nonprofit Tech Fellows with no portal, no design language and no brief.
- What we did
- Sole UX designer: shaped the IA from working sessions, wireframed 15+ screens, then built a full design system in Figma, token JSON and React.
- Outcome
- Approved by Bloomberg senior leadership on the first formal presentation and handed off to dev in 90 days.
A portal that guides nonprofit leaders through every phase of the program.
The Bloomberg Digital Accelerator Program sends nonprofit Tech Fellows through a structured, multi-phase journey — learning sessions, document submissions, vendor selection, and implementation. The program had no portal, no design language, and no brief.
Bloomberg Philanthropies and their managing consultant, the Lapine Group, needed a secure, phase-aware web portal that would guide each Fellow through exactly where they were in the program — surfacing the right tasks, resources, and connections at exactly the right time.
I was brought in as the sole UX designer. 90 days later: a full design system, 15+ annotated screens, a React component library, and a design token JSON file — all approved by Bloomberg senior leadership and handed off to dev.
Bloomberg Philanthropies — one of the largest philanthropic organizations in the world. The DAP invests in nonprofits' digital capabilities, cohort by cohort.
Build a centralized, secure portal for Bloomberg Tech Fellows — phase navigation, task guidance, document library, peer directory, and vendor directory. No existing design language. No prior UX.
Full Figma handoff, design token JSON, and React component library approved at the Bloomberg senior leadership level. Developer build targeting April 30, 2026.
A dream. A powerpoint. No team. Full system.
This project started with a series of working sessions with Dave Ebert at the Lapine Group — no formal document, just conversations about how the program actually ran. From there I shaped the full IA, defined the page inventory, and began wireframing while the content was still being written in parallel.
The design system came next — built from Bloomberg's public brand, elevated for a portal context, and documented in three formats: a Figma file, a machine-readable token JSON, and a React component library ready for WordPress handoff. Bloomberg leadership reviewed the final comps and approved on the first formal presentation.
Working sessions with Lapine Group. No brief — UX architecture shaped from conversation. Full page inventory and nav structure defined.
15+ screens covering dashboard, five phase pages, document library, directories, calendar, and event pages. Full team review with Bloomberg stakeholders.
Color tokens, type scale, spacing, 30+ components — built from scratch and documented in Figma, JSON, and JSX. Every state. Every variant.
Full-fidelity comps across all screens. Iterated through Bloomberg stakeholder feedback rounds with same-day and next-morning turnarounds.
Annotated Figma file, design token JSON, React component library, written reference doc, and a Loom walkthrough — handed to Chapter 324 for WordPress build.
Tools + Team
- Figma
- Claude Code
- Design Token JSON
- React / JSX Components
- Figma Annotated Handoff
- Loom Walkthrough
- Dan Nemirovsky (UX Lead)
- Dave Ebert · Lapine Group
- Jason Froderman · Dev
- Bloomberg Philanthropies
Three calls that shaped the portal
-
No brief? Start drawing.
- Tradeoff
- Wireframing while the content was still being written, with conversations standing in for a formal document.
- Result
- A full IA, page inventory and nav structure shaped from how the program actually runs.
-
Organize around the phase
- Tradeoff
- Every screen has to know where a Fellow is in a five-phase journey, not just list everything at once.
- Result
- A portal that surfaces the right tasks, resources and connections at the right time.
-
Ship the system in three formats
- Tradeoff
- Documenting every state and variant in Figma, token JSON and JSX, not just handing over comps.
- Result
- A developer-ready handoff to Chapter 324 for the WordPress build, with a reference doc and Loom walkthrough.
Selected work.
09 ARTIFACTS
01 · Dashboard
03 · Dashboard Detail
04 · Wireframes
05 · Document Support
06 · Program Calendar
08 · Event Detail
No brief turned out to be a feature, not a bug. When nobody hands you the requirements, you get them from how the program actually runs, and the design system becomes the spec everyone else builds from.