Strategic Business Proposals is not a long description of a problem or a list of attractive recommendations. It is a reasoned case for action that shows why a change is needed, what options exist, how affected stakeholders will be engaged, what resources and risks must be managed, and how leaders will know whether the intended value has been created.

The practical answer: a credible proposal connects a defined problem and strategic objective to evidence, options, stakeholder engagement, implementation feasibility, governance, measures and a review cycle.

The seven elements of a credible proposal

Element	Question to answer	Evidence required
Strategic problem	What outcome is not being achieved, and why does it matter?	Customer, financial, operational, workforce, market or risk evidence
Objective and scope	What will the proposal achieve, for whom and by when?	Clear outcome, boundaries, assumptions and constraints
Options	What realistic choices exist, including doing nothing?	Benefits, costs, risks, dependencies and trade-offs
Recommendation	Why is this option preferable in this context?	Explicit evaluation against agreed criteria
Stakeholder engagement	Who can influence or be affected by the change?	Stakeholder map, engagement purpose, timing and response routes
Implementation and governance	How will the work be delivered, owned and controlled?	Workstreams, resources, decision rights, risks and escalation
Measurement and review	What evidence will show progress, value and unintended effects?	Baseline, leading and lagging indicators, feedback and review points

A proposal should make its logic visible. The recommendation must follow from the evidence and criteria, rather than appear as a preferred answer presented after a selective description of the problem.

Stakeholders: engagement as a design input

Stakeholder engagement is not a final communications plan. People affected by a change often hold operational knowledge, legitimacy or implementation power. Engagement should therefore start when options can still be shaped.

Stakeholder group	Likely interest	Appropriate engagement
Senior sponsors and board	Strategic value, risk, resources, governance	Decision papers, risk review and outcome reporting
Employees and managers	Work design, capability, workload, fairness and feasibility	Workshops, pilots, consultation, feedback and implementation support
Customers or service users	Quality, access, continuity and trust	Insight research, testing, accessible communications and complaint learning
Partners, suppliers or regulators	Interdependencies, compliance, service standards	Joint planning, assurance and formal reporting

Power-interest mapping can help prioritise engagement, but should not reduce lower-power groups to a communications problem. People with less formal power may carry significant implementation knowledge or experience disproportionate consequences.

Implementation: translate intent into operating reality

Implementation fails when a proposal assumes that a good idea will deliver itself. A credible plan identifies changes to roles, process, capability, technology, finance, communication and governance.

Implementation area	Questions to test
Roles and accountability	Who owns delivery, decisions, escalation and benefits realisation?
Capability	What skills, time, leadership and support are required?
Operating processes	What workflows, policies, systems or handovers will change?
Resources	What investment, capacity and opportunity cost are involved?
Risk and assurance	What could go wrong, how likely is it and what mitigation is realistic?
Change and communication	What needs to be understood, practised, co-designed or reinforced?

Measurement: avoid the single-KPI trap

Measures should capture both intended outcomes and potential harm. A cost-saving proposal may meet its financial target while damaging service quality, capability or employee wellbeing. Using balanced indicators makes these tensions visible.

Measurement type	Example
Leading indicator	Capability completion, system readiness, stakeholder participation, process adoption
Outcome indicator	Customer resolution, quality, cost, throughput, retention or safety result
Experience indicator	Employee voice, customer feedback, inclusion and confidence in the new process
Risk indicator	Errors, complaints, workload, adverse impact, compliance or control failures

An original workplace application

Fictional Rivergate Libraries faces declining use of physical sites and pressure to improve digital access. The proposal is not simply “launch an app”. It defines the strategic objective—improve equitable access to information and learning—then compares options: extend opening hours, improve digital services, partner with community hubs or combine the approaches.

Stakeholder engagement includes users, staff, volunteers, local groups and accessibility advocates. Implementation identifies digital skills, support for staff, data protection, library-space changes and service standards. Measures include digital uptake, physical access, user satisfaction, staff workload, accessibility feedback and usage across different communities. The proposal is credible because it links technology to purpose, inclusion, operating capacity and learning.

Appraising options and making trade-offs explicit

A proposal becomes strategic when it demonstrates judgement between plausible alternatives. This means defining evaluation criteria before selecting an option. Criteria might include strategic fit, customer value, equity, financial affordability, capability requirements, legal or reputational risk, time to benefit and reversibility. The recommended option should not be described as risk-free; it should be selected because its trade-offs are better understood and more acceptable than the alternatives.

Option-appraisal criterion	Question a decision-maker should ask
Strategic fit	Does this option advance a defined organisational aim rather than solve a local symptom?
Value and distribution	Who benefits, who bears cost and could the option create unequal access or impact?
Feasibility	Are capacity, skills, systems, permissions and partners realistically available?
Risk and resilience	What could fail, what early warning signs exist and can the option be adapted or reversed?
Timing	When will value be visible and what has to happen first?
Stakeholder legitimacy	Is the process likely to retain trust among those who must implement, use or regulate it?

The comparison should include a credible “do nothing” or “improve the current state” option. This establishes the cost of inaction and prevents a proposal assuming that any change is automatically preferable.

Benefits realisation and implementation assurance

Implementation needs a named benefits owner, not only a project owner. A project can deliver a system, policy or process on time while failing to create the intended organisational value. Benefits ownership asks who will change working practice, which assumptions must hold true and what action will be taken if early measures indicate that value is not emerging.

Assurance area	Practical control
Benefits	Define baseline, intended benefit, owner, measure, review date and dependencies
Risks	Maintain a live risk register with clear mitigation, trigger and escalation owner
Decisions	Set decision rights and stage gates for spending, scope changes and material risks
Readiness	Test capability, technology, communication, process and stakeholder preparedness before scale-up
Learning	Pilot where possible, capture feedback and adapt the approach before wider commitment

This is especially important where a strategic proposal changes both technology and behaviour. Communication alone cannot create adoption. People need clarity about what changes, why it matters, what support is available and how practical problems will be resolved.

Proposal-writing discipline

A good proposal is readable as well as rigorous. It should state the recommendation early, use evidence that is relevant to the decision and distinguish facts from assumptions. Avoid creating false precision through untested forecasts. Where estimates are necessary, identify the assumptions, range of possible outcomes and the evidence that would alter the recommendation. This improves executive scrutiny and makes later learning possible.

Sequencing change and communicating with stakeholders

Strategic proposals should specify sequencing because timing affects risk, trust and capacity. A proposal that requires new technology, revised roles and behaviour change at the same time may need a phased approach. Early phases can establish governance, test feasibility and develop capability; later phases can extend the model once evidence supports it. Sequencing is not delay for its own sake. It protects service continuity and makes assumptions visible before the organisation commits to full scale.

Communication should also be designed as a two-way process. Stakeholders need different information depending on their role: sponsors need choices and risk; managers need implementation responsibilities; employees need a clear account of what changes in their work and how concerns will be addressed; customers or service users need practical information about access and continuity. A single presentation or launch email is rarely sufficient.

Communication question	Proposal response
What must people understand?	State the purpose, change, timeline, decision boundaries and practical support clearly
What needs to be tested?	Identify assumptions best checked through pilots, workshops or user feedback
Where could trust be lost?	Address uncertainty, trade-offs and safeguards openly rather than offering false certainty
How will leaders listen?	Name feedback channels, response owners and the way issues will influence decisions

Reviewing value after implementation

A proposal should define when leaders will review whether benefits have materialised and whether adverse effects have emerged. This review should compare actual outcomes with the baseline and assumptions stated in the original case. If a result falls short, leaders should ask whether the design, implementation, context or measurement was at fault rather than simply concluding that people resisted change.

A disciplined review also creates organisational learning. It improves future business cases, strengthens stakeholder confidence and prevents an organisation repeating the same delivery errors under a new project title.

CMI 705 relevance

This framework supports CMI 705: Leadership and Management of Strategic Change. It is useful where strategic leaders need to move from analysis to a defensible, implementable proposal. The emphasis is on evidence, stakeholder legitimacy, delivery feasibility and review—not on providing a response to any current assessment brief.

For a unit-specific illustrative resource, see the CMI 705 Strategic Change example. This guide is distinct from that NHS case study and focuses on a reusable proposal architecture.

Frequently asked questions

What makes a strategic proposal credible?

It defines the problem, tests options against evidence, makes trade-offs explicit, engages affected stakeholders, demonstrates feasibility and states how benefits and risks will be measured.

Why include stakeholder engagement before a decision is made?

Early engagement can improve problem understanding, identify delivery risks, strengthen legitimacy and surface options that leaders would not otherwise see.

References

Chartered Management Institute (CMI) (n.d.) Management and Leadership (Level 7). Available at: https://www.managers.org.uk/education-and-learning/qualifications/ (Accessed: 19 August 2026).

Hollmann, H. et al. (2022) ‘Ten simple rules on how to develop a stakeholder engagement plan’, PLoS Computational Biology, 18(10), e1010385.