professional woman facing a crossroads with two signs going in either direction that say CODE and NO CODE

To Code or Not to Code (this is the question!)

‘Tis it nobler to bend to false conventional wisdom or to follow the found truth; ay, there's the rub! Introduction Unless you’re brand new to the ServiceNow ecosystem or have completely ignored all talk and literature about the platform in recent years, you’ve heard the drumbeat of a couple of key messages (that I’ll paraphrase): Low and no code solutions are the future Stay “Out of the Box” as much as possible Out of the gate, the question I’ll pose is: does low code / no code matter? If so, why does it matter? In this article, I’m going to…
architectural structure

Wherefore Architecture?

If ServiceNow is built to support Citizen developers, why do we need ServiceNow architects? “Thinking about design is hard, but not thinking about it can be disastrous.” - Ralph Caplan Introduction For almost 14 years in the ServiceNow space, and across a rapid expansion of the exosystem, it has been interesting to observe and analyze various organization’s approaches to developing and maintaining their ServiceNow environment. Specifically, how do organizations manage the inflow of business needs, the distribution and velocity of development, configuration and administrative work, and the ongoing maintenance of the platform? As the footprint of ServiceNow has expanded conjunctionally…
platform part 2

It’s the Platform, Stupid* (Part 2)

* - A play on the famous James Carville quote about the economy, not implying that ServiceNow folks are stupid It’s been a few years since I wrote Part 1 of this article, going through the history and evolution of the ServiceNow platform, and the morphing of the company strategy from platform to product. After working with multiple clients in the meantime, and reading lots of new marketing and going through many platform release upgrades, I thought it time to revisit the subject with new perspective and analysis. A quick recap: In the early 2000s, ServiceNow (nee “Glide”) was envisioned…
Improvement graph

PD (Platform Disfunction) is Treatable

The things ServiceNow should change or enhance yesterday "Continuous improvement is not about the things you do well — that’s work. Continuous improvement is about removing the things that get in the way of your work. The headaches, the things that slow you down, that’s what continuous improvement is all about." - Bruce Hamilton I’ve written previously about the power of the platform, and my belief in its terrific original design and flexibility. In recent years, in its push to create and sell products, ServiceNow has sacrificed enhancements to the platform which us architects, developers and admins have to work…
Where, When and Why

The Three Ws of Development

Where, When and Why you should do your development In journalism, there’s the concept of the Five W questions whose answers are fundamental to getting the information needed: Who What When Where Why I want to talk about what I call the “Three Ws of Development” in the ServiceNow realm. These three are: When, Where and Why. We’re going to skip the questions “Who” and “What”. Why? Because “who” is a question for hiring managers, recruiting, and resource vetting. And “what” is (too often) the focus of most if not all training and documentation. Do you need to get the…
To Scope or Not to Scope

To Scope or Not to Scope

ServiceNow introduced the concept of Scoped Applications in the Fuji release. From their documentation: Application scoping protects applications by identifying and restricting access to application files and data. By default, all custom applications have a private scope that uniquely identifies them and their associated artifacts with a namespace identifier. The application scope prevents naming conflicts and allows the contextual development environment to determine what changes, if any, are permitted. Source: Application scope Each ServiceNow application has an application scope that determines which of its resources are available to other parts of the system. Application scoping ensures that one application does…
Code

Breaking the Code – Designing for Configurable Maintenance

ServiceNow is nothing if not flexible. It certainly gives you options for achieving your business and development goals; some of these are obvious and well documented, and some feel like they’re on the “secret menu” for the die-hards only. Regardless, ServiceNow was designed as a flexible platform. Over the years I’ve seen this flexibility used in a myriad of ways, some really clever and some head-scratchers. Most fall somewhere in the middle. It’s also been the impetus for the rise of good and best practices, from tribal hearsay to attempted codification. But one thing I feel strongly about is using…
upgrades

The Misconceptions of Upgradeability

The Blob is a 1958 American science fiction horror film whose storyline concerns a growing, alien amoeboid entity that comes to Earth from outer space inside a meteorite. It devours and dissolves citizens in small Pennsylvania communities as it grows larger, redder, and more aggressive each time it does so, eventually becoming larger than a building. In recent years in the ServiceNow ecosystem, one of the topics that has taken on a “blob-like” existence is upgradeability: the ability to perform an upgrade to the next ServiceNow release, how long it takes, how much it costs, how much remediation is required,…
Platform

It’s the Platform, Stupid*

This is the one where I most run the risk of sounding like an old curmudgeon. However, I don’t think I’m wrong, and hopefully my explanation bears this out. * - A play on the famous James Carville quote about the economy, not implying that ServiceNow folks are stupid As many know, ServiceNow has been through 4 CEOs: Fred Luddy, Frank Slootman, John Donohoe, Bill McDermott; and as most know, Fred was the founder. Fred at his heart is a developer. (From Broke To Billionaire: How Fred Luddy Built The World’s Most Innovative Company) From Forbes: Luddy hit on a…