Evolving customer value propositions in combination with the accelerated pace of technology requires that IT leaders not only stay on course to increase IT transparency, but also steer the effectiveness of tech adoption and business outcomes as well.
When it comes to ServiceNow implementation, IT leaders often find themselves challenged with a customization vs. configuration dilemma, and it’s easy to understand why.
ServiceNow customization appears alluring, as it is minimally disruptive to the status quo with easier to migrate workflow and processes. Owing to certain business functionalities, demands, and scenarios where the benefits of customization outweigh the potential risks and challenges – such as any compliance and regulatory requirements, critical business objective, or adoption requirement – clients prefer customization that delivers the desired outcomes.
A complexity/value measurement and evaluation matrix can help in auditing and ensuring that proposed customizations and functionalities stay within the threshold of acceptable risks and systems performance.
While customization brings benefits in the form of tailor-made functionalities, it also impacts time, effort, cost, and introduces the challenge of deploying upgrades for future releases. Codes that have been altered and customized might break during an upgrade, leading to delayed implementation and an inability to deploy new applications or features. Further, additional IT and development staff may be required to maintain the customization, resulting in cost- and resource-creep.
Configuration, on the other hand, has proven to be a more value-accretive option, especially when organizations are on the verge of a migration milestone and need to revisit organizational processes to rationalize the legacy points of customizations. Deploying out-of-the-box (OOTB) functionalities deliver the desired benefits of automation, interoperability, timely deployment of the latest upgrades, reduced need for special resources, and the opportunity to implement cost-optimized process improvements. Care should be taken in evaluating each option, however.
In our experience on ServiceNow implementation engagements with Fortune 500 clients and small-land medium-sized businesses, a majority of IT leaders select the baseline configuration deploying the ServiceNow best practices and APIs to address business requirements. An OOTB configuration minimizes invasive risks and technical debt, and ensures timely, error-free upgrades. Principally, it is wise to avoid the scope creep resulting from ad hoc or continual requirements due to adding customized features that require specialized developers for custom application maintenance.
While there is no one-size-fits-all solution, there will always be scenarios where customization is more appropriate than configuration, especially in certain industry- or business-specific workflows. Trianz has delivered many engagements successfully with client-specified customizations tailored for business outcomes.
Our seasoned ServiceNow experts work in alignment with business and IT leaders to understand their concerns and leverage the OOTB functionalities with customizations and workarounds(when required) to deliver a transformative stakeholder experience.
Application Modernization at Speed and Scale Enterprises are pursuing greater application scalability, cost efficiency, and standardization with containerization and virtualization platforms. So, what’s the difference? Containers are a type of virtualization technology that allows users to run multiple operating systems inside a single instance of an OS. They are lightweight and portable, making them ideal for running applications across different platforms.Explore
Container Orchestration or Compute Service? Amazon Web Services (AWS) offers a range of cloud computing services to meet enterprise needs. Included in its service offering is the elastic compute service (ECS) and elastic compute cloud (EC2). Choosing between these two services can be difficult, as one focuses on virtualization while the other manages containerization. In the following article, we will explore the differences between Amazon ECS and EC2 to help you better understand which service is right for your use case.Explore
What is Application Modernization? Application modernization is the process of converting, rewriting, or porting legacy software packages to operate more efficiently with a modern infrastructure. This can involve migrating to the cloud, creating apps with a serverless architecture, containerizing services, or overhauling data pipelines using a modern DevOps model.Explore
What are the Differences? Though often used interchangeably, data pipelines and ETL are two different methodologies for managing and structuring data. ETL tools are used for data extraction, transformation, and loading. Whereas data pipelines encompass the entire set of processes applied to data as it moves from one system to another. Sometimes data pipelines involve transformation, and sometimes they do not.Explore
What is a Hybrid Data Center? A hybrid data center is a computing environment that combines on-premise and cloud-based infrastructure to enable the sharing of applications and data across physical data centers and multi-cloud environments. This allows organizations to balance the security provided by on-premise infrastructure and the agility found with a public cloud environment.Explore
Finding Hidden Patterns and Correlations Innovative technologies such as artificial intelligence (AI), machine learning (ML) and natural language processing (NLP) are transforming the way we approach data analytics. AI, ML and NLP are categorized under the umbrella term of “cognitive analytics,” which is an approach that leverages human-like computer intelligence to identify hidden patterns and correlations in data.Explore