/GLOSSARY

Platform vision

A platform vision is the constrained statement that defines what the ServiceNow platform will become, what it will not become, and what the first three years look like in concrete capability terms. It is the document architects can build against, not a marketing sentence about digital transformation.

WHY IT MATTERS

Vision without constraint is marketing copy. Every ServiceNow programme has a vision statement somewhere, usually in a slide deck from the original business case - and it almost always reads like a press release: "Become the single pane of glass for enterprise service management." That statement is true, aspirational and entirely useless for making architectural decisions.

A constrained platform vision answers three questions an architect needs before they can make a design choice: what is in scope (which capabilities the platform will own), what is out of scope (which capabilities belong to other systems), and what the maturity trajectory looks like (what the platform does in year one versus year three). The third question matters most because it forces the programme to sequence capability delivery rather than promising everything at once.

COMMON MISTAKES

Writing the vision as a marketing statement rather than an architectural constraint. A vision that does not exclude anything cannot guide anything.
Treating the vision as a fixed document rather than a governed artefact that is reviewed and updated as the platform matures. The year-three vision should be more specific than the year-one vision, not a copy of it.
Allowing the vision to be written by a single stakeholder group (usually IT leadership) without business-unit input, which produces a technically coherent vision that the business does not recognise or support.

Platform vision

The frameworks your steering committee will actually use.