Once everybody completed the onboarding process, you should see your colleague's names and avatars appear on the Dashboard. From the Teams section, you could monitor their real-time usage and eventually allocate an hourly budget to each of them for more accurate profitability calculations.

Despite the process of tracking time is very easy, some people might find it hard to get into the routine. Leave at least 1 to 2 weeks, depending on the company size, for everybody to get acquainted with the new software. Also, you could set automatic reminders and recap emails for your employees.

Make the necessary adjustments

In the first few weeks of usage, some issues might emerge, so make sure to address them promptly and make the necessary adjustments to your workspace.

If necessary, consider organizing a video demo with your champions and streamlining all potential friction points or simply gathering feedback on this experience.

In case of a technical issue or to request a feature, please contact us at [email protected]

Gather feedback with a quick survey

Towards the end of your trial period (1 or 2 months), send out a survey to your team in order to gather more insights about this experience.

A good survey should be quick: no more than 2-3 minutes to complete. Most of the questions should be closed questions and maybe leave some open questions to give the opportunity for a more elaborated answer on complex topics.

Before starting, list the survey’s goals and write down some questions according to those objectives. We can provide you with an example of an end-of-the-trial survey, but we would recommend using it as a starting point for more tailored research.

If you have never used one before, there are plenty of survey tools on the internet (some are free), like Microsoft Forms, Google Forms, Typeform, Hubspot, and SurveyMonkey.

Allow one full week for everybody to complete the survey. When you have a good response percentage, start analysing the results. What went well and what didn’t? What’s the overall reaction? Is there anything that could be fixed or improved before the org-wide deployment?

For example, in case one of the recurring types of feedback is that there wasn’t enough training before starting using Timeneye, you could consider organizing more video demos, for smaller teams, with smaller chunks of information and more often.

This is an example of a precious insight that will save you from a bigger headache down the road.

As a final step, we advise you to create a document with all the insights you could gather from this survey and organise a meeting to present it to the stakeholders. Together, you could decide on the actions to take to streamline the whole process.

Did this answer your question?