Value, Risk, and What’s Next?

[Derek32]

Measure outcomes, not outputs. Track cycle time from idea to production, reuse of shared components, incident density per release, and percentage of work using platform standards (tables, flows, spokes). For business impact, align each app to a value hypothesis—reduced onboarding time, faster case resolution, fewer compliance exceptions—and review quarterly. ServiceNow’s recognition in enterprise low‑code and broader orchestration validates that mature programs combine speed with consistency; your metrics should reflect both. Publish dashboards that make reuse visible and celebrate teams that contribute high‑quality components back to the catalog. Over time, these practices create a predictable delivery engine—and a portfolio that’s easier to audit and evolve.

[Simon Hendery]

Hey @Derek32 

Hope you're doing well! Appreciate your engagement here on the Community, but to be honest, I see you've been regularly posting these little snippets of sales content, without even any links to the related products.

All due respect, but I don't think this is particularly helpful for this audience: we're ServiceNow pros, we don't need to be sold to. I also don't think this forum ('In other news') is the right one to post in.

Sorry for being blunt and negative, but I think we need to maintain high standards of helpful content here in the Community.