We have outlined below the key roles and responsibilities to build your ‘Nelly Champions’ team to ensure your journey runs as smoothly as possible. Having this team in place is crucial and has brought lots of success to all our deployments
Roles:
Senior Stakeholder – A key person in ensuring Clever Nelly is launched successfully within your business. Essentially the sponsor of the project, this person will ensure the correct messaging is delivered throughout the business.
Operational Leaders – A critical role to be involved who help cascade and reinforce the message coming from your Senior Stakeholder to ensure each business area is clear on what is required. Your Account Director will ensure this population have the correct understanding and will run a designated session for this.
Project Lead – This person will remain the ‘constant’ during the deployment phase of Clever Nelly, keeping the project on track and ensuring all the correct stakeholders are involved and have insight during all sign-off points.
SMEs – Your Subject Matter Experts will play a crucial part of question sign-off, ensuring accuracy, relevance, and approval of content.
The following roles are optional in terms of being a ‘Nelly Champion’, however, it’s imperative that your Operational leaders or Project Lead has access to these areas.
L&D/Content owners – Similar to SMEs, your content owners should ensure that any content that is used to create questions from is signed-off and approved for authoring
IT Contact – You will require this person or team to take responsibility for implementing required whitelisting, ensuring emails can be received and questions can be delivered within your business. If you are deploying SSO, sftp file transfers or API links, IT will play an essential part.
HR Contact – Sometimes required to support with pulling user data for population of the Clever Nelly user load file. Doesn’t necessarily need to be part of the process but does need to be accessible by your Project Lead.
For more launch information, see our FAQs document here.