Design & Experience
We design around the users you serve.
Every interface starts with the same question: who is this for, and what do they need to get done? From there we shape something the people you serve can use.
Trusted by public-good organizations
- City of Arlington Virginia logo
- Americares logo
- Arlington Public Schools logo
- City of Ashville logo
- Bond Dealers of America logo
- CVSA logo
- DCHS logo
- DrAxe.com logo
- George Mason University logo
- MACPAC logo
- MedPac logo
- Motorola logo
- Military Womens Memorial logo
- National Housing Conference logo
- National Industries for the Blind logo
- National Science Foundation logo
- Oliff Law llogo
- PRB logo
- SFI logo
- Wesley Seminary logo
Research
We learn the room before we move a thing.
Before we design anything, we get specific about who uses the site and what they are trying to get done on a Tuesday morning. We sit down with the program staff who run it, the editors who keep it current, and the audiences who depend on it.
What it covers
Stakeholder and audience interviews, content audits, analytics review, and a competitive scan of the organizations doing similar work.
How we get there
Structured conversations and desk research. Findings get synthesized into a single, readable brief your team can act on.
What it looks like
- Research brief
- Audience personas
- Audit + analytics review
- Competitive analysis
Information architecture
Your users find what they came for, fast.
We shape the site around how your audience searches, so the structure matches the way they think. Someone looking for one thing, a form, a deadline, or a program they qualify for, lands on it in a few clicks, straight to the page they came for.
What it covers
Sitemap design, content modeling, taxonomy work, URL strategy, and editorial roles are shaped around how people search, so the path to what they need is the obvious one.
How we get there
We map what you have, draft what it could be, and pressure-test the structure with real people looking for real things, all before a single page gets designed.
What it looks like
- Sitemap
- Content model
- Taxonomy + tagging plan
- Editorial role map
wireframes & prototypes
Great design starts with a carefully drafted blueprint.
Every key page and flow gets drafted in low fidelity, the rough working version of the site you can click-through and interact with. It is the clearest place to make decisions together, while the structure is still soft enough to mold.
What it covers
Low-fidelity wireframes for every primary template, clickable prototypes for the critical flows, and reviews built into the schedule, so feedback lands on the calendar instead of an email at 11 pm.
How we get there
We work in real content (if available) from week one at phone and desktop sizes. Stakeholders can see how the site works before anyone argues about a shade of blue.
What it looks like
- Responsive wireframes
- Clickable prototype
- Annotated user flows
- Review notes + sign-off
UI & design systems
One system, so your brand stays consistent across every page.
Type ramps, color tokens, spacing scales, component states, responsive layouts, and motion are defined once and applied everywhere. One visual language for your entire site, documented as a system, that aligns with your organization’s brand identity.
What it covers
Type ramps, color tokens, spacing scales, component states, and motion specs, all delivered in Figma and in code so the build follows one set of rules from the start.
How we get there
We start with the smallest pieces (tokens, primitives) and compose upward. Every screen in the site speaks the same alphabet.
What it looks like
- Design tokens
- Component library
- Motion specs
- Usage documentation
Accessibility
Accessible from the first sketch, through the final audit.
For the public-good organizations we serve, accessibility is designed in from the first sketch, built to meet WCAG AA and Section 508.
What it covers
Color and contrast systems, focus order, keyboard navigation, screen reader semantics, and assistive-tech testing, all validated against the standards your funders and audits require.
How we get there
Designers and developers work from the same checklist from day one. When the audit arrives, the work is already done.
What it looks like
- Accessibility audit
- Contrast + focus system
- Screen-reader QA notes
- VPAT-ready report
Selected work
Digital worlds we've shaped.
A short list of recent engagements with public-good organizations, each one doing work worth supporting.
Let's talk