The setting
connects patients, outpatient mental health providers, and health insurers. gives health plans a network of credentialed clinicians who give outpatient mental health care, plus referral links and ways to measure how the network performs.
Provider guidance must change coding behavior without being mistaken for a clinical ruling.
The payer needs auditable correction patterns, while providers need feedback they can understand and trust.
Who you’d be doing this for
“My compliance team keeps asking what changed after the adjustments, and I don’t have a clean answer.”
Margaux Stewart · Behavioral Health Network Executive · a character in this brief
Oversees coding integrity and network performance for a health plan using the clinician network.
What is at stake
Repeat coding adjustments are rising among providers who say they followed earlier feedback. You must choose how much explanation providers receive when each added detail increases review risk.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- payer auditability vs provider trust
- actionable guidance vs clinical boundaries
- speed to commitment vs verified evidence
- shared product pattern vs payer-specific response
Why Headway
Provider feedback sits between the clinician experience and the coding integrity health plans expect from the network.
Written with these in mind
Not your kind of problem? 104 more at Headway, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Headway. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Senior Product Designer, New Channels · no longer posted
- You prototype and test ideas quickly with Claude Code, Cursor, or your AI tool of choice.
- Designers use Claude Code and Cursor to prototype, ideate, and ship improvements to our codebase.
- Principal Product Designer, Payer · no longer posted
- You'll lead the design vision and execution for how we support clinical excellence, ensure coding accuracy, and provide meaningful feedback to providers to influence their behavior—all while maintaining the provider experience that makes Headway different.
- Prototype with Claude Code/Cursor and MagicPattern to build and iterate on the flows and Information Architecture.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these turns on committing to a deal before it checks out.
Members in six priority markets are offered clinicians who later cannot take their coverage or referral.
You must weigh a durable access commitment against reimbursement cost and provider trust.
Members are booking specialists the agent describes as covered, then learning the clinic will not accept their plan.
You must weigh a faster path to care against the risk of making a coverage promise from conflicting records.
Nine of 16 release-test members described incompatible sharing scopes.
You have to weigh clinician continuity against consent that members can genuinely explain.
The same setting, from another role
Each is set around Headway’s Headway for Payers, written for a different role. They’re separate briefs, not the same scenario.
Five of eight payer deals contain requests beyond approved proposal language.
You decide whether AI drafts those requests as marked terms or leaves them as questions for the seller.
Six qualified discussions lack agreement on who funds referrals from health systems.
You must weigh a payer's demand for predictable participation against health systems' refusal to guarantee patient volumes.
A payer's expansion now depends on three years of exclusivity across three states.
You must weigh guaranteed contribution against blocked deals while refusing commitments the network cannot substantiate.
Other problems with a similar purpose
In each of these, as in this one, the aim is to make complicated, high-stakes systems feel simple to navigate without quietly removing the protections people depend on.
Cross-surface tasks take a median of 7.4 navigation actions, and support data ties the confusion to delayed production changes.
You have to decide how developers move between workflows, evaluations, connections and deployed agents before deep links and permissions migrate and set that path.
Admins stall at permission validation and destination selection, and many misread what happens when a connection is committed.
You have to settle the interaction model now, because changing it after rollout is costly.
In audit samples, interviewers saw context that some customers do not permit, and the migration runs one way.
You have to keep scorecards structured and auditable while narrowing what interviewers see.
