Skip to content
Nerdy beta

From Project Management to Product Strategy

Add to Space
 Product Outcomes Case Study

The Situation

Parallax, a growing SaaS company, was running its product like an agency runs client work, because that’s where the team came from. Every initiative got scoped up front and executed waterfall-style, and the timelines were regularly missed. Requirements stayed vague, priorities stayed unclear, and the roadmap belonged to whichever customer need was loudest that week rather than to any strategic vision. Sales and customer success had stopped trusting delivery commitments, which is the quiet failure mode of project thinking: the dates exist to create confidence, and they were doing the opposite.

What We Did

Our engagement ran several months of part-time collaboration sessions. Our collaborator on the ground started with roles: carving out clear ownership and responsibilities among the product leaders, so decisions had a home.

“[Our collaborator] really helped us carve out roles & responsibilities amongst product leaders.”

With ownership settled, the team replaced big upfront scoping with outcomes over outputs and outcome-based roadmapping. The Impact-Outcome Model gave everyone the same question to ask of any initiative: what measurable change is this supposed to create? The rest of the shift ran through a handful of connected changes:

  • From waterfall to iterative delivery. Smaller, more manageable increments instead of planning everything upfront, so the team could correct course while it still mattered.
  • A structured planning cadence. Predictable sprint cycles, a groomed backlog, and disciplined prioritization that tied the work to strategic goals instead of the loudest voice.
  • Engineers in discovery. Developers joined the planning cycle early, so technical feasibility shaped the plan and the people making the promises were the people shaping the work.
  • Visibility that rebuilt trust. Everyone could see what was being worked on, when it would land, and why decisions were made. Confidence across departments replaced guesswork.

Change like this holds or slips on coaching, and the coaching was constant: meeting people where they were, adapting to personal strengths and styles, and reinforcing that the team was on track rather than piling on.

“If we were running into issues or hiccups, there was zero hesitation to reach out [to our collaborator]. She was always willing to listen and help us come up with solutions.”

The Results

The results were the kind sales can repeat to customers: 90% on-time delivery of committed timelines, from a baseline of missing most of them, and features shipping in weeks instead of months. Faster releases meant faster customer feedback, and faster feedback fed the next round of priorities.

The deeper result doesn’t fit on a dashboard. Sales, customer success, and engineering now trust the same timelines, and the product team stopped acting like order-takers and started acting like stewards — making proactive decisions and taking pride in the work.

“We’re more collaborative with more ownership than ever.”

The line we kept from the retro: “It feels like we’re finally operating like a real SaaS product team.”

Ninety percent on-time didn’t come from better estimates. It came from commitments the people doing the work helped shape before anyone promised a date.

Resources