ServiceNow ITOM, ITAM, CMDB, custom apps, AI and managed services.
All articles

Fractional architect

What a fractional ServiceNow architect holds

Someone in leadership is accountable for the ServiceNow platform, but nobody is accountable for how it is built. A fractional architect holds that role part-time. This piece sets out what the role holds, what stays with you, and what you keep.

By Brandon Wilson · · Reviewed

A role, not a block of hours

Think of a fractional CFO. A company that does not need a full-time finance chief still needs someone who holds the role, makes the calls it exists to make, and is still there next quarter.

A fractional ServiceNow architect works the same way. It is a named architect who holds your platform's architecture role part-time: the roadmap, the design authority, the standards, and the oversight of whoever is building on the platform. The unit is scope and accountability. What is agreed is what the role covers and which decisions it holds, and hours are not what is bought.

It is also not a project with a fixed scope, and it is not extra hands for a backlog. Delivery capacity is a different thing. The last section of this piece covers where the two meet.

Signs nobody holds the architecture

Someone is accountable for the platform, and nobody is accountable for how it is built. The admins and developers are capable, and they build what is asked for. A partner may be involved too, and a partner's architect answers to the partner's project.

These are the signs. Design decisions are made by whoever is building the request, or by the vendor quoting the work. Nobody can explain why the instance is built the way it is, and nothing is written down. Every project and every partner brings its own conventions, and customizations pile up between them.

The planning signs follow. The roadmap is a list of requests, not a sequence with dependencies and owners. Upgrades are deferred because nobody is sure what will break. Device, discovery and telecom tools all write to the CMDB, and nobody has decided which source wins. Leadership asks whether the platform is healthy and gets a ticket count.

One test cuts through the list: ask who decides how the next piece of work is built. If the honest answer is whoever is building it this month, nobody holds the architecture.

What the role holds

The role is a set of responsibilities, and each one is tied to a decision. There are seven.

The roadmap. One sequenced roadmap, with dependencies and owners, tied to leadership's priorities. It is an order of work, not a list of requests.

Design authority. Designs above an agreed threshold are reviewed before they are built, whoever builds them, and each decision is recorded with its reasoning. In practice a design review produces a short written note: the options considered, the one recommended, and why.

Standards and governance. How the platform is extended, configure versus build, how data enters the CMDB, and who approves an exception. The decision between configuring a product, extending it and building a scoped application is one of these, and Scoped app, product, or extension? Deciding before anyone writes code sets out how that decision can be made. Where the role sets standards for how data enters the CMDB, it works in the stages that ServiceNow's own CSDM guidance describes.

Partner and vendor oversight. Proposals, statements of work and deliverables are reviewed from your side of the table. A partner's architect answers to the partner's project and leaves when it ends. A fractional architect answers to you, stays between projects, and reviews the partner's designs on your behalf.

Upgrade and release decisions. When to upgrade, what must be ready first, and a recommendation that leadership can act on. ServiceNow publishes upgrade tools and planning resources of its own. The recommendation takes account of those tools, such as Upgrade Center and the Automated Test Framework, and of any customizations that will need review afterwards.

Reporting to leadership. A plain written report: what was decided, what is at risk, what needs a decision.

An escalation point. Admins and developers have an architect for hard design questions.

The standing cadence is agreed in writing before the role starts. There is a weekly design and decision session with the platform team. Each month brings a written platform report for leadership and a roadmap review with the platform owner. Each quarter brings a leadership review of the roadmap, risks and technical debt, and a review of the role itself. Upgrade and release decisions, partner checkpoints and major design reviews happen as needed. Between sessions there is a direct channel for decisions that cannot wait; handling is agreed at the start.

Scoped app, product, or extension? Deciding before anyone writes code

What stays with you

Platform ownership and the business decisions stay with you. Your platform owner and your leadership stay accountable for the platform.

What the architect decides, and what it recommends, is set in the decision-rights table. Each recommendation is recorded with its reasoning so that you can test it. An architect's job includes deciding what should be built, how it fits, and what should not be built at all.

You choose who builds: your team, your partner, or Emetrix. The architect can oversee work delivered by anyone. The role starts with read access, and changes are made by your team, your partner, or under a separate delivery agreement.

The architecture does not live in one person's head. Decisions, standards and the roadmap are written down, and they are yours. Cover during absence is set in the agreement.

What you keep

The artifacts are yours:

  • a decision-rights table;
  • an architecture baseline;
  • target architecture and standards;
  • a decision record;
  • a sequenced roadmap;
  • a technical debt and risk register;
  • monthly reports;
  • upgrade recommendations;
  • a handover pack, if the role ends.

The decision record is the one that earns its keep over time. It shows what was decided and why, so a later decision can be tested against it. The handover pack is there for the day the role ends, so that the platform does not live in one person's head.

Where it fits next to a managed services retainer and a partner

The managed services retainer is delivery capacity. You set the backlog and the order of the work, and the retainer completes backlog items, runs health checks and applies fixes. The fractional architect is a role that holds the roadmap and design authority, and the architect sets the agenda together with your platform owner. Many teams use both. The full difference is on the managed services page.

A simple question separates them: do you need hands, or someone to hold the decisions?

The role works alongside a partner and does not replace one. The architect reviews the partner's designs on your behalf, and the partner's team keeps building. The work under the role can be built by your team, your partner, or Emetrix through the retainer. A team that is mid-project with a partner can start with a design review.

If the platform needs a full-time architect, hire one. Many platforms need architectural judgment every week but not a full week of it, and the role can also cover the gap while you hire.

Managed services at Emetrix

If nobody can say who decides how the next piece of work is built, the platform has no architecture owner, whatever its job titles say. Write down the decisions that need an owner, then ask who holds each one today. The fractional ServiceNow architect page sets out the role, the cadence and how it starts: a first conversation at no cost, a short written role definition, then a standing cadence reviewed each quarter.

References

Want this looked at on your platform?

If the honest answer is whoever is building it this month, start with a conversation.

Start with a conversationWe reply within 24 hours on business days.