Identify appropriate use cases
Not every use case is appropriate for citizen developers or for the ServiceNow platform. Evaluating each use case ensures that the app will be successful and that your citizen developers will get value out of what they create. Focus on use cases that are at the skill levels of your Citizen Developers.
Good use cases
When determining if an app is appropriate for both citizen developers and ServiceNow be on the lookout for things that are task-based, repeatable processes that have a clearly defined workflow. It should be something that can easily live in a custom application or the Service Catalog.
Poor use cases
Poor use cases, on the other hand, involve new integrations or complex logic that should really be setup by your Pro-Code development team. Additionally, if the work falls outside of App Engine Studio or Catalog Builder, it's likely not the best use case for Citizen Developers. You'll also want to avoid things in the global scope as it's more difficult to install governance for your Citizen Developers outside of scoped apps. While these items may make the use case less desirable for Citizen Developers, it does not indicate that it is a poor use case for the Now Platform.
