WORK WITH PDSL
Examine the system behind the problem.
PDSL works with product-development teams when the formal process no longer explains what is actually happening—and the organization needs a clearer view of its decisions, risks, evidence, and constraints.
THE PREMISE
The problem may be visible.
The system producing it may not be.
A delayed project, a recurring quality issue, or an inconclusive review can appear to be an isolated failure. Often it is evidence of something deeper: unclear authority, disconnected decisions, normalized assumptions, or a development system that is no longer questioning itself.
PDSL does not begin with a prescribed framework. It begins by examining how the organization understands the problem and how its current system has responded to it.
CONDITIONS WORTH EXAMINING
Does any of this
feel familiar?
- 01
The formal development process and the actual work have separated.
- 02
Reviews occur, but critical assumptions remain unchallenged.
- 03
Teams generate evidence without reaching defensible decisions.
- 04
Risk management exists as documentation but does not shape the work.
- 05
Quality problems emerge late because earlier signals were normalized.
- 06
Business pressure and product integrity are treated as opposing forces.
- 07
Responsibility exists, but decision authority remains unclear.
HOW PDSL WORKS
Inquiry before
prescription.
Examine the system
Look beyond the process map to understand the decisions, interfaces, incentives, and constraints shaping the work.
Make the reasoning visible
Surface assumptions, evidence, trade-offs, ownership, and the questions the organization has stopped asking.
Define the actual problem
Determine whether the condition is technical, organizational, systemic—or an interaction among all three.
Strengthen the way forward
Develop an intervention appropriate to the situation and leave the organization with stronger reasoning, not dependence on the consultant.
THE BOUNDARY
PDSL helps an organization see its system more clearly, make the decision in front of it explicit, and strengthen the conditions under which good work can happen.
The objective is not to manufacture agreement or install a generic methodology. It is to create enough clarity that the organization can act deliberately—and understand the trade-offs it is accepting.
START A CONVERSATION