Series Keeping Up With AbbaDox · Product Operations

How Your Roadmap Request Becomes a Shipped Workflow

Scott Yankton on why product operations should chase real customer outcomes instead of becoming a feature factory.

With Scott Yankton, VP of Product & Product Operations Published

For imaging center leaders who request features, and for anyone deciding what to fix first in their workflow.

Read the recap
Jump to a chapter14 chapters
Episode highlights

What you’ll learn in this episode

Why chasing release velocity can hurt quality and value in health tech
How to peel back a pain point with root-cause analysis before building
How Lean Kanban exposes and removes the real bottleneck in a process
How NPS and navigation analytics tell you a feature actually worked
Why moving the dial from sales-led to product-led lets software scale
From the conversation, 20:18

Pain is an onion. Peel it back

Scott on why a center leader should not take a pain point at face value, run, and fix it.

Episode context

The Challenge: Output Is Not the Same as Value

In health tech, teams are pushed to ship features quickly. Chasing output produces crowded roadmaps and software that technically works but does not fully solve the customer’s problem.

For imaging centers, that shows up as disconnected workflows, slow adoption, and tools that add complexity instead of clarity.

As Scott Yankton explains, focusing only on output makes teams busy, not effective. The alternative is to start from customer pain and measure real outcomes.

  1. Pain is an onion: peel it back before building anything.
  2. Test the idea on paper with real users, round after round.
  3. With Lean Kanban, find the bottleneck and contract each step.
  4. After release, measure whether the outcome was delivered.
About this episode

The Solution: Product Operations at AbbaDox

In this episode of Keeping Up With AbbaDox, Scott Yankton, VP of Product & Product Operations, joins host Pierre-Antoine Tricen to explain how AbbaDox guides a product from idea through launch and, critically, through evaluation afterward.

By combining an end-to-end product process with Lean Kanban thinking, the team can find bottlenecks, contract each step, and deliver value faster while keeping quality consistent.

Scott Yankton, VP of Product & Product Operations at AbbaDox
You’ve got this nugget called pain, but it’s like an onion. You need to peel it back.
Scott Yankton VP of Product & Product Operations, AbbaDox
Why your roadmap requests actually land
“What we’re chasing is the delivery of real outcomes, real outcomes that impact income statements and financials for groups. That’s the goal here, not just a feature factory.”

Scott is setting real outcomes against a vendor measuring itself on shipped features. The alternative he sets out is concrete: every initiative starts from a customer pain that gets peeled back to its cause, concepts are tested on paper with real users, round after round, before code exists, and success is judged after launch on NPS, navigation analytics and direct feedback, not on the release note.

Product operations in practice

How AbbaDox Approaches Product Operations

Scott describes product operations as the art and science of guiding a product from ideation to release and analysis.

Put it to work

Take it to your team

Three questions for your next leadership meeting, each with the moment in the episode that answers it.

  1. What is the pain underneath the feature you are asking for?

    Scott calls pain an onion: peel it back to understand it, rather than taking it at face value and running to fix it.

  2. How will you know the change actually worked?

    Delivery is not the finish line. NPS and navigation analytics show whether a release produced the outcome it was meant to.

  3. Are you asking for a one-off fix or a product improvement?

    Turning the dial from sales-led toward product-led keeps software from becoming layer on layer of one-off changes.

Want these answered for your center?

See Product Built Around Real Problems

Discover why imaging centers choose AbbaDox CareFlow, a platform shaped by customer outcomes rather than feature count.