Next Experience - Features Recommended to Configure Prior to Turning On

[kathymorris]

Hi all,

We are finally going to enable Next Experience within the next couple of weeks. I went through much of the documentation, watched videos, etc.

Question: Which configurations are recommended to make BEFORE rolling Next Experience out to our Production environment? I watched a ServiceNow video that mentioned setting a global preference first. The example they discussed: One Customer requested to force left hand navigation instead of the top hand navigation menu. ServiceNow advised to set the global property because it cannot be done after the user logs in. 

Another example: configuring the branding beforehand.

Are others configuring the landing page first for certain groups/users to have a certain view?  Or are you going with only the OOB?

Are there any configuration recommendations that anyone before we roll this out, and are sorry later that we did not configure XYZ in the Next Experience?

Thanks,

Kathy 

[Dr Atul G- LNG]

Hi @kathymorris 

If i share my personal experience , more over the configuration , a good end user training is must. Plan 2-3 sessions with user , show them new changes , how it get benefited and what new it brings. 

Also give user a lower instance , to play around new experience. 

[The Machine]

From what I've seen the first step for most organizations is enabling it and getting their users used to the new look and feel.  

Regarding branding, most make sure there header logo is their brand's logo (or whatever it was originally).  Regarding themes.  Theres a regular and dark mode.  If you are looking to modify the theme to follow your company's brand guide lines, I recommend checking out the new Theme builder.

Lastly, as to which preferences and settings you should set before will depend on your organization.  I'm assuming you did this in sub production in an update set to capture the changes you made.  If not, I highly recommend doing that and then deploying the update set.

Its a change, but IMO, its not deal breaking.  The main thing is that if there is a concern about the view change have that option to allow them to switch back, but I would put a time limit ( like next upgrade ) and then take it away since most things are going the way of Next Experience / Polaris.

Hope this helps.  Good luck on your deployment.