12. Leadership and delivery

A strategy needs an owner and a calendar

Delivery translates a choice into work that a real team can sustain. A good plan names what will happen, who is responsible, what it requires, what depends on what and how the team will respond when an assumption fails. It does not turn every useful idea from the course into another task. Leadership includes protecting focus and stopping work that no longer serves the mission.

Begin with the strategic decision, not a blank calendar. If access investigation comes before promotion, the schedule must reflect that dependency. A communication launch should not be dated before eligibility wording and capacity are confirmed. A visually tidy plan can hide this contradiction; write the dependency in plain language so it is reviewable without a project-management tool.

Allocate scarce hours as well as money

The fictional advice project has a maximum £1,000 and 20 staff hours over 90 days. That is an improvement allowance, not an unlimited operating budget. Routine service work remains separate. An activity using two people for an hour consumes two person-hours. Meetings, preparation, checking, coordination and maintenance all count.

Create a budget with amount, purpose, assumption, owner and whether the cost is cash or imputed time. A contingency reserve is a planning choice for uncertainty, not spare money to spend automatically. Actual commitments need the organisation's appropriate authority. In this course, budgets are proposals only; no purchase, service installation or deployment is required.

A useful first allocation is deliberately modest. The supplied example assigns six hours to evidence design and audit, four to access prototype, three to review, three to test planning, two to handoff and two to contingency. That totals 20. The cash scenario reserves £200 for access adjustments, £200 for research support if authorised, £150 for production, £150 for evaluation and £300 uncommitted contingency. These are fictional planning amounts, not price quotes or spending instructions.

Put responsibilities at the point of decision

Name an accountable owner for the project, an operational owner for the service, a content reviewer and an evidence owner. Small teams may combine roles, but an unassigned role is still a gap. For a fictional submission, use role titles and state that appointment is proposed. Do not imply that a real colleague has accepted responsibility.

Decision rights matter more than a long responsibility matrix. Who can approve public wording? Who can stop a test? Who decides whether capacity is safe? Who handles a complaint or a suspected privacy issue? A task can be completed while its approval remains unresolved. Make that status visible instead of labelling everything done when a draft exists.

A handoff needs the current version, source facts, limits, owner, next action and restart conditions if paused. Do not hand over only a polished artefact without the assumptions that make it valid. If the person maintaining the work cannot tell when to update it, the initial delivery is incomplete.

Plan in stages with useful checkpoints

A 90-day plan can use three periods. In days 1–30, confirm the problem, permissions and evidence limits; prepare a bounded prototype. In days 31–60, review feasibility and design or conduct an appropriately authorised test. In days 61–90, interpret the evidence, decide the next step and hand over maintenance. The fictional route designs and simulates these stages without claiming a live implementation.

Each checkpoint should produce a decision, not merely a document. After evidence appraisal, the team may revise the diagnosis. After operational review, it may narrow the promise or abandon the prototype. After evaluation, it may continue, revise or stop. A plan that allows only forward movement is not prepared for learning.

Include recovery and reverse actions. If an access change confuses people, how would the team restore the approved wording? If a supplier becomes unavailable, what manual process remains? If the owner leaves, what information allows another person to continue? Recovery should be proportionate to the task, but it should exist before the launch proposal is treated as ready.

Evaluate suppliers without buying a dependency

Compare a manual route, a free tool route and an optional supplier route against the same task. Consider required capability, data handling, access, export, maintenance, support and exit, not only the subscription price. A free tool can impose staff work or unsuitable information terms. A paid supplier is not automatically more reliable or necessary.

Do not require a paid service to complete the course or capstone. If your organisational proposal includes one, supply a feasible no-cost alternative and explain the trade-off. Customer-specific configuration should be an explicit product or operational responsibility in a real project, not an unexplained assumption that the learner must solve by buying software.

For AI-supported work, include checking and re-evaluation after changes. A tool update, a changed service fact or a new task can invalidate earlier workflow evidence. Assign someone to review those changes and preserve a manual fallback. 'Automation' is not a reason to omit ownership.

Lead a defensible discussion

A presentation should explain the problem, evidence, choice, alternatives, resources, risk and learning rule. Put the consequential uncertainty near the recommendation. The audience should be able to understand the decision without reading every appendix. Avoid claiming that a clean slide or confident delivery proves the strategy is correct.

Anticipate objections fairly. A service owner may worry about workload; a community representative may worry about exclusion; a finance colleague may question the budget assumptions. Treat those as evidence about the plan rather than resistance to marketing. Revise the proposal where the objection identifies a real mismatch.

The final handoff should distinguish designed, authorised, tested and delivered. A fictional simulation is designed and analysed, not implemented in a real organisation. A live project may have permission for one step but not another. Accurate status protects both people and the credibility of the work. The capstone now asks you to integrate these distinctions into a strategy you can defend, including a decision not to proceed when the prerequisites are absent.

Turn a blocker into a bounded decision

A delivery blocker should identify the missing prerequisite, the role able to resolve it and the next action. 'Waiting for approval' is too vague. 'The service owner must confirm whether staff can cover the proposed appointment time; until then, retain current availability wording and continue the eligibility prototype' identifies both the dependency and safe work that can proceed. In a fictional capstone, these remain proposed responsibilities, not actual commitments by named people.

A well-reviewed draft may be ready for handoff while a real launch still needs service configuration, accessibility review or organisational permission. Keep those states distinct. Equally, do not make an unrelated future ambition block a small action whose prerequisites are genuinely complete.

At the final checkpoint, ask what the next owner needs to maintain the work for a month without you. Supply the source facts, current wording, budget assumptions, review date, incident route and manual fallback. Identify which evidence becomes stale if service scope, staffing or tool behaviour changes. A handoff that preserves only the final recommendation forces the next person to reconstruct the reasoning and may lead them to reuse invalid evidence. A concise maintenance note is therefore part of delivery, not optional documentation added after the useful work. It keeps the strategy connected to the conditions under which it was defensible.

Study allocation and completion

Allocate 1.5 hours to this lesson and worked example, 1.5 to critical reading, 2 to the lab, 3 to the assignment, 1 to critique and 1 to reflection and revision: 10 hours in total. These are planning allocations, not measured duration or a timed assessment. Read in short sessions if helpful. All resources are plain text; a notebook, calculator or optional free spreadsheet is sufficient. No video, AI account or paid service is needed.

For critical reading, use the linked selection if accessible and the internal reading comparison. Record its question, argument, evidence type, assumptions and one reason it might not transfer to your organisation. A missing external reading does not prevent completion: compare the two original internal positions and state that you have not appraised the external source. Keep a source log with title, URL, access date if accessed, claim supported and limitation. Links are references, not permission to copy or upload readings to AI.

Complete the lab manually first. The supplied simulated AI output is authored teaching material, not a transcript, real research or verified model performance. Mark each claim supported, unsupported or contradicted. Optional live AI may generate alternatives from these fictional inputs only; record tool, date, instructions, checks and revisions. Never supply personal, confidential or unauthorised material. If not using AI, compare the supplied output against your manual work and label that route accurately.

For critique, use the rubric and annotated example, alone or with a consenting peer; no peer is required. For reflection, revise one consequential decision and record the old choice, new choice, evidence and unresolved uncertainty. Keep work locally. Self-completion records learning activity, not professional competence or an independently assessed award. Version: 1 November 2026; report suspected errors through the course host's available contact route, or retain a correction note if no route exists.

Practical lab — 2 hours

Reconcile the supplied hours and cash scenario. Assign proposed responsibility roles to every stage. Introduce two disruptions: the service owner cannot approve evening availability, and a chosen free tool becomes unavailable. Revise the plan without raising its ceilings. Compare manual, free-tool and supplier routes on maintenance and exit; do not sign up or purchase.

Portfolio assignment — 3 hours

Produce a 90-day delivery plan, budget and 600-word strategic presentation script. Include dependencies, decision checkpoints, stopped/deferred work, routine versus improvement capacity, named role responsibilities, configuration prerequisites, recovery and a manual fallback. Integrate Modules 1–11 into the capstone evidence pack; do not describe planned work as completed.

Critique — 1 hour

Use the rubric and annotated example, alone or with a consenting peer. Challenge your preferred option, a missing owner and a possible harmful consequence.

Reflection and revision — 1 hour

Change one consequential choice and keep a revision note. State what evidence would reverse the revised decision. No live contacts, spend, AI account or publication are required.

Self-review weights: evidence and source appraisal 25%; critical reasoning 25%; contextual fit 20%; feasibility and evaluation 20%; clarity and reflective judgement 10%. Score each 0–4 and sum(weight × score / 4). These are illustrative learning criteria, not validated academic grades.

Evidence: label costs and acceptance of roles as assumptions where appropriate. Reasoning: show dependencies and responses to disruption. Context: respect service, community and finance objections. Feasibility: reconcile all work to 20 hours and £1,000. Reflection: reduce scope or stop safely rather than hiding resource overruns.

0 means absent or misleading; 1 asserts without support; 2 supplies partial relevant support; 3 links evidence, alternatives and feasible action; 4 tests a strong contrary account and defines a reversal condition. Invented evidence, privacy breaches and unsupported public promises require correction before self-completion regardless of the score.

Weak: 'Launch all channels in week one; volunteers will cover the work.' Capacity and acceptance are invented. Competent: 'Investigate first, then prototype and evaluate within 20 hours.' Strong: 'No public promise of evening appointments until the service owner confirms staffing. If unavailable, test clarity of existing options instead. Keep source wording in plain text so loss of a free tool does not block the project. Reserve two hours for contingency and hand over the claim ledger and stop rules.' Annotation: the stronger plan includes a viable response to missing prerequisites, not just a list of milestones.