Product strategy & discovery
Clarify the problem, map the workflow, and turn ambiguous requirements into focused product direction.
Federal Digital Services & AI Product Design
Senior product support for consequential federal systems: clarify ambiguous opportunities, validate user needs, and design AI-enabled digital services that are usable, testable, and implementation-ready.
Senior product design and prototyping support for complex services, AI-enabled workflows, and public-facing digital experiences.
Clarify the problem, map the workflow, and turn ambiguous requirements into focused product direction.
Plan and run user interviews, synthesize findings, and translate research into product requirements.
Journey maps, service blueprints, intake flows, and operational views for complex service environments.
Human-in-the-loop workflows, agent experiences, decision support, and review queues people can trust.
High-fidelity prototypes that test assumptions and de-risk implementation before full build.
Interface specifications, design systems, and engineering-ready product experiences.
One craft—stakes, not sector. Lane A carries the proof-backed depth; Lane B extends the same human-in-the-loop design practice into mission and operational systems.
Lane A — Federal Health & Public Services
The stake is comprehension. A service the public can’t understand hasn’t been delivered.
Public health, benefits and eligibility, patient and provider experience, science and health communications, and public-facing digital services.
Backed by the principal’s career, not the entity’s: NHTSA’s safety web under Section 508 (via UICGS/Bowhead), NIH-adjacent health communications (via Palladian Partners), and Amtrak’s 30M-user booking system. Feedback Loupe is the practice he brings it through.
Lane B — Defense, Mission, Cyber & Federal IT
The stake is trust under load. An operator who doesn’t trust the tool routes around it.
Mission software, operational dashboards, analyst and caseworker workflows, cyber operations, and AI-assisted decision support—systems where clarity, provenance, and operator trust decide whether the tool gets used.
Credibility rests on the principal’s prior environments—defense IT via UICGS/Bowhead and product design at a national-security venture studio (AI/cyber incubation)—not on entity past performance. Positioned at the unclassified/CUI design layer, under cleared primes rather than as one.
Evidence of the principal’s capability—not corporate past performance for Feedback Loupe LLC.
Performed by Chris Mullins as an employee or subcontractor of other firms before founding Feedback Loupe. Employer and client specifics available to teaming partners on request.
Domain overview—federal safety web, national booking, health communications, and civic digital services under institutional constraint.
View domain summary →Section 508, Drupal production surfaces, and regulated consumer safety communications made readable without being made wrong.
View engagement →National passenger rail booking at 30M+ traveler scale—AEM transition, assigned seating, and design system foundation.
View engagement →Agentic civic AI on a state-government mobile channel—governed agents, wedge definition, and stage-gated delivery.
Clearance & access: No active clearance; clean record; CUI-aware. Deeper case narratives are password-protected on this site—available to teaming partners on request.
Focused, senior-level support that moves teams from unclear needs to usable, testable product direction. Method and delivery model: Approach.
Most federal digital work runs on prime contract vehicles. Feedback Loupe joins as a subcontractor or specialist labor category (NAICS 541512, PSC DA01/DD01) on active task orders—the usual way primes staff senior UX, service design, and AI workflow support.
One practitioner spanning health and defense—unified by human-in-the-loop AI design, trust surfaces, and workflow fit under stakes.
From unclear ideas and fragmented stakeholder needs to validated direction and working prototypes.
AI that supports human judgment: review, transparency, and real operational handoffs.
Works directly with engineers and product leaders on implementation-ready UX, not concept slides.
Entity information for teaming conversations, vendor onboarding, and capability review.
Security clearance: No active clearance; clean record; CUI-aware. Feedback Loupe LLC has no corporate past performance—teaming is based on principal capability.
Read-only teaming metadata for capture tools and AI connectors—the same registration facts as this page.
Public HTTPS MCP — entity registration, NAICS/PSC codes, capabilities, and teaming fit. Case studies are not in the connector; contact for deeper proof.
ChatGPT: add the MCP endpoint as a connector, then enable the app in each chat before asking teaming questions. Setup detail and local-dev use (Cursor / Claude Desktop): colophon · llms.txt.
Available for prime teaming, subcontracting, and focused direct engagements across UX research, service design, AI workflow design, and prototyping. On most programs that means joining your team on an existing vehicle as a small-business sub or specialist labor category.