Brent Lavin

The problem, they say, is that no single function owns the whole case.

• Specialized teams optimize within their own lanes, and the program drifts one reasonable decision at a time until the approved product no longer matches the business originally imagined.
• Guarding the business case means weighing those trade-offs through the customer’s lens and making their consequences clear to the business.

Lavin lists the questions that need to be answered together: whether an extra function is worth its cost, whether the business model is capital, disposables, or a mix, how large the clinical trial needs to be, what the pricing guardrails are, and what the ideal account profile is—and whether that segment is large enough. They end by asking who owns the business case in a program.

Read original

The product owner’s hardest job is to separate signal from noise and synthesize diverse input into one set of product attributes. They call that synthesis part science—deciding which needs are universal, segment-specific, individual preference, or loud but commercially shallow—and part art: having the conviction to converge and say what is being built, for whom, and why.

A physician in a German university hospital and a physician in a US ambulatory surgery center can perform the same procedure and disagree about what better looks like.

• Both can be right from where they stand, but a company can make only one product.
• Lavin argues that optionality—through configurability, extra SKUs, or letting geography decide—is sometimes right, but often amounts to avoidance.
• It also compounds into more design inputs, regulatory submissions, clinical evidence, and manufacturing complexity.
• In a shared State of Medtech clip with Omar Khateeb, they connect the point to the line that designing for everybody ends up designing for nobody.

Read original · Original 2

Responding to a Harvard Business Review article on bridging, they summarize three bridger activities: curate the right partners, translate across different languages and priorities, and integrate disparate efforts into coordinated execution.

• They say their medtech career has involved doing exactly that among specialized teams, global partners, and acquisitions—translating between physicians, engineers, regulators, payers, hospital procurement, and investors.
• Their conclusion: technology is rarely the problem; coordination is.

Lavin points to connecting Asia design centers with US commercial teams, taking a whiteboard drawing to market within 18 months of concept, and leading commercial integration on four buy-side M&A transactions.

Read original

The design and manufacturing were genuinely new, but market conditions shifted during development.

• Reimbursement fell faster than usual, competitors started fighting on price, and supply-chain disruption raised costs.
• The team kept using a launch plan built on a pricing assumption that had stopped being true two years earlier, while sunk costs made stopping unattractive.
• Lavin asks what the kill criteria are and who is allowed to call it.

Market pricing dropped by more than 10% for three straight years while the program continued. Lavin treats that as a test of whether a company can revise or stop a program when the commercial evidence changes, not just whether it can get regulatory approval.

Read original

In a career reflection, they describe leaving GE and family in Milwaukee for a smaller, more nimble company in Phoenix, later acquired, and then watching the industry shift toward larger strategics, heavier regulation, more employed physicians, and reimbursement pressure.

• They argue that large strategics are pursuing less organic innovation, new product development is more complex, and funding is harder.
• Ironwood Medtech Partners is meant to fill that gap by helping early-stage companies build commercial logic into innovation and turn technologies into viable businesses.

Lavin says Ironwood Medtech Partners aims to bring product catalyst skills to early-stage companies, connecting clinical excellence to commercial success. The move shifts their focus from corporate medtech roles to an advisory practice centered on the commercial case from the beginning.

The clearest evolution in the material: Lavin moves from large-company product management to founding a practice aimed at early-stage medtech.

Read original · Original 2 · Original 3

Lavin defines guarding the business case as a core product-management job: integrating engineering, clinical, regulatory, and commercial choices into one coherent picture.

• The post lists decisions such as whether a product is capital, disposable, or mixed; the size of a clinical trial; pricing guardrails; and the ideal account profile.
• Without one owner for those tradeoffs, specialized teams optimize their own lanes, and the approved product can drift from the business originally imagined.

For brands planning a campaign

Use it to diagnose an early-stage medtech pipeline: identify who owns the integrated business case, list tradeoffs without an owner, and add a launch-readiness checkpoint to test the original commercial assumptions.

Lavin describes talking with thousands of physicians and valuing their strongly held beliefs, then argues that the product owner's hardest job is separating signal from noise.

• A physician in a German university hospital and one in a US ambulatory surgery center may want different things, and both can be right, but a company can only make one product.
• Lavin calls the synthesis part science and part art, and warns that optionality—such as configurable designs, extra SKUs, or letting geography decide—is often a hard decision avoided, compounding into more inputs, submissions, evidence, and complexity.

For brands planning a campaign

Use it to structure physician advisory work: define which needs are universal, segment-specific, or individual; require a documented rationale for what is in and out; and treat added configurability as a cost to justify.

A product was approved and then went nowhere.

• Lavin describes building something new in a lookalike segment, then watching reimbursement fall, competitors fight on price, and supply-chain costs rise.
• When market pricing dropped by more than 10% for three straight years, sunk costs made the team unwilling to stop.
• The launch plan still relied on a pricing assumption that had stopped being true two years earlier.
• Lavin asks what the kill criteria are and who is allowed to call it.

For brands planning a campaign

Build kill criteria and assumption-review triggers into the innovation plan. Assign someone accountable who can stop or reshape the program before sunk costs override new market evidence.

Lavin connects an HBR article's bridging concept to 20 years of medtech work: curating partners, translating across different priorities, and integrating execution.

• Examples include connecting Asia design centers with US commercial teams, taking a whiteboard drawing to market within 18 months of concept, and leading commercial integration on four buy-side M&A transactions.
• Their conclusion: technology is rarely the problem; coordination is.

For brands planning a campaign

In a commercial-integration plan, explicitly assign the role that bridges R&D, clinical, regulatory, and commercial teams, with milestones for partner selection, translating priorities, and coordinated execution.

In a post about a State of Medtech conversation with Omar Khateeb, Lavin repeats the idea that designing for everybody ends up designing for nobody. The post says the clip covers part of their origin story and the need for good product management: making trade-off decisions and knowing who owns priority decisions with customer and internal context.

For brands planning a campaign

For deeper due diligence, use the referenced conversation as an interview lead and verify the details. Ask who owns priority decisions in the target organization, using the quoted question as a prompt.

A 15-year reflection on moving to Arizona for a job at CR Bard after leaving GE.

• Lavin says the goal was to join a smaller, more nimble organization, bring global product-management skills to a US-centric company, and lead teams.
• The post describes CR Bard being bought by BD, changes after 2020, and Lavin leaving corporate medtech to start Ironwood Medtech Partners.
• There, they focus on helping early-stage companies build commercial logic into medtech innovation and turn technologies into viable businesses.

For brands planning a campaign

Use it to frame an engagement conversation: the stated fit is early-stage medtech that needs commercial logic built into innovation, not a pure technology or R&D review.

The failure they identify most often is that no single function owns the whole case.

• Engineering optimizes the design, regulatory the approval, clinical the trial, and sales the launch.
• Each makes rational calls in its own lane, while nobody integrates the trade-offs through the customer’s lens.
• The program then drifts one reasonable decision at a time until the approved product no longer matches the business originally imagined.
• The questions they say they evaluate are whether an added function is worth its cost, whether the business model is capital, disposables, or a mix, how large the clinical trial needs to be, what the pricing guardrails are, and what the ideal account-targeting profile looks like and whether that segment is large enough.

The argument takes the form of a short list of business-case questions, ending with a direct question to the reader: who owns the business case in their program?

For brands planning a campaign

For an early-stage medtech team trying to build commercial logic into its innovation pipeline, the test is whether Lavin can hold the full business case, not just one function’s slice of it. Ask them to identify where ownership is split and what could drift as a result.

Examples: Source 1

Physicians in different health systems, countries, and payment environments can perform the same procedure and disagree about what “better” means.

• Both can be right from where they stand, but only one product can be made.
• They call synthesis part science—identifying which needs are universal, segment-specific, or individual preferences dressed up as requirements, and which signals are loud but commercially shallow—and part art: having the conviction to state what is being built, for whom, in which settings, and why.
• Optionality—making a product configurable, offering two SKUs, or letting geography decide—is sometimes the right answer, but often a hard decision avoided.
• They argue that every increment of optionality compounds into more design inputs, regulatory submissions, clinical evidence, and manufacturing complexity, while pulling the product further from its original value proposition.
• The same convergence argument appears in a clip they shared from a State of Medtech conversation, built around the line “when you design for everybody, you end up designing for nobody.”

The synthesis argument appears in a structured text post contrasting product attributes with optionality, while the State of Medtech clip gives the trade-off a spoken form.

For brands planning a campaign

A brand assessing Lavin for a product management role should test whether they can make and document a convergence decision, not just gather input. A useful brief asks them to take a real set of conflicting physician requirements and show the call, the rationale, and how they would hold the line when the next interview produces another “but what about…”.

Examples: Source 1 · Source 2

Responding to a Harvard Business Review piece that named “bridging” as what lets great innovations scale, they list three things bridgers do: curate the right partners, translate across different languages and priorities, and integrate disparate efforts into coordinated execution.

• They say they have spent a career doing exactly that among specialized teams, global partners, and acquisitions, translating between physicians, engineers, regulators, payers, hospital procurement, and investors.
• Their conclusion is blunt: the technology is rarely the problem; coordination is.
• The experience they cite includes connecting Asia design centers with US commercial teams, taking a whiteboard drawing to market within 18 months of concept, and leading commercial integration on four buy-side M&A transactions.

Ask for the employers, products, and deal parties behind the career examples.

For brands planning a campaign

For a company whose clinical, engineering, and commercial groups are not talking to each other, ask Lavin which boundary is breaking the program and what integration they would put in place. Ask for a specific collaboration breakdown and what they did about it.

Examples: Source 1

The design and manufacturing were genuinely new, but the market moved during development: reimbursement fell faster than usual, competitors started battling on price, and supply-chain disruption pushed costs up quickly.

• Market pricing dropped more than 10% three years in a row, while a launch plan built on a pricing assumption that had stopped being true two years earlier stayed in use because sunk cost made pulling the plug unattractive.
• They end with the question the post wants programs to answer up front: what are your kill criteria, and who is allowed to call them?
• The story applies the discipline of guarding the business case to market conditions that change after approval.

For brands planning a campaign

This is the strongest material for due diligence or market-risk assessment. Ask Lavin to define kill criteria, the market assumptions a plan depends on, and the review cadence and authority that would stop a program before sunk cost overrides market signals.

Examples: Source 1

They describe an industry that has moved from a fluid middle class of product-led companies toward larger strategics, heavier regulation, higher physician employment, and reimbursement pressure.

• With large strategics pursuing less organic innovation, new product development programs more complex than ever, and funding harder to get, they left corporate medtech to start Ironwood Medtech Partners.
• There, they say, they work with early-stage companies to build commercial logic into medtech innovation and turn technologies into viable businesses.

For brands planning a campaign

The industry read provides context for Lavin’s positioning: their work targets early-stage companies that need commercial logic built into development, not large corporate programs. Test whether the company’s stage and problem match that focus, and ask what “not necessarily bad…just different” means for its specific reimbursement and funding picture.

Examples: Source 1

Lavin borrows outside framing where it fits, quoting Harvard Business Review on bridging and sharing a clip from Omar Khateeb’s State of Medtech podcast.

• They mix professional content with personal reflection on family, church, and living with an autoimmune disease.
• The recurring move is to name the decision a team is avoiding, then ask who is accountable for it.

For brands planning a campaign

A brand considering co-created content or a commissioned piece gets a discussion-driven format: a clear claim, a framework of questions, and an invitation for the audience to answer. Third-party references give the material a research hook rather than a purely personal one.

Examples: Source 1 · Source 2 · Source 3 · Source 4 · Source 5 · Source 6

They describe their role as protecting the business case and connecting engineering, clinical, regulatory and commercial teams. They partner with physicians, engineers, regulators, payers, hospital procurement teams and investors.

View example

They wanted to join a smaller, more nimble organization, bring global product management skills to a US-centric company and lead teams. They describe spending at least seven years there.

View example

The post places this acquisition inside their own career timeline rather than describing a separate commercial relationship.

View example

They describe the move as a shift from a large employer to a smaller organization.

View example

They use the article’s three bridger behaviors to frame their career and the work of Ironwood Medtech Partners. The post links to the article.

View example

View example

Belkin focuses on physician workforce planning as a proactive discipline rather than a reactive one, and on burnout as a leading indicator of turnover. They make the same kind of ownership argument for the medtech business case, asking who integrates engineering, clinical, regulatory, and commercial trade-offs.

Belkin writes from the healthcare delivery and clinical workforce side, covering staffing models, burnout, retention, and patient access. Lavin writes from the medical device and product development side, covering commercial logic, product attributes, and launch assumptions.

Read original · Original 2

Omar uses a cost-and-morale framing for prior authorization and administrative work, arguing that the fastest return comes from taking admin work off clinicians. Lavin uses a business-case framing for medtech programs, arguing that one owner must connect commercial consequences to engineering, clinical, and regulatory choices.

Omar writes about AI and administrative automation inside health systems, including prior authorization, staffing economics, and ROI from deployed tools. Lavin writes about medtech product management and early-stage device commercialization, not AI deployment or health-system operations.

Read original · Original 2

Bham tracks psychedelic and radiopharmaceutical developments through regulatory, manufacturing, reimbursement, and market-access questions. Lavin tracks medtech programs through business-case ownership, physician-input synthesis, pricing assumptions, and kill criteria.

Bham covers pharmaceutical and radiopharmaceutical modalities, including trial replication, isotope supply, regulatory strategy, and market access. Lavin covers medical devices and product management inside device companies, with a focus on commercial logic during development.

Read original · Original 2

The posts argue that healthcare organizations should forecast demand by service line, track retirement and attrition, and build clinician pipelines before coverage gaps become urgent.

• They also connect physician burnout to turnover, specialty instability, and flexible staffing models.
• If the buyer needs to assess how a commercial plan depends on physician availability, retention, or care-delivery capacity, Belkin's posts speak directly to that decision.

The tradeoff is scope.

• Brent Lavin's posts do not address medical-device product management, product-attribute trade-offs, reimbursement assumptions for a new device, clinical-trial design, or the cross-functional business case they describe.
• Buyers who need those device-commercialization decisions should view Belkin as a workforce-strategy alternative, not a direct substitute for product-management advice.

Examples: Source 1 · Source 2

The posts frame the choice between AI that increases health-system revenue and AI that saves society money.

• They break down prior authorization as both a cost and morale problem, citing an employee-cost comparison and focusing on removing administrative work from clinicians.
• For buyers deciding which AI investment a hospital will adopt and how to make the ROI legible, these posts are closer to the decision than Lavin's product-business-case posts.

The tradeoff is that this is not device or product-management advice.

• Brent Lavin's posts do not cover early-stage medtech pipeline decisions, physician-input synthesis for product attributes, regulatory submissions, manufacturing complexity, or launch-plan assumptions.
• Buyers deciding what product to build and how to align the commercial case across engineering, clinical, regulatory, and commercial functions should turn to Lavin's posts.

Examples: Source 1 · Source 2

The posts analyze clinical replication, treatment-center capacity, monitoring and reimbursement requirements, isotope supply and manufacturing strategy, and the need for regulatory, CMC, clinical, and access narratives to describe the same source of value. Companies weighing an investment or access strategy in those areas will find these posts closer to their decision than a device-focused product-management profile.

The tradeoff is relevance to medtech device commercialization.

• Brent Lavin's posts do not address device product attributes, early-stage device commercial logic, cross-functional product ownership, or launch decisions for a new device.
• Buyers seeking help integrating commercial logic into a device innovation pipeline should use Bham only if the pipeline is pharmaceutical or radiopharma in nature, or the need is specifically for market-access narrative work in those sectors.

Examples: Source 1 · Source 2