MENTARA
Book a call
Software Services

Implemented as a ticket system, bought as a workflow platform.

The common ServiceNow failure is encoding existing process into the platform rather than fixing it. MENTARA treats process design as the deliverable.

Discuss a ServiceNow priority Read the detail

More in Software Services

The decision in front of you

ServiceNow is bought to change how work moves through an organisation and is frequently implemented to preserve exactly how it moved before. The existing approval chain, the existing categorisation scheme and the existing queue structure get reproduced in a more expensive system, and the platform becomes a better-instrumented version of the problem.

The tell is that reporting improves and outcomes do not. Everyone can now see how long things take, and things take as long as they did — because the delay was never a visibility problem. It was the process itself.

The failure mode

Customisation as a substitute for a decision.

When a platform is configured to match every existing local variation, the result is an implementation that nobody wants to upgrade. Custom logic accumulates against a product that ships substantial releases twice a year, and each upgrade becomes a regression-testing project rather than routine maintenance. Organisations then defer upgrades, fall behind, and lose access to the capability they are paying for.

Almost every one of those customisations was requested by someone with a legitimate reason. The failure is that nobody was empowered to say that a local variation was not important enough to encode permanently, so the platform absorbed every exception and the standard product was never allowed to do its job.

The second pattern is scope drift into workflows nobody owns. ServiceNow expands easily into HR, facilities, security and customer workflows, which is a real strength — and each expansion needs a process owner in that function who is accountable for how the workflow behaves. Where the platform team owns the technology and no business function owns the process, workflows are built and then decay.

Capability

What MENTARA does.

01Process design before configurationDeciding what the process should be, which variations are genuinely required and which are habit — the work that determines whether the implementation is worth doing.
02IT service managementIncident, request, change and problem designed to reduce elapsed time rather than to reproduce the current model with better dashboards.
03IT operations and asset workflowsCMDB scope decided by the decisions it must support, discovery and asset lifecycle. An accurate partial CMDB beats a comprehensive stale one.
04Employee and customer workflowsExtension beyond IT, with a named process owner in the receiving function as a precondition rather than an afterthought.
05Security and risk workflowsSecurity incident, vulnerability and risk workflows connected to the operational reality of who acts on them.
06Platform governance and upgradabilityCustomisation policy, technical debt reduction and release practice that keeps the platform current instead of frozen.
Approach

How the work runs.

  1. 01 Measure the process as it is

    Where elapsed time actually goes — usually waiting for approval or clarification, rarely in the step everyone assumes.

  2. 02 Decide what standard means

    Which variations survive and which are retired, agreed with the people affected before configuration. This is the difficult part and it is not a technical exercise.

  3. 03 Configure to the standard product

    Deliberate bias toward out-of-the-box behaviour, with customisation treated as a decision that carries an ongoing upgrade cost someone has accepted.

  4. 04 Establish process ownership

    Each workflow has an owner in the function that runs it, accountable for how it performs — not the platform team by default.

Questions

What buyers ask.

Are you a ServiceNow partner?

MENTARA does not currently hold ServiceNow partner status and receives no commission on ServiceNow licensing. Where certified partner status is a procurement requirement, that is worth establishing early.

It does mean our advice on module expansion carries no commercial interest — including when the recommendation is that you do not need another module.

Our instance is heavily customised and we cannot upgrade. What now?

A common and recoverable position. The work is to inventory the customisations, establish which are still used and still justified, retire what is not, and move the remainder toward supported patterns — sequenced so you can upgrade before it is complete rather than after.

Should we extend ServiceNow into HR or facilities?

Only where that function will own the process. The platform capability is real; the failure mode is a workflow built for a function that never took ownership of it, which then degrades and damages confidence in the platform generally.

06

Where MENTARA fits best.

Scope

We fit process design, upgradability remediation, governance, and independent assessment of an implementation that is not delivering what it was bought for.

Large multi-module global rollouts requiring a substantial certified bench are better served by a badged ServiceNow partner, as is anything needing partner-tier procurement.

Where this connects

Bring the implementation that improved reporting and nothing else.

Share the business context, constraints and expected outcome. MENTARA will identify the relevant accountable route.

Submit your requirement

One partner. One plan. Measurable outcomes.