UX Design · Product · AI · 8 Years

Tyler Quackenbush

"Make the problem simple, then solve the simple problem."

01 · The Work

I take an ambiguous problem, a federal agency that won't sign without proof, an AI rollout with no real plan, and turn it into something people can actually use.

I'm Tyler. Eight years doing this for a federal contractor and a public university. Most recently: designing concept prototypes that win federal contracts, running the company's AI-native training program, and managing the design team behind both.

02 · Selected Results

Across federal and higher-ed products, the work I lead with.

0

Federal concept dashboards designed

0+

Employees reached through AI training

0+

Pages redesigned at UNG

0%

Engagement increase

Read the case studies →

03 · Selected Work

Two engagements, and the plain-language problem each one actually was.

Federal

Agile Defense

Senior UX Designer · 2021–Present

Federal agencies won't sign a contract on a promise. Agile Defense proves the idea first, building working concept prototypes clients can react to before a line of code gets written. I've designed four of those prototypes, run a design team, and now build the training teaching 1,500 employees to use AI the same deliberate way.

Result: 4 federal concept dashboards designed, AI training reaching 1,500 employees company-wide.

Read the case study →

Higher Ed

University of North Georgia

Web Designer · 2016–2021

A public university site grows one department at a time, for twenty years, and nobody's responsible for the whole thing. Mine had 20-plus navigation menus. I decided what stayed, what merged, and what finally got cut.

Result: 35% increase in engagement across a 5,000+ page site.

Read the case study →

04 · The Approach

Three steps, repeated on every engagement regardless of industry.

01

Audit

Read what's already live and flag what's unclear, redundant, or failing an accessibility check before writing anything new.

02

Draft

Write the plain-language version first. Then fold back in the legal, brand, or technical requirements without losing the clarity.

03

Ship

Test it with the people who'll actually push back (legal, dev, a real user) and hold the line through revisions.

How I work →

There's always a clearer way to say it. Let's find it.