Elliott Storms
> asking AI unreasonable questions

I make hard
things fun.

Implementation project manager with a software engineer's brain. I turn complex fintech launches into successful ones - and bring everyone along for the ride.

100%
On-time launches
9
Launches in 5 years
850K+
Users live
$70B+
Client assets
// where i learned it Visa·Online Resources·ACI Worldwide·Fiserv·Lumin Digital
Let's talk →
// the through-line

It all starts with your Moon.

Your Moon is the outcome worth steering by: the reason you are using AI at all. I find it first, then keep the work in orbit around it, not the newest shiny tool. Method, architecture, and the launches behind me are one thread.

Find your Moon → See the system →
// what i do

I make the hard parts
feel possible.

Launch digital banking

End-to-end fintech platform implementations for credit unions and community banks. Nine launches in the last five years, every one on time, for institutions serving 17K to 194K accountholders each.

Drive AI adoption

I help teams move from AI-curious to AI-fluent - change management, prompt training, and automations that actually stick.

Bring people along

Clients make hard decisions faster when they're laughing with you, not bracing against you. Relationships outlast the project.

// case studies

Proof, not promises.

Three real projects, clients anonymized down to the outcomes. Here's what it looks like when it works.

// the rescue · tech lead
The rescue that became a reference.
Red → On-time
at-risk to delivered
// on-time launches
Nine launches, zero missed dates.
9 / 9
100% on-time record · last 5 years
// ai adoption
Teaching a team to actually use AI.
Hours/wk
admin eliminated · skeptics → daily users
Read the case studies → See the build log →
// build log

Shipped, dated,
and on the record.

A dated ledger of systems I've shipped - newest first, receipts linked where the code is public. The recurring theme: each one enforces its own claims instead of asking you to trust them.

  • 2026-07-20
    design-tokens

    A dark-first design system whose accessibility claims are enforced rather than asserted: a contrast contract plus a stdlib checker in CI that fails the build the moment any shipped color pair drops below the WCAG level it promised.

    elliottstorms/design-tokens →
  • 2026-07-20
    shell-fieldkit

    Five dependency-free shell libraries for the jobs that run when nobody is watching. Each one is the second version, written after the first failed quietly, with the original failure documented next to the fix.

    elliottstorms/shell-fieldkit →
  • 2026-07-20
    Provenance manifest

    A public tree-hash manifest that binds private source trees to public timestamps, published in the operator toolkit.

    elliottstorms/moonops-toolkit →
  • 2026-07-19
    gitscore loop

    An autonomous weekly loop that tends my public GitHub profile: it re-implements a public grading rubric as a local scorer, picks the highest-leverage improvement, ships it through the same PII and brand gates as everything else, then re-measures and writes every change to a ledger. The score moved from 69 to 217 on day one; the standing rule is that the score stays a byproduct of real work.

    elliottstorms →
  • 2026-07-17
    PII kit

    A deterministic, checksum-validating scanner with fail-closed gates on the tool-call and commit paths, two adversarial review agents, and CI that proves the gate still catches on every push.

    elliottstorms/moonops-toolkit →
  • 2026-07-16
    First-party visitor counter

    Two edge functions that keep analytics honest and entirely first-party: no cookies, no IP addresses, referrers cut to hostname, a UTM allowlist, and a fail-open contract so analytics can never break a page.

  • 2026-07-14
    One-screen operations snapshot

    A deterministic stdlib script that reads every workstream from files on disk and renders health and a next action per lane in about one second, with zero network calls.

  • 2026-07-11
    Self-healing skill library

    End-of-session digests distilled into evidence-cited improvements: 60+ digests and 17 ledgered runs so far, with risky changes proposed for human review instead of silently applied.

  • 2026-07-07
    Dispatch handoff system

    One session hands locked decisions and unfinished work to a future session as a paste-ready spec; the executing side verifies outcomes and logs every external effect.

    elliottstorms/moonops-toolkit →
  • 2026-07-06
    Eight-agent governance cabinet

    Chartered over a live content operation: one member, one vote, ties escalate to the human, and the design lead holds a real veto, which turned quality from a preference into a gate.

    See the architecture →
// ai, in practice

I don't just use AI.
I get whole teams using it.

I was a founding member, and the only woman, on my former company's AI Adoption Council, and my former team's designated AI Champion. I built the automations, then taught the humans: prompt engineering, practical dos & don'ts, and the change management that turns "we should try AI" into "we use it every day and love it."

Founding
AI Council member
Claudette-Code
Women-in-AI community I built
Team Champion
Designated AI lead
Certified
Building with the Claude API · Anthropic 2026
AI tools
Claude · Chat, Cowork, Code ChatGPT Perplexity Gemini Cursor GitHub
Automation
n8n Zapier Workflow automation Google Workspace
Practice
Prompt engineering Loop engineering AI change management Team training & enablement Agile / Scrum Waterfall & hybrid SDLC ownership Risk management Vendor management Scope & budget tracking
// leave it better

Adopt AI fast.
Leave no mess.

Everyone's being told to "go adopt AI right now," and most of them are leaving an ocean of garbage behind: half-checked docs, hallucinated answers nobody caught, automations no one maintains, tech debt quietly handed to the next unsuspecting person. I don't do that. My rule is simple: someone owns every AI output, it gets verified and maintained, and it's retired when it goes stale. You leave the knowledge base better than you found it.

That's not red tape - it's craftsmanship. And it happens to map cleanly onto the NIST AI Risk Management Framework, the exact playbook credit unions and community banks are pointed to.

// govern
Set the rules & ownership
Decide who's accountable for AI before it's everywhere. Every output has a name attached.
// map
Know where AI is used
Inventory every place AI touches the work - and be honest about where the risk actually sits.
// measure
Test accuracy, bias & drift
Check that it's right, that it's fair, and that it hasn't quietly gotten worse since launch.
// manage
Monitor, maintain & retire
The step everyone skips: keep it working, or decommission it when it's stale. Clean up after yourself.
Model risk · 2026 MRM guidance Vendor & partner-ecosystem risk Explainability Fair lending Member trust

Examiners and the NCUA point institutions to NIST AI RMF, so building this way isn't extra work, it's the work your board and your next audit already expect. And here's the secret: hard things are a lot more fun when nobody's dreading the mess you left behind. See how I set it up →

// dispatches

Field notes from
the AI trenches.

Short, opinionated essays on adopting AI in fintech - written by someone who has actually had to clean up after it. No hype, no doom.

Pinned · July 1, 2026
Don't leave a trash ocean.
Adopting AI without cleanup and ownership isn't progress. It's just faster mess-making - and in a regulated shop, that's a finding.
Craft · July 16, 2026
Whimsy is an adoption strategy.
I built a rigorously governed astrologer for fun, and she taught me more about adoption than most rollouts I've watched. Delight is what gets the rigor used.
Read the dispatches →
// the plot

Engineer who fell
for the people part.

I came up the technical way: taught myself SQL from "SQL 2008 for Dummies," became the product trainer for a digital banking platform, and a technical lead running developer teams for publicly traded banks. I’ve done it across the full spectrum, from Fortune 500 companies like Visa and Fiserv to fast-moving startups, where I stepped fully into the project manager seat. Along the way I realized the part of the job I loved most was the humans, so leading projects is exactly where I belong.

  • 2011
    Business Analyst
    Visa - Tier One merchant payments
  • 2012-2021
    Engineer → Technical Lead
    Online Resources → ACI → Fiserv
  • 2021-2026
    Project Manager → Sr. PM
    Lumin Digital · AI Adoption Council
// what people say

Trusted by the people
who worked beside me.

“She brings warmth, humor, and real care to every engagement. Her clients don’t just respect her, they love working with her. That combination of sharp professional skill and authentic human connection is rare.”
David Ringler
Product Management professional · worked with Elliott at Fiserv & Lumin Digital
Read full recommendation →
“She brought a sense of levity to stressful situations, helping teams stay focused without losing sight of the human side of the work. An exceptional project manager and an even better teammate.”
Jerry Hsu
Senior Implementation Engineer at Lumin Digital
Read full recommendation →
“Elliott has a unique ability to balance strategic planning with day-to-day execution… organized, dependable, and genuinely invested in the success of both their team and their projects.”
Aimee Hensley
Senior Product Manager at Lumin Digital
Read full recommendation →
“She’s got a real knack for getting things done… always pushing the team to think about how AI fits into our workflows, looking for smarter, more efficient ways to deliver for clients without losing the human touch that makes her so good at what she does.”
Tom Hockenbery, PMP
Project Management Professional · worked with Elliott for three years
Read full recommendation →
// now playing

The soundtrack to
making hard things fun.

Every on-time launch has a playlist behind it. Here's what's spinning while I untangle fintech rollouts, build automations, and ask AI unreasonable questions - straight from my To The Moon playlist. It updates live from Spotify.

Now spinning · To The Moon
// say hello

Working on AI or delivery?
Let's compare notes.

Elliott Storms
linkedinElliott Storms githubelliottstorms emailewheapes@gmail.com résuméPDF