Outcomes and deliverables
Describe what is being provided and how completion will be assessed.
Understand how a service or project can move from an initial conversation to delivery, handover, and review.
Discuss the way your team works, where technology is causing friction, and what you want to change. Existing systems, suppliers, deadlines, and budget expectations help shape an appropriate next step.
Some requests can be scoped from a conversation. Others need a closer technical assessment. Where discovery involves additional work, its scope and any cost should be agreed first.
Describe what is being provided and how completion will be assessed.
Identify decision-makers, system owners, supplier dependencies, and approval requirements.
Separate project work, recurring services, and external charges. Record assumptions that could affect the schedule.
Agree the sequence of work and any service interruption before implementation. For changes affecting staff, include communications and guidance. For a migration, define validation steps and an appropriate rollback approach.
Progress discussions should focus on decisions, dependencies, and changes to scope. Additional work needs a clear approval path so expectations remain aligned.
Check the agreed deliverables and record outstanding items rather than leaving them implicit.
Identify support contacts, operating notes, access ownership, and any maintenance tasks.
For ongoing services, decide how priorities, changes, and improvement opportunities will be discussed.
A simple outline of your users, applications, current providers, and immediate priorities is a useful start. You can also identify the person who approves changes and any dates the work needs to fit around.
Planning a provider changeTell us what’s working, what isn’t, and where you want to go.