Skip to content

00 / Product design

Principal-level product design for software teams.

Add a principal designer to your team month to month, or scope a fixed package to test an idea before engineering commits. Either way you work directly with Brad Shroyer.

01 / Embedded principal designer

A principal designer on your team, without the hire.

Month to month

I join your team for a set number of days each week and own the design work from problem through release.

Who it is for
Software teams without a senior designer, or with more product work than their designers can cover.

001 / What the time covers

  • Product flows and interface design, inside your design system
  • AI feature design: what the model answers, how it shows uncertainty, where a person stays in control
  • Prototypes in code for the interactions that carry the most risk
  • Usability testing with your users, measured before and after
  • Design review with engineering through build and release

002 / How it runs

Days
A set number each week, agreed in the statement of work
Term
Month to month
Tools
Yours: design files, repository, and tracker
Meetings
One named principal in your planning and review meetings
Checkpoint
Weekly, on priorities and progress

02 / Fixed packages

Fixed scope, fixed timeline.

Scope and timeline fixed

Each package has a ceiling on what it covers and a set list of what you receive. Pricing follows the discovery call.

001

Tested prototype

Timeline
8 weeks

A high-fidelity prototype of a single user role’s core experience, tested with users in 2 rounds. An optional code-built component covers the highest-risk interaction. The output is a validated design, ready for engineering handoff.

Who it is for
Product teams and startups that need to test an interaction concept before committing engineering investment.

Scope

User role
1
Device class
1, mobile or desktop
Core screens
Up to 8, with full interaction states
User flows
Up to 2 through those screens
Code-built component
Up to 1, scoped during discovery
Usability testing
2 rounds, 5 to 7 participants each

Deliverables

  1. Discovery document: validation questions, success criteria, in-scope and out-of-scope flows
  2. User journey and storyboard mapping the prototype flows
  3. High-fidelity interactive prototype with realistic data and full interaction states
  4. Optional coded interactive component in production-quality code
  5. Usability testing plan: screener, interview guide, success metrics, observation rubric
  6. Round 1 and round 2 test reports with prioritized findings
  7. Tested-design rationale: annotated prototype documenting decisions that survived testing
  8. Engineering handoff spec: component inventory, tokens, interaction states, edge cases

002

Usability study

Timeline
4 weeks

Mixed-method research that answers one question about one user population, delivered as synthesized findings with prioritized opportunities.

Who it is for
Teams weighing a product or service change, and prime contractors that need user research as a deliverable.

Scope

Research question
1 primary
User population
1
Interviews
Up to 12, in depth, with target users, conducted remotely
Survey
Up to 1 supplementary, up to 200 responses
Expert interviews
Up to 3, short, with subject-matter experts
Readout workshop
Up to 1, with the client team

Deliverables

  1. Research plan: question, methods, criteria, recruitment plan, deliverable definition
  2. Recruitment screener and semi-structured interview guide
  3. Survey instrument and analysis (if scoped)
  4. Anonymized interview notes or transcripts, survey response export
  5. Synthesized findings document: themes, supporting quotes, prioritized opportunities, caveats
  6. Journey map or service blueprint visualizing the user experience
  7. Up to 7 prioritized opportunities, sized informally and tagged by impact and feasibility
  8. 60 to 90 minute facilitated readout, recorded

03 / AI features

AI feature design is part of the work.

It is covered in any engagement on this page. For AI added to a product you already have, there is a page of its own.

See AI integration

04 / Results

Results from past product design work.

Principal experience

System Usability Scale score on the Army’s airspace system, across 5 rounds of field testing.General Dynamics for U.S. Army
68 to 83
Read the TAIS case study
Faster core task times on the same system
17%
Internal security tools consolidated into 1 platform.Amazon Web Services
6 to 1
See the work
Task satisfaction in usability testing on that platform
4.6 out of 5

Delivered by Brad Shroyer as an employee of the organization named. Principal experience, not Veteran Design contracts.

05 / Next step

A straight answer on fit, in 30 minutes.

Tell me about the product and the constraint you are working under. If the work fits, a tailored statement of work follows within 48 hours of the call. AI tooling supports the work; I review and own the result.