Developed 80% of the enhancements in 4 months, completely stabilizing this US-based Leading Enterprise’s ServiceNow environment

Jade Global optimized processes, implemented out-of-the-box features, and improved user experience of the ServiceNow platform for this Global Entity

About the Client

Pure Storage develops all-flash data storage hardware and software products. It helps innovators build a better world with data. Pure's data solutions enable SaaS companies, cloud service providers, and enterprise and public sector customers to deliver real-time, secure data to power their mission-critical production, DevOps, and modern analytics environments in a multi-cloud environment.

Pure Storage enables customers to quickly adopt next-generation technologies, including artificial intelligence and machine learning, to maximize the value of their data for competitive advantage. And with a Satmetrix-certified NPS customer satisfaction score in the top one percent of B2B companies, Pure's ever-expanding list of customers are among the happiest in the world.

Client Speak

iconEveryone in Jade Global's ServiceNow team has been instrumental in stabilizing Pure's ServiceNow environment. They quickly came up-to-speed on Pure's ServiceNow environment and became productive. They were very reliable and available to resolve issues. I appreciate the team accommodating Pure's overwhelming demands and want to share my appreciation for the work that was above and beyond the normal responsibilities and the quick resolution of production bugs. I would love to get their continued feedback on how to streamline and optimize Pure's ServiceNow Platform.icon

- Pattie Park, IT Project Manager

The Challenges

  • The inability of the customer to articulate their existing process
  • The unwillingness of teams to change existing processes to adopt best practices
  • No documentation was available to understand the processes
  • Direct code changes were being made in Production
  • Multiple issues in code deployment as development and testing instances were not being cloned from Production
  • Stringent project timelines to meet the deployment deadline
  • Multiple projects involving similar components going live at the same time