In platforms like ServiceNow, architecture decisions rarely start with building something new.
The first question is: does the platform already solve this problem?
When working in platforms, like ServiceNow, the first instinct should not be customization, but discovery.
ServiceNow already provides many capabilities out of the box, modules, workflows, data models, and domain solutions designed for common enterprise processes. These elements exist because the platform has observed patterns across many organizations.
The temptation, however, often goes in another direction.
Requirements look unique.
App Engine allows organizations to create applications rapidly while staying within the platform boundaries. But every new application becomes another component to maintain, govern, and evolve.
In practice, experienced architects tend to follow a hierarchy of decisions.
First, look for out-of-the-box capabilities.
If the platform already models the process, even imperfectly, not at 100%, it often provides long-term stability, upgrades, and platform alignment.
Second, consider configuration and extension of existing modules.
Only after these paths are exhausted does building an application become the alternative.
Not because building is wrong, but because building creates ownership.
Every custom application introduces new data models, lifecycle considerations, governance, and operational responsibility. In a small implementation this may seem insignificant. In a large enterprise platform, these decisions accumulate.
Over years, the difference becomes visible.
Some platforms remain coherent ecosystems.
Others become collections of custom applications.
In practice, it is often not about what we can build, but about what we choose not to build.
