Explore
  • Explore NotifyMe
  • Customization through Business Process Analysis
  • Getting started
    • Quickstart Guide
      • 1. Onboard users and guests
      • 2. Set up your projects and packages
      • 3. Plan your inspections and NOIs
      • 4. Follow up on action items
  • WHY NOTIFYME
    • Software benefits
    • Increase business process digitalization
    • Increase supply chain collaboration
  • KEY FEATURES
    • Collaborative workflows
    • Central data repository
    • Automated scheduling
    • Seamless communication
    • Dashboard, reporting and analytics
    • Data integration
  • ACADEMY PREVIEW
    • Academy videos preview
  • ADOPTING NOTIFYME
    • Set your goal
    • Plan the software adoption
    • Select your key users
    • Carry out a staged roll-out
    • Business use case (NOI management)
  • Pricing
    • Pricing plans
    • NotifyMe Professional Services
  • DATA SECURITY
    • NotifyMe Statement on Security
  • Release Notes
    • NotifyMe Release Notes
  • Restricted access
    • Password protected content
Powered by GitBook
On this page

Was this helpful?

  1. ADOPTING NOTIFYME

Carry out a staged roll-out

In order to validate the Roll-out model and processes, and to reduce the roll-out risk, it is recommended to carry out a staged roll-out. When possible, you should select a pilot site or department and carry out a preliminary roll-out on a limited scale.

Best practices with regards to the selection criteria of the pilot site or department are:

  • be representative of the rest of the sites or departments

  • be small scale (compared to the size of the final population)

  • bnable easy communication and access by the implementation team.

The reasons behind conducting a pilot roll-out may be:

  • Assessing the feasibility of large-scale implementation under certain conditions

  • Evaluating the impact of a particular roll-out model on project achievement

  • Demonstrating that roll-out can be implemented with existing resources

  • Develop a site that can serve as future model demonstration site

  • Increase stakeholder buy-in

  • Promoting consensus by showing how implementation can work

  • Lowers risk of failure by limiting resource usage

  • Assess true performance in controlled-but-live experiments

  • Quickly deliver a version of the solution to a targeted segment of the client population

  • Confirm or disprove expected results and relationships

  • To test and validate the benefit of the proposed solutions before final roll out

  • Validate the resources needed to effectively scale up roll-out

  • Identify additional improvements in either the solution or implementation launch itself

  • Improve future projections of benefits of full roll-out

  • Assessing the feasibility of large-scale implementation under certain conditions.

PreviousSelect your key usersNextBusiness use case (NOI management)

Last updated 4 years ago

Was this helpful?