Enate Implementations
Last updated
Was this helpful?
English
Last updated
Was this helpful?
This document is an explainer for anyone involved in the Solution Discovery and Solution Design phases of an Enate implementation.
The Solution Methodology activities start at the beginning of your first Enate implementation project, or at the start of each of the subsequent projects. There are two parts to the methodology:
Solution Discovery & Scoping – Covered in a single 2-4 hour workshop with key stakeholders and the sales team.
Solution Design – A one or two day workshop per team to design a solution that works for them. This design Phase is split into 6 sub-sections.
This is a critical ‘pre-step’ where the scope of the deployment is defined. This stage will normally be led by sales and project sponsors. We’ve called this Phase 0 because sometimes it is completed during the initial sales / engagement process.
Once you’re happy that scope is appropriately defined coming out of Solution Discovery (Phase 0), we move on to the various phases of Solution Design. This is the point where a wider group of stakeholders become involved, i.e. representatives of people actually doing the work in scope day to day, like Team Members / SMEs. The six phases of the Solution Design are:
1. Understanding the Work – This is where you understand the work carried out in the scoped business and collate this into a single Unique Work List. Subsequent phases then use this work list as the basis for all questions & information gathering.
2. Variance – In this phase you’ll look to understand what in the real world causes the work to vary. For example, we will explore whether the work is done in different countries or for different customers, and if these have an impact on who needs to do what work when. The key output of this phase is knowing how many factors work varies BY, and what they are. The specifics of how the activity varies is NOT a key point to record here that is picked up in the build phase. Knowing what things vary BY allows you to decide how to use Enate’s unique features for managing variance.
3. Work Visibility (Permissions) – In this phase we are answering the question ‘Who is allowed to see what work?’. Note: Creating silos like this should only be designed in on an exception basis – the assumed starting in this phase will be that everyone should have permissions to see everything, even if they might never actually DO that work or see it in their Enate user interface day to day. With this understanding we will decide how to use the permission features in Enate.
4. Allocation – In this phase you will be understanding the skills in the organisation and how those skills map to work. Just like in Phase 1 where we created the Unique Work List, in this phase we will define the Unique Skills List. We will decide how to use Enate’s features to allocate work to people and digital workers.
5. Data – In this phase you will identify the different types of data which need to be supported as part of the Enate solution. You will decide how to handle communication data (like emails and call notes), how to manage files and how to manage key data required for reporting, searching and automation. You will be deciding whether to manage this data in Enate and if it is in Enate, then what features will be used to manage it.
6. Manage Quality – Here you identify if there are any key quality check / feedback loop activities for each of the items on the work list, and what Enate features you will use to ensure this is supported.
Once solution design is complete, the design is then used in the BUILD phase. That’s the point where we actually build the solution, directly into the Enate platform. This activity would ideally be a focused one where a small number of Enate Builders (citizen developers) work through the solution discovery & design information compiled in phases 0-6 working directly with Subject Matter experts as they build.
This solution is then set up in Enate in the ‘Build Phase’ where Enate is configured for the team to go live (Build Phase activities are not covered in this document - See the section for information on how to build your process solutions in Enate Builder).
See the section for information on how to build your process solutions in Enate Builder.
