Give a Yearly Service Review a Clear Baseline
A yearly technology review needs a baseline that explains what is being compared.
Ideas for the work ahead
Useful planning notes for public-sector connectivity, technology delivery, and service operations.
The insight library
106 practical guides
Browse practical guidance by date, topic, or the question you are working through.
12 guides from 2024
Clear filtersA yearly technology review needs a baseline that explains what is being compared.
A small IT team needs documentation that fits its working capacity.
A project may encounter a condition that does not match an organization's established security requirements.
A pilot can demonstrate a useful feature while leaving its support model unresolved.
Ticket categories influence what a service team can learn from its records.
A government office in a shared building may depend on spaces and pathways controlled by other parties.
A public project update should explain the service improvement without revealing operational details that do not belong in a broad audience.
A responsibility matrix can clarify a service shared by an agency, a hosting provider, and an application vendor.
The first week after a launch is a useful period for finding questions that did not appear in a demonstration.
A wireless assessment and a user experience review answer related but different questions.
A public form supports a workflow that starts before submission and continues afterward.
Technology budget discussions are clearer when each proposed item explains the service consequence it addresses.
From the original archive
These links lead to the original company articles, with their recorded publication dates.