Assembly Required
Introducing Assembly Required: What we write about, why, and when.
Ten years ago, patient engagement/affairs/etc. was mostly about compliance or doing the “right thing.” Check the box. Get patient input for the FDA. Put a patient story in your marketing deck. Keep advocacy groups happy. Show some emotional patient videos at your all-company town hall.
That’s changing. Not everywhere, not fast enough, but it’s changing.
The best companies now understand that patient intelligence, real, structured, queryable patient intelligence, drives business decisions. It informs clinical trial design. It shapes regulatory strategy. It changes how you talk to investors. It determines whether your commercial launch works. It determines the outcomes of patients who need you.
But nobody knows how to do this well yet.
The field is fragmented. Clinical development teams think about patients one way. Medical affairs thinks about them differently. Commercial has their own approach. Regulatory is focused on compliance. Communications is worried about messaging. Data teams are drowning in unstructured quotes. Patient advocacy organizations are doing their thing.
Everyone’s working in silos. And that’s where patient engagement dies - in the gaps between disciplines.
Where The Rubber Meets The Road
The interesting work, the work that actually matters for patients and industry, happens at the intersections:
Where data meets communications - how do you structure patient input so it’s not just quotes in slide decks, but evidence you can query, reference, apply, report on, and build stories around?
Where strategy meets compliance - how do you design patient engagement that’s both legally defensible AND strategically valuable?
Where clinical development meets commercial planning - how do you capture patient intelligence in Phase 2 that informs your launch strategy in year 5?
Where organizational design meets patient outcomes - who owns patient strategy? Where do they sit? What decision rights do they have?
Where bioethics meets business models - when is it appropriate to engage patients? What are you asking them to do? What do they get out of it?
Where creativity meets utility- how do you design experiences that inspire and are indispensable?
These intersections are where patient engagement either becomes strategic intelligence or remains theater.
Most consulting firms pick one discipline. Strategy firms do strategy. Data firms do data. Communications agencies do communications. Compliance consultants do compliance.
Nobody assembles all the pieces.
That’s why we started Assemble Health.
Why We Do This Work
We’ve spent years watching smart people build patient engagement programs that didn’t produce lasting value. Not because they didn’t care. Not because they weren’t trying. But because they were solving one piece of the puzzle without understanding how it connected to everything else.
You can’t fix patient engagement with better advisory boards. Or better data collection. Or better communications. Or better compliance policies. Or better organizational design.
You need all of it. And it has to work together.
The companies that figure this out will have better clinical trials, faster regulatory approvals, more successful launches, and stronger relationships with the patient communities they serve.
How We Work Differently
The model: We do extensive work upfront - calls, thinking, informal advice. We invest in knowing the people and problems before projects exist. We build partnerships and knowledge, not transactions.
Selective clients: We say yes to people who are curious, try hard, stay flexible, are ambitious, and can spar with us. We vet who we work with because our reputation is tied to their approach to patients. We try not to place bad bets.
The unglamorous work: Other firms want sexy, creative, and strategic work - big splashy vision, thought leadership, first‑of‑its‑kind patient workshops, events, and partnership activations. We do that too. But we also do what most firms won’t touch:
Compliance policies that work in practice (not just pass the legal review)
Detailed org models - who reports to whom, actual job descriptions, and the skills required to make the model work
Scientific exchange vs. promotional policies your team can follow
Patient advocacy audits - what you’re actually doing vs. what you think you’re doing
This is infrastructure work. Tedious, detailed, quiet work. Most strategy firms skip it because it’s low-margin and not conference-worthy. But this is what makes strategy WORK.
We do it because you can’t build a patient strategy on broken infrastructure.
Where The Real Thinking Happens
Most of our best thinking doesn’t happen in “billable hours.” (That’s why we don’t work hourly.)
It happens while I’m walking the dog. Packing lunches for my kids. When I’ve had too much coffee, and I’m awake at 2am. When I’m questioning my life choices in the gym.
That’s when the real questions surface:
Why are there so many frameworks? They aren’t working. A new slide template won’t solve a strategic problem.
Why do people keep paying agencies tens of thousands for patient advocacy group mapping when they can do it themselves for a fraction of the cost with tools that exist now?
What would a Patient Avoidable Amendment Lookback actually look like? How much data would I need to prove engaging patients earlier would have prevented that protocol amendment? Can I even get that data?
What is the decision proximity of your patient insights delivery? Are your insights/data actually timed to influence decisions? Or, nah?
Why are there seventeen definitions of “patient engagement” and how is that definitional chaos preventing the field from maturing? Does it even matter what we call it?
Why do patient advocacy skills need to change entirely if organizations want strategic partners instead of compliance checkboxes?
How do corporate campaigns actually shape patient perception and what does that mean for authentic engagement vs. manufactured narratives?
Why do patient communications treat “patient voice” like branding instead of strategic intelligence?
What does executive communications about patients signal about actual organizational priorities?
Most of this never makes it into final deliverables. These are the infrastructure questions underneath project questions we wrestle with so the more visible work can land cleanly.
This is where we’re putting that thinking.
What You’ll Find
Not a tutorial newsletter. We’re not teaching you how to run an advisory board. There are plenty of resources for that.
This is strategic thinking that shapes how we approach client work - and how the field should think about patient intelligence:
And, specific strategic problems we’re solving. Anonymized, but real. The messy middle of structuring patient input so it’s usable. Building measurement systems that don’t require PhDs to understand. Communicating patient intelligence to boards and investors. Hiring for roles that don’t exist yet.
Assembly Required
Patient intelligence isn’t just a data problem. It’s a systems problem, design problem, communications problem, business model problem, ethics problem, organizational problem.
The best client work is multidisciplinary. We’re not just building patient advocacy strategy - we’re connecting it to regulatory timeline, commercial narrative, corporate communications, organizational capacity, competitive positioning, investor story, and executive messaging.
Who This Is For
Biotech founders - trying to figure out if you need patient engagement or if it’s just something investors expect you to say.
Pharma executives - you know your patient experience function isn’t delivering strategic value, but you’re not sure how to fix it.
Patient advocacy leaders - tired of being treated like a compliance checkbox, want to demonstrate real impact.
Investors - trying to evaluate whether a company’s patient strategy is real or window dressing.
Strategists and consultants - doing this work and want to think bigger about where the field is going.
Frequency and Format
We’ll publish when we have something worth saying. Sometimes weekly. Sometimes, when a client conversation surfaces a question we can’t stop thinking about. Sometimes, when we read something that makes us want to respond.
Posts vary. Some are short and specific. Some long and exploratory (here’s why this whole approach is wrong). Some structured arguments. And some messy, in-progress thinking as we assemble ideas sparked from client learnings, industry interactions, and what we’re seeing/inspired by in the world into a more coherent perspective/sharper point of view.