Product operations portfolio · Prepared for Solum Health

I make complex operations easier to run.

I turn customer problems and recurring operational failures into clear requirements, useful internal tools and product improvements that work in production.

See selected work ↓ mitcheladiele@gmail.com

PRODUCT OPERATIONS LIVE WORKFLOW

Operational improvement

CUSTOMER SIGNALRepeated access failures

Pattern found across support and service data

HIGH IMPACT

1UNDERSTANDFind the real cause

2DEFINESet expected behaviour

3DELIVERBuild and validate

4MEASUREConfirm the outcome

MY ACCOUNTABILITY

Priority, requirements, trade-offs, acceptance and production outcome

REAL PRODUCT EXPERIENCE

Verified from live service records.

0paying customers

0authenticated sessions

0usage sessions

0controlled access channels

01 / SELECTED WORK

What my work looks like
in practice.

Clear problems, clear ownership and outcomes that made a live service easier to operate.

CASE 01

Preventing unreliable data from becoming a customer-facing mistake

The problem: External providers could disagree, arrive late or report an event as complete while it was still progressing. Customers then received incorrect updates and operators had to repair them live.

MY PART

Reframed repeated incidents as one product problem and defined how a trustworthy state should progress.

DECISIONS

Required stronger evidence for risky changes, explainable decision logs and safe handling of incomplete results.

ROLLOUT

Kept the new logic in shadow mode until comparison reports showed how it behaved against production.

RESULT A reusable control system replaced a cycle of one-off fixes, while keeping the operator in control of promotion.

SHADOW CONTROLLEREvidence: 3/3

✓

STATE 01Scheduled

confirmed

✓

STATE 02Active

confirmed

STATE 03Terminal?

validating

STATE 04Complete

held

DECISIONHold transition

Provider conflict detected. Awaiting sustained evidence.

ACCESS REQUESTAuthenticated

✓VALID SESSION

CASE 02

Making customer access reliable when traffic increases

The problem: A login flow that worked for one person could still fail when many customers arrived together. I connected that risk to a previous database-contention incident, defined the expected behaviour and required realistic load testing.

Result: a safer access flow backed by test evidence, not assumptions.

CONTROL SURFACE

Service stateHEALTHY

Recovery

Decision logVISIBLE

CASE 03

Turning repeated emergencies into everyday product controls

The problem: Important recovery actions depended on terminals, memory and manual intervention. I defined operator-facing controls, clear health states and safer recovery paths designed for use under pressure.

Result: recurring interventions became visible, repeatable workflows.

02 / HOW I WORK

I use AI to move faster.
I own what ships.

I use AI coding and automation tools to accelerate delivery. My responsibility is to identify the right problem, define the outcome, direct implementation, challenge weak approaches and decide whether the result is ready for real users.

Frame the actual problem

Separate symptoms from the underlying product or operating failure.

Set constraints and trade-offs

Balance customer impact, speed, cost, reliability and reversibility.

Define acceptable behavior

Write scenarios, edge cases, failure states and measurable acceptance criteria.

Accelerate implementation

Use Codex, Claude Code and specialized tooling to turn precise requirements into working systems.

Explore alternatives quickly

Compare architectures, investigate incidents and expose assumptions before committing.

Preserve operating context

Maintain structured memory, documentation and evidence across interconnected workstreams.

Test real workflows

Validate customer, administrator and operator journeys across devices and failure conditions.

Observe production behavior

Use health signals, logs, state and user outcomes to catch what a clean demo misses.

Iterate without ego

Reject incorrect work, simplify over-engineered solutions and preserve safe rollback.

WHY THIS TRANSFERS TO SOLUM

Different industry.
The same operating muscles.

Workflow thinking

I can follow a messy process across users, systems and handoffs, then define a simpler operating path.

Frontline to product

I turn recurring customer and operator friction into requirements, priorities and reusable improvements.

AI enabled execution

I already use the tools named in the role to investigate, prototype, test and ship faster without outsourcing judgment.

03 / EXPERIENCE

Technical enough to go deep.
Operational enough to ship.

2024
to 2026

INDEPENDENT SUBSCRIPTION DIGITAL SERVICE

Product Owner & Operations Lead

Own product priorities, customer workflows, payments, administrative tooling, service reliability, behavioral QA and the conversion of recurring incidents into reusable capabilities.

2023
to 2024

IMISI 3D

Lab Associate & Technology Facilitator

Facilitated immersive-technology demonstrations and learning sessions, supported participant setup, resolved practical issues and helped gather feedback for improved delivery.

2023
to 2024

AR/VR AFRICA

Community Associate

Support community engagement and accessible communication around emerging-technology programmes, events and ecosystem opportunities.

EDUCATION BSc Computer Science, Second Class Upper

Abia State University, Uturu · 2021 to 2025

WHAT I AM LOOKING FOR

A small, ambitious team where real workflows shape the product.

I am strongest where workflows are still messy, ownership matters, and a useful internal tool is better than another meeting about the problem. I am based in Lagos and open to remote work or relocation.

LET'S TALK

Give me a difficult
operating problem.

mitcheladiele@gmail.com ↗