Share your Golden Rules

Fitz4
Tera Expert

‎09-19-2024 08:38 AM

In a recent Platform Owners Roundtable session, Allen Andres talked about "Golden Rules" or those principles that guide governance on your platform.  Examples he gave were:

- We will always be on the latest ServiceNow version, within X months of release, using automated testing and rapid deployment.
- We will design and build using ‘out of the box’ functionality. We will customize only where there is a clear business need and no alternative.
- Integrations will be limited to those needed to deliver value. Bespoke build should be a last option only.

 

Question:  What are some of your Golden rules?  (looking to steal borrow from the best)

  • 810 Views
3 REPLIES 3

Daniel Borkowi1
Mega Sage

‎09-19-2024 11:57 PM - edited ‎09-19-2024 11:57 PM

Hi @Fitz4,

 

good idea to collect such Golden Rules. I will add some here:

 

  1. We build solutions which meets Security, Performance, User Experience and Compliance requirements.
  2. We adapt the process to the platform and not the platform to the process.
  3. Business Smart Customisation -we will only do customisation which deliver a justifying value.
  4. Integrations - We will use Standard integrations before implementing custom integrations. 
  5. We will follow and use the CSDM in all our processes.
  6. We will import only data which is quality assured and brings value to the processes on the platform.

 

PrabhakarCh
Tera Contributor
In response to Daniel Borkowi1

‎12-02-2024 11:50 AM

As an Organization Policy, we decided to always be at n-1 of current version. While assessing the version, i look at 1. what is in it for me from new features, eligibilities without impacting my licenses or future budget spend. 2. can the new version make our platform more robust on security aspects 3. can i use any unused features in the new version with less efforts. 

britta
ServiceNow Employee
ServiceNow Employee

‎09-24-2024 07:31 AM

I like Daniel's list very much.  Since we just did the session on soft skills, I would add some like: 

1.  We will communicate regularly with our user community.

2.  We will include non-technical people in requirements gathering and testing.

 

You might want to think of some industry specific ones...

Retail -- we will not plan upgrades or new feature roll outs during peak shopping season

Education --  we will not plan upgrades or new feature roll outs during grading periods and graduation

 

I hope more folks chime in here.