Product

What makes a good ServiceNow architect? And what makes “architect” a misnomer? In part one, we discussed what an architect is within the ServiceNow and the larger IT ecosystems. Now, we’ll delve into design documentation - a key part of an architect’s deliverables, and some of the behaviors of folks who may have the title architect but whose actions belie the title. Documenting designs and implementations A good architect understands the value of documentation, and both creates and enforces documentation. My rules of thumb for documentation are: Any custom development that includes creating new tables needs design documentation. This does…

What makes a good ServiceNow architect? And what makes “architect” a misnomer? “Architecture is not an inspirational business, it's a rational procedure to do sensible and hopefully beautiful things; that's all.” - Harry Seidler If you’re here and reading this, you probably have a concept of what a ServiceNow architect is. (In this context, “architect” means a ServiceNow technical architect.) And you’ve likely worked with folks who have the title “architect”, whether on implementation projects or as part of a larger IT ecosystem. But what does this mean, and what should it mean? I’ll spend the rest of this article…