The Three Moments a Mid-Sized Enterprise Should Call for ServiceNow Consulting Services (and the One Moment They Usually Do)
A CIO at a 900-person specialty chemicals group phoned me on a Tuesday in June. His voice had that specific flatness you hear from people who have been in meetings since seven in the morning. The ServiceNow platform his team had been building for eleven months was going live in three weeks, and he had just been told by his own implementation partner that the CMDB was not going to be ready for wave two. Not "delayed by a sprint" not ready. Not populated, not governed, not integrated with the discovery tool they had already paid for. He wanted to know whether it was worth pausing the go-live or pushing through. I asked him when he had first suspected the CMDB was in trouble. He said month four. I asked why he had not called anyone in month four. He said he thought his internal team could handle it, and by the time he was sure they could not, it felt too late to bring anyone else in. That is the pattern. Mid-sized enterprises call for outside ServiceNow consulting services when they are already on fire, and the fire is usually something that started five months earlier as a small design decision nobody caught. If you are a CIO or a platform owner at a mid-market company running...
