Choose the method after you understand the work.

Define the problem

A familiar delivery framework can provide a useful starting point. It cannot by itself decide how a particular initiative should balance learning, stability, speed, and organizational consequences. The design problem is to make those choices explicit.

Identify parties and interests

Bring the sponsor, delivery leads, operational owners, and affected service users into the framing. Their tolerance for change may differ because they carry different consequences. Identify who can agree a tradeoff across those interests.

Separate evidence from assumptions

The evidence below establishes what the archive argues. It does not establish the circumstances of a particular client, prove an obligation was met, or demonstrate a violation.

Supported by evidence: The essay argues for selecting a delivery approach in relation to the initiative and its constraints. Its image-only criteria table is not reproduced.
“Governance is dead, long live governance” — Paragraph beginning “To balance customer value”.
Supported by evidence: The essay connects incremental work, learning, and leadership with business outcomes.
When did AGILE become a “Four Letter Word"? — Improvement, Iterations, and Leadership.
Supported by evidence: The essay distinguishes frequent application changes from more rigorous underlying infrastructure changes.
Simplifying SecDevOps 1 Day at a Time — Key Concepts.

Assumptions to test

Different parts of the work may need different feedback and approval cycles.
A familiar framework may be carrying assumptions that do not fit this situation.

Identify obligations and constraints

Establish the real dependencies and approval requirements. Separate change that is inexpensive to reverse from change that affects shared infrastructure or a long-lived commitment. The unavailable criteria diagram in the source is not a basis for a prescribed scoring model here.

Consider competing interpretations

The framework may be appropriate, with poorly chosen decision points.
Different parts of the initiative may need different management arrangements.

Identify the missing evidence

The archive does not contain the client-specific records needed to choose between these interpretations. For an actual engagement, the evidence request would include:

The decisions and approvals currently required to move work forward.
Examples of delay, rework, and useful early feedback.
The consequences and reversibility of proposed changes.

Documentation not produced: Relevant records are not present in the material reviewed. That does not establish that they do not exist.
Unable to determine: The available material does not resolve these questions:

Which decisions can be delegated and which must be retained?
What would show that the cost of governance is justified by the decisions it improves?

Develop alternatives and weigh the consequences

Adapt the present method

Keep familiar working practices while changing the decision points, measures, and responsibilities that are causing friction.

Tradeoff: Continuity reduces disruption, but inherited assumptions may remain.

Separate distinct types of work

Use shorter learning cycles where change is reversible and explicit review where shared dependencies make change consequential.

Tradeoff: A mixed approach requires clear interfaces and can increase coordination effort.

Define the possible contractual engagement

A delivery-design engagement can define the governing constraints, compare workable management alternatives, and recommend decision rights, feedback measures, and a staged implementation plan.

See how a focused engagement could be structured →

Original source material

This is a new synthesis. Dates below belong to the original sources, rather than this interpretation. The source wording, historical claims, and images have not been republished wholesale.

“Governance is dead, long live governance” — original on LinkedInOriginally published 2025-01-03. Editorial review: Historical and attributed claims need verification; the 11-criteria table is image-only, unavailable locally; do not reconstruct its contents.
When did AGILE become a “Four Letter Word"? — original on LinkedInOriginally published 2015-06-04. Editorial review: Historical meetup reference and order-of-magnitude productivity suggestion need verification; metaphorical argument, not measured evidence.
Simplifying SecDevOps 1 Day at a Time — original on LinkedInOriginally published 2024-12-19. Editorial review: Automation consistency claims need qualification; environment portability is explicitly uncertain in the source.