Software Delivery Current-State Diagnostic
A compact assessment of the software-delivery system, its most important friction points, and the priorities that should guide the next 90 days.
- Best suited for
- Small and medium technology companies with broad or poorly defined delivery concerns.
- Typical duration
- One week
- Primary outcome
- A clear view of the current state and a prioritized direction for improvement.
When this is useful#
This diagnostic is designed for organizations that can see signs of difficulty but do not yet know what kind of intervention they need.
Those signs may include:
- Delivery becoming slower or less predictable
- Recurring coordination problems
- Unclear ownership
- Too much work in progress
- Repeated operational interruptions
- Technical and organizational concerns becoming entangled
- Leadership receiving conflicting explanations of what is wrong
- Improvement initiatives being proposed without a shared diagnosis
The objective is not to evaluate every team, process, or technical decision in detail. It is to identify the small number of conditions that most strongly shape the current performance of the software-development system.
What the diagnostic examines#
Depending on the organization and the evidence available, the review may examine:
- How work enters and moves through the delivery system
- Where decisions are made and delayed
- Ownership and responsibility boundaries
- Coordination between product, engineering, architecture, and leadership
- Recurring interruptions and escalation patterns
- Delivery constraints and work-in-progress pressure
- Technical conditions affecting organizational performance
- Organizational conditions affecting technical work
- Existing improvement initiatives and their underlying assumptions
How the engagement works#
The diagnostic normally combines:
- A brief initial questionnaire
- A 60–90 minute leadership conversation
- Two to four focused team or stakeholder interviews
- A lightweight review of relevant evidence
- Analysis and synthesis
- A final findings and priorities conversation
The evidence review may include selected planning artifacts, workflow information, delivery indicators, architectural material, organizational documentation, or other sources relevant to the concerns being examined.
The process is intentionally compact. It is designed to identify direction rather than produce an exhaustive audit.
What you receive#
The principal deliverable is a Current-State and Priorities Brief, containing:
- A concise description of the current software-delivery system
- The most important findings
- The underlying dynamics connecting those findings
- A prioritized map of concerns
- Recommended direction for the next 90 days
- Questions or risks that require further investigation
- A recommendation regarding the appropriate next level of support
The result may indicate that the organization should address a focused delivery concern, clarify ownership, improve a specific operating mechanism, or undertake a deeper diagnostic.
It may also show that the apparent delivery problem is fundamentally a governance problem.
Relationship to the Scaling Governance Diagnostic#
The Current-State Diagnostic is not a shortened version of the Scaling Governance Diagnostic.
It is broader in its initial scope and is intended for organizations whose central problem has not yet been identified.
When the evidence shows that the primary constraints involve decision authority, founder or executive dependency, governance compression, or structural coordination problems during growth, the deeper four-week diagnostic may be the appropriate next step.
That recommendation is made only when the findings support it.
Start with a conversation
If one of these situations resembles what your organization is facing, write to me with a brief description of the problem.