Creative Paragon Logo
The Humans Behind the Systems

Small Team.
Big Systems.
Very Strong Opinions About Good UX.

Creative Paragon is a product and technology studio built around a simple idea: technology should make people's lives easier, not give them another thing to fight with.

We combine product strategy, system architecture, design, delivery, and a frankly unreasonable amount of curiosity to turn messy ideas and complicated workflows into tools people actually want to use.

Where tech meets heart — and occasionally a very opinionated Chihuahua.

Meet Creative Paragon

Two humans, two highly unqualified executives, and a lot of tabs open.

Stylized editorial illustration of Brittany Trugman, Chief Product Officer, reviewing product wireframes in a dark neon studio

Brittany Trugman

Chief Product Officer

Turns "we have an idea" into "here's exactly what we're building."

Brittany lives in the space between what a client says, what they actually need, and what the product eventually becomes.

She leads product strategy, requirements, client collaboration, mockups, QA, SOPs, contracts, and the important art of asking, "Okay, but what happens if the user does THIS?"

If there's a fuzzy idea floating around a meeting, Brittany will probably turn it into a workflow, a screen, a requirement, and three follow-up questions before everyone else has finished their coffee.

Her superpower is making complicated things understandable — and making sure the thing we built is actually the thing people needed.

Known for

Turning conversations into requirements.

Frequently heard saying

"But what does the user see?"

Product philosophy

If people need a training manual to understand the button, we should probably fix the button.

Stylized editorial illustration of Katrina Rogers, Principal Architect, surrounded by system diagrams in a dark neon studio

Katrina Rogers

Principal Architect

Builds the system behind the idea — then probably builds a system to manage that system.

Katrina turns product ideas into working platforms, architectures, integrations, workflows, and the occasional suspiciously elaborate diagram.

As Creative Paragon's Principal Architect, she leads solution architecture, platform engineering, technical delivery, documentation, systems design, and the deeply satisfying process of making disconnected tools finally talk to each other.

She has a particular fondness for taking a process that currently involves email, three spreadsheets, somebody's memory, and a prayer — and turning it into an actual system.

If Brittany defines where the product needs to go, Katrina figures out how the entire machine gets there without catching fire.

Known for

Seeing an entire workflow hiding inside one annoying manual step.

Frequently heard saying

"Wait. We can automate that."

Architecture philosophy

If the process lives entirely in someone's head, eventually we are going to have a problem.

Executive Oversight

Every great company needs supervision.

Illustrated portrait of Teddy

Teddy

Creative Paragon Mascot

Chief Morale Officer

Enthusiastic, concerned, involved, ready to escalate.

Teddy oversees Creative Paragon's most critical operational functions: lap availability, snack compliance, unexpected meeting interruptions, and determining whether anyone has been working entirely too long without paying attention to him.

His technical qualifications remain unclear. His confidence in those qualifications is absolute.

Teddy specializes in sitting directly beside whichever human is attempting to concentrate, conducting highly sensitive perimeter inspections, and reminding leadership that every scalable organization requires scheduled breaks.

He has never missed a deadline because nobody has successfully assigned him one.

Department

Executive Vibes

Core competency

Looking extremely concerned about completely normal events.

Preferred collaboration tool

Lap.

Escalation procedure

Bark once. Reassess. Bark again.

Illustrated portrait of Otis

Otis

Creative Paragon Mascot

VP of Strategic Observation

Calm, skeptical, observant, mildly disappointed.

Otis approaches technology the way every great quality-assurance professional should: with skepticism.

While Teddy handles morale, Otis is responsible for quietly observing Creative Paragon operations from a carefully selected location and determining whether any of this is actually up to standard.

His methodology is rigorous. First, observe. Then, observe from somewhere slightly higher. Then, sit directly on the thing someone needs.

Otis specializes in quality control, keyboard interference, unannounced desk audits, and staring at leadership until someone realizes they've made a mistake. He rarely attends meetings voluntarily, but maintains complete confidence that he could have solved the problem faster. His approval is difficult to earn. His presence is mandatory.

Department

Quality Assurance & Judgment

Core competency

Finding the one flaw nobody else noticed.

Management style

Silent evaluation.

Preferred collaboration tool

Whatever you're currently trying to use.

Together, they maintain Creative Paragon's rigorous standards for morale, quality assurance, snack distribution, and unattended office chairs.

How We Work

Product brain meets systems brain.

Listen First

We start by understanding the people, the problem, and the weird little workarounds everyone has quietly accepted as normal.

Make It Make Sense

We turn conversations into requirements, workflows, architecture, prototypes, and a plan people can actually follow.

Build for Real Life

We build around how people actually work — including the messy parts nobody remembered to put in the requirements document.

Professional enough to trust with your infrastructure.
Human enough to admit the spreadsheet is getting out of hand.

Creative Paragon exists because good technology does not start with technology.

It starts with understanding how people work, where they're getting stuck, what they're trying to accomplish, and what would make tomorrow a little easier than today.

Then we build from there.

Got a messy process, ambitious idea, or suspicious number of spreadsheets?