Tyler QuackenbushUX Design · Project Management · AI · 10+ Years

Make the problem simple, then solve the simple problem.

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

I want to work on hard, ambiguous problems, in a role that mixes design and project management.

01 · The work

A UX designer and project manager.

I'm Tyler, a UX designer and project manager with over 10 years at a government contractor and a public university. Most recently, I help design and run the 10-day Pre-Discovery sprints that help win federal contracts. I also helped build AI Foundations, the course every employee takes before using our internal AI tools, and I'm project manager for Experience Studio, the four-person design team.

Selected results

4

Concept dashboards contributed to

~1,500

Employees reached through AI training

3 in 3 days

Course modules, up from 1 in 2 weeks

20+

Navigation menus consolidated into one

Read the case studies →
02 · Selected work

Two engagements, and the problem each one turned out to be.

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 competitors have written a proposal. I've contributed to four of those prototypes, project-manage a design team, and help build the AI training that reaches around 1,500 employees.

Result
Contributed to 4 concept dashboards; AI training reaching around 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, and nobody's responsible for the whole thing. Mine had 20-plus navigation menus. I helped decide what stayed, what merged, and what finally got cut.

Result
20+ navigation menus consolidated into one structure across a 5,000+ page site.
Read the case study →
03 · The approach

Three steps, repeated on every engagement.

The same three steps, regardless of industry.

  1. AuditRead what's already live and flag what's unclear, redundant, or failing an accessibility check before building anything new.
  2. DraftBuild the first real version, a prototype, a plan, a decision, before folding back in the legal, brand, or technical requirements.
  3. ShipTest it with the people who'll push back (legal, dev, a real user) and hold the line through revisions.
How I work →

Have a messy problem? Let's make it simple.