It's crucial to have a deployment strategy to make this journey smooth. Here are four decisions to be made at this early stage.
For this phase, some decisions need to be made, which may involve all or part of your beta testers. The following governance decisions may impact the end-user experience and will simplify the choices you will need to make at that later date.
As a winning strategy, we recommend postponing large-scale governance and security conversations after you have completed your initial experimentation with Timeneye.
Here is what you need to focus on at this stage:
Decision 1: Who can create teams
It is time to decide who will be involved in this pilot and their role. List the core stakeholders and business leaders in your organization who have expressed an interest in this initiative. For everyone, ask the following questions:
Who is the most suitable candidate to participate in this limited business onboarding?
Has this individual (or group of individuals) shared an ordinary work situation that might be a good use case for this first phase?
Do they have enough interest from employees in their organization to be early adopters and give you meaningful and regular feedback?
Decision 2: Group naming conventions
You will likely want to implement some naming conventions for your broad deployment of Timeneye and check for duplicate names. In Phase 2, we suggest you implement a manual naming convention for your initial projects only. The best practice for this is to create Groups in Timeneye that reflect as much as possible the departments in your company (ex: Admin, HR, IT, Sales, Marketing, etc.)
Decision 3: Integrations
Check out the full list of integrations.
Depending on your use case and other apps used in your organization, you may include additional apps as a part of your controlled experiment. Be sure to vet any third-party apps to ensure they adhere to your organization’s security and compliance requirements.
Decision 4: Length of your experiment
To evaluate a successful Timeneye deployment, it is important to give the end users the right amount of time to learn, experiment and give you feedback in return. Therefore, we recommend you give the experimentation phase 1 or 2 months to ensure the onboarding is completed and the employees get used to the new working habit. At the same time, the experimentation phase should be brief because the corporate-change program might never start and get forgotten.
Generally speaking, small to medium organizations could use the free 30-day trial period, rather than bigger companies opt for a pilot (2 to 6 months) because they require a longer time to complete a proper rollout.