01 / POSSIBILITY

Don’t be afraid of the

WHAT IF.

ERROL THOMAS / DSCX

Digital Systems Architect · Product Builder

I design and build digital products, systems, and experiences that solve real problems and create real impact.

SYSTEMS THINKER.
PRODUCT BUILDER.
PROBLEM SOLVER.

Selected Work

Built to solve.
Built to evolve.

Three products. Three very different problems. One common thread: turning complexity into something people can actually use.

Kintinuity / Healthcare SaaS

Care coordination designed around the people doing the caring.

Product strategy, experience architecture, care-network permissions, communication workflows, security-first systems thinking, and a scalable SaaS foundation.

Product StrategyUXSystemsHealthcare

View project ↗

BirthdayMe / Consumer Platform

A celebration product built as an ecosystem, not a feature.

Family accounts, onboarding, native bundle checkout, admin operations, responsive product UX, and the infrastructure required to move from idea to stable production.

ProductCommerceFamily AccountsOperations

View project ↗

LobeWork / AI Desktop Platform

AI tooling shaped into a product people can actually operate.

Desktop application UX, licensing, account bridge, admin console, model integrations, product strategy, and a production architecture designed to evolve.

AIDesktopLicensingArchitecture

View project ↗

How I think

DON’T BE AFRAID
OF THE PROBLEM.

The obvious problem is rarely the whole problem.

SYMPTOMUsers are dropping off.

Start with what people can see, feel, or describe — but don’t assume the first explanation is the answer.

ASSUMPTIONThe interface needs redesigning.

Challenge the first explanation. The obvious answer is often just a comfortable assumption.

FRICTIONImportant actions are hard to understand.

Question where the experience and the system disagree. Friction usually points somewhere real.

PATTERNThe workflow is fighting the user.

Look for repetition. The pattern underneath the complaint matters more than the complaint itself.

ROOT The product was designed around the system instead of the person.

Reduce the noise until the real constraint is clear enough to name.

The system behind the experience

01 / EXPERIENCE

THE INTERFACE
IS ONLY THE PART
YOU CAN SEE.

What the user sees, understands, and feels.

02 / PRODUCT LOGIC

WHAT CAN
HAPPEN.

Rules, permissions, states, and business logic define what the product is capable of doing.

03 / WORKFLOWS

HOW IT
MOVES.

People, information, and decisions move through a system — not a screen.

04 / DATA

WHAT IT
REMEMBERS.

Connected information gives the experience memory, context, and meaning.

05 / AUTOMATION

WHAT MOVES
WITHOUT YOU.

Triggers and actions remove unnecessary manual work and keep the system moving.

06 / INFRASTRUCTURE

WHAT HOLDS
IT TOGETHER.

A secure, scalable foundation keeps every visible and invisible layer reliable.

USERRULESFLOWDATAAUTOMATIONINFRA

How I build

BUILD. LEARN.
RECONSIDER.

The next version should know something the last one didn’t.

Assumption

Every version starts with a hypothesis about what should work.

My Thoughts

Ideas, notes,
and perspectives.

A working notebook on systems, products, clarity, and the decisions underneath the interface.

Read all thoughts ↗

01 / Note

The systems thinking advantage

Why thinking in systems creates better products and better outcomes.

02 / Essay

Designing for clarity in complex products

Clarity isn’t minimalism. It’s making the complex feel inevitable.

03 / Idea

The future is composable

Products aren’t monoliths. They’re connected capabilities.

BRING ME
THE PROBLEM.

Product. System. Experience.
If it needs to work better,
I’m interested.

View my story + CV ↗

WHAT IF.

Built to solve.
Built to evolve.

Care coordination designed around the people doing the caring.

A celebration product built as an ecosystem, not a feature.

AI tooling shaped into a product people can actually operate.

DON’T BE AFRAID
OF THE PROBLEM.

THE INTERFACE
IS ONLY THE PART
YOU CAN SEE.

WHAT CAN
HAPPEN.

HOW IT
MOVES.

WHAT IT
REMEMBERS.

WHAT MOVES
WITHOUT YOU.

WHAT HOLDS
IT TOGETHER.

BUILD. LEARN.
RECONSIDER.

Ideas, notes,
and perspectives.

The systems thinking advantage

Designing for clarity in complex products

The future is composable

BRING ME
THE PROBLEM.

THE PART
YOU CAN SEE.

WHAT CAN
HAPPEN.

HOW IT
MOVES.

WHAT IT
REMEMBERS.

WHAT MOVES
WITHOUT YOU.

THE FOUNDATION
BEHIND IT ALL.

EXPERIENCE
IS THE SURFACE.

First, who am I talking to?

What are we working on?

What’s getting in the way?

Give me the useful context.

Your request, distilled.

Thanks — I’ve got it.

WHAT IF.

Built to solve.Built to evolve.

Care coordination designed around the people doing the caring.

A celebration product built as an ecosystem, not a feature.

AI tooling shaped into a product people can actually operate.

DON’T BE AFRAIDOF THE PROBLEM.

THE INTERFACEIS ONLY THE PARTYOU CAN SEE.

WHAT CANHAPPEN.

HOW ITMOVES.

WHAT ITREMEMBERS.

WHAT MOVESWITHOUT YOU.

WHAT HOLDSIT TOGETHER.

BUILD. LEARN. RECONSIDER.

Ideas, notes,and perspectives.

The systems thinking advantage

Designing for clarity in complex products

The future is composable

BRING METHE PROBLEM.

Built to solve.
Built to evolve.

DON’T BE AFRAID
OF THE PROBLEM.

THE INTERFACE
IS ONLY THE PART
YOU CAN SEE.

WHAT CAN
HAPPEN.

HOW IT
MOVES.

WHAT IT
REMEMBERS.

WHAT MOVES
WITHOUT YOU.

WHAT HOLDS
IT TOGETHER.

BUILD. LEARN.
RECONSIDER.

Ideas, notes,
and perspectives.

BRING ME
THE PROBLEM.