Skip to content
Osa Omoregie

About

The story

I have spent most of my life making things in mediums that had no reason to talk to each other. Photographs and video. Graphics and motion. Then a character universe, incorporated in 2021, which turned into a comic, a game, a collectibles line and a community that named itself. Then software, because at some point the only way to get the thing I wanted was to build it.

For a long while that looked like a lack of focus. Photographer, videographer, designer — three business cards for one person, none of them describing the actual work. The through-line was invisible even to me.

What made it legible was emerging technology, and not for the reason people usually give. It is not that AI lets me make more things faster. It is that the bottleneck moved. When execution stops being the scarce resource, the scarce resource becomes knowing what to make, holding it to a standard, and building a system that can produce it more than once. Those happen to be the three things I had accidentally spent a decade practising in four unrelated disciplines.

So the work now looks like this: I take an idea, design the pipeline that can produce it — a shot protocol, a design system, a canon, an economic model — and then direct the thing through that pipeline until it is finished. On a series that means character masters, a cost ladder and a pre-flight gate before a frame is bought. On a product it means a constitution and a list of what the thing refuses to do before a feature list. Different outputs, identical job.

I am not precious about which medium it lands in. I care that it is good, that it ships, and that the second one costs less than the first.

Technology delivery

Alongside all of this I have spent three years inside a bank, working in technology delivery — service-level assessments, policy governance, requirements, quality assurance and risk tracking. That experience is part of my technical practice: understanding a process, documenting what it needs and helping people work through it.

It also shapes my creative work. It is why a project arrives with a cost model derived from measured rates rather than a guess, why the pipeline has a mechanical pre-flight gate instead of a hope that everyone stays careful, and why a product brief opens with the things the product is not allowed to claim.

My earlier systems QA work at ZT Systems adds hands-on server testing and troubleshooting experience. Together, these roles ground the project work in documentation, quality checks and practical problem solving.

Workflow automation

Condensing a teammate's repetitive tasks

A teammate on the Policy Governance Team was handling repetitive Technology Service Level Assessment (TSLA) tasks. I used Copilot to help automate and condense that work.

The result was a 70% reduction in that teammate's workload on those tasks, not a team-wide productivity figure.

My contribution was applying Copilot to the repetitive work and helping a colleague complete it more efficiently. This summary excludes internal records, prompts and implementation details.

Experience

Bank of America
Analyst I — Tech Delivery
Mar 2025 — present
Bank of America
Business Analyst Apprentice
Sep 2023 — Mar 2025
ZT Systems
Systems Quality Assurance Technician
Jun 2023 — Aug 2023
Amazon
Senior Fulfillment Associate II
Sep 2018 — Jan 2021

Certifications

  • AWS Certified Cloud Practitioner (earned April 2026)
  • CompTIA A+ (1101 · 1102)
  • Google IT Support Professional
  • Google Project Management

Contact

If any of this is the shape of a problem you have, I would like to hear about it.