Skip to content
Nerdy beta

From Project Management to Product Strategy

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 anyway. 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.

Our engagement ran several months of part-time collaboration sessions. Anne, our collaborator on the ground, started with roles: carving out clear ownership and responsibilities among the product leaders, so decisions had a home. From there the team shifted to iterative delivery with a structured planning cadence and disciplined prioritization, replacing big upfront scoping with outcomes over outputs and outcome-based roadmapping. Engineers joined discovery early, so the people making the promises were the people shaping the work. The Impact-Outcome Model gave everyone the same question to ask of any initiative: what measurable change is this supposed to create?

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. 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 making promises the team had actually shaped.

Resources