FAQ
Useful answers before we get into the details.
Here are a few things teams often want to understand before starting a health product conversation.
What kinds of projects are a good fit?
We are a fit when a team is making a health or benefits service easier to understand and use—especially when the journey spans multiple steps, teams, or channels. We can help shape an early idea or improve an existing product.
What happens during discovery?
We align on the audience, service context, constraints, and decisions that need to be made. Depending on the question, discovery may include stakeholder conversations, journey mapping, workflow review, or a focused product plan.
How do you approach accessibility?
We bring accessibility into requirements, content, prototyping, implementation, and quality review. We consider keyboard operation, semantics, contrast, responsive layouts, plain language, and relevant assistive technology and user variation.
What does privacy-conscious design mean here?
We minimize unnecessary data collection in product flows, make data needs understandable, and consider access, retention, and exposure risks during design. We do not claim that a design alone makes a product compliant or secure.
Can you hand work off to our internal team?
Yes. We document design decisions, component behavior, content patterns, technical assumptions, and open questions so your team can continue with clarity.
How long does a project take?
Timing depends on the product question, review needs, existing platform, and team availability. A focused sprint may be shorter than a platform build; we agree scope and milestones before work begins.
Can you work alongside our internal team?
Yes. We can join an established product team, collaborate with service and engineering partners, and share working artifacts as we go. We aim to make the team more capable rather than create a handoff dependency.
Do you support content as well as interface design?
Yes. Plain-language content and interaction design belong together. We can help structure information, explain eligibility or next steps, and create reusable editorial patterns.
What happens after launch?
We can support a measured release, review feedback and support signals, prioritize improvements, and work with your team on the next iteration. Ongoing support can be arranged as an embedded partnership.
How do I request support?
Use the Support page to choose a project, client, accessibility, or privacy route. We aim to acknowledge new messages within two business days. Do not send passwords or personal health information.
Do you guarantee a particular outcome?
No. We set useful measures with the team and report what testing or product evidence shows. Outcomes depend on context, implementation, adoption, and other factors beyond a design or engineering engagement.
Still wondering?