Reuse the method. Check the fit.

A practical library for delivery practitioners working across clients, assignments, employers, and teams.

Northstar Delivery Studio is a fictional example. Find a method, check its stated audience and limits, and identify who can clarify its use. A reusable method is a starting point—not a client-ready answer or permission to reuse every associated artifact.

Browse by work stage

These summaries describe method categories; the cards are not links.

Discovery
  • Frame a question before a workshop.
  • Separate observed facts from assumptions.
Delivery planning
  • Make milestones, dependencies, and decision owners visible.
  • Adapt planning prompts to the assignment’s audience and constraints.
Handover and learning
  • Record decisions, open questions, and next owners.
  • Capture transferable learning without carrying over restricted client material.

Three reusable methods

Original working structures for an internal discussion; check assignment fit and reuse permissions before adapting.

Discovery agenda
0–5 minutes: name the decision
Write one sentence: What decision should this discussion help us make? Agree what is outside the session.
5–15 minutes: examine observations
Each participant shares one observed example. Keep a separate list of assumptions and unanswered questions.
15–25 minutes: compare explanations
Ask which evidence supports each explanation and what would change the group’s view.
25–30 minutes: choose the next inquiry
Record one unanswered question, the role that will investigate it, and the next review point. Do not convert an assumption into a conclusion.
Planning prompts
Milestone
What observable result marks this stage complete, and which role can confirm it?
Dependency
What must arrive from another role first? Name the needed input and when its absence would affect the sequence.
Decision owner
Who resolves a scope or priority conflict, and what evidence will that role need?
Changed assumption
Which assumption is least certain? Record the event that would make the team revisit the plan.
Handover note
Done
State the completed result and the permitted evidence or approved source that supports it.
Open
Name the unresolved question without presenting it as a settled conclusion.
Owner and next step
Identify the receiving role, its next action, and the agreed coordination point.
Transferable learning
Record the process lesson in neutral terms; omit client identities, restricted data, branding and quotations unless their reuse is expressly permitted.

Check fit and limits before adapting

Reader guidance

Start with the method’s intended audience, work stage, assumptions, and stated exclusions. Then check the assignment’s client, employer, audience, and reuse permissions. A method may be reusable while a client-specific slide, dataset, logo, or quotation is not.

Keep practitioner guidance distinct from owner administration. Practitioners need the approved version, instructions, known changes, any relevant training context, and the responsible role. Owner-only administration includes maintaining the source, recording permission evidence, and deciding whether a proposed change belongs in the shared version.

If permission or applicability is unclear, do not infer approval from a resource’s presence in a library. Pause adaptation and ask the method owner about the shared method and the assignment lead about local applicability.

Make a reuse decision

Use this sequence before adapting a method for a new assignment.

  1. 1

    Describe the assignment context

    Name the work stage, intended audience, client or employer boundary, and the outcome the method is meant to support.
  2. 2

    Compare fit and limits

    Check the method’s stated audience, assumptions, exclusions, instructions, and any training context. Identify what differs in this assignment.
  3. 3

    Separate method from artifact

    Distinguish reusable prompts or structure from client-branded files, data, quotations, and other materials with separate reuse rights.
  4. 4

    Adapt only within confirmed bounds

    If fit or permission is unclear, pause adaptation. Ask the method owner about the shared method and the assignment lead about local applicability.

Worked example: adapt the method, not the client artifact

A practical distinction from the fictional Northstar Delivery Studio example.

A reasonable adaptation

A delivery practitioner is preparing an internal discovery session for a new assignment. The practitioner checks the agenda’s intended audience and assumptions, keeps its question sequence, and rewrites the prompts for the new discussion. The assignment lead confirms the method fits the local context.

  • Use the method structure as a starting point.
  • Check the audience and assignment context.
  • Leave client-specific material out.
Reuse is not established

The practitioner finds a client-branded version of the agenda from an earlier engagement. Its presence in the library does not establish permission to use it for another client or assignment. The practitioner does not copy its logo, data, or wording and asks the method owner and assignment lead to clarify what, if anything, may be reused.

  • A stored artifact is not proof of reuse permission.
  • Keep client-specific content out unless permission is confirmed.
  • Ask the owner about method rights and the assignment lead about local fit.

Who can clarify a question?

Client Delivery Operations
Method owner — shared method, restrictions, and approved changes
Department: Delivery Operations
Assignment lead
Local applicability — assignment context and audience
Department: Delivery team