Skip to content

Services

Nine services, and the seams between them.

Applications, data, artificial intelligence, cloud, security, engineering, transformation, operations and demand. Each is a full service with its own capability architecture — and almost no enterprise programme stays inside one of them.

Why they sit together

A finance system moves to a new release. That is an applications project until the interfaces are counted, at which point it is an integration project; then the reporting has to reconcile, so it is a data project; it runs somewhere, so it is a cloud project; the authorisations have to agree with the corporate directory, so it is a security project; and somebody operates it on the Monday after go-live.

Split across five suppliers, each of those is somebody else’s dependency and none of them owns the seam. Noble’s services are separate disciplines with separate depth, held in one organisation, so that the handover between them is an internal one.

How the work arrives

Three shapes, and most engagements move through more than one of them. Which service leads is decided by the problem rather than by which team is free.

01

Advisory and architecture

What is running today, what it costs to keep running, and what the target state would actually involve. The output is a sequenced plan with a first deliverable inside the quarter, not a document.

02

Design and delivery

Implementation, engineering, migration and integration, delivered in working increments that can be seen and used rather than in a phase that ends with a demonstration.

03

Managed operations

Service desk, infrastructure, cloud, network, workplace and application support. Running a system is a different discipline from building one, and it is the year the build decisions get tested.

Start with the problem.

Describe what is not working, or what has to be built. Which service leads follows from that, and often more than one does.