Articles / Decisions, not features
The decisions behind a ServiceNow platform that people trust.
Written by Brandon Wilson for platform owners and the teams who run Discovery, the CMDB and custom applications. Each article takes one recurring problem and works through the decisions that stop it from coming back.
- 01
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.
- 02
CMDB / Integrations
Bringing Fleet device data into the ServiceNow CMDB
Fleet already knows which computers you run, what is installed on them and who uses them. Getting that into the ServiceNow CMDB is less about moving data than about a handful of decisions: which class each device belongs in, how ServiceNow recognizes a device it has seen before, which source wins when Fleet, SCCM, Intune or Jamf disagree, where software lands, and what happens when a device goes quiet.
- 03
ITOM / Discovery
Does Discovery find what is really running? Five ways to check
A Discovery schedule that completes every night proves only that the schedule ran. Whether the CMDB reflects what is actually running depends on scope, credentials, MID Servers, schedule design, and classification. These five checks show where the gaps are, and the order to fix them in so the fixes hold.
- 04
CMDB / CSDM
CMDB trust is a decision problem, not a cleanup problem
Bulk cleanups remove duplicate, stale and orphaned CIs, and within months many of them are back. The cause is rarely the data itself. It is the missing decisions underneath: which attributes identify a CI, which source may update which field, which class a CI belongs to, and who owns it until it retires. Make those decisions and cleanup starts to hold.
- 05
Custom applications
Scoped app, product, or extension? Deciding before anyone writes code
A process that lives in spreadsheets and email can land on ServiceNow in three ways: as configuration of a product you already run, as an extension of one, or as its own scoped application. The right answer depends less on what is technically possible than on boundaries, data, and who will own the result once the project team has gone.
Working through one of these decisions?
Each area starts with a fixed-scope engagement, so the first step is easy to approve.
Discuss your project We reply within 24 hours on business days.