Using TestLogger as a team
TestLogger is a powerful data management and telemetry platform that enables teams to operate with higher discipline. By centralizing data like lap times, driver comments, and car setups, it empowers your team to analyze performance and make data-driven decisions.
Benefits using TestLogger
Imagine that you have run data like lap times, comments, and conditions from each team driver in the same table. Add setup sheets in a comparable format to the equation. This gives the team manager and drivers a powerful way to analyze and find trends to optimize setups by comparing performance data from runs.
Now let’s take this potential vision to the next level. What if all drivers had a Collector data logging unit in their cars, providing measured data like speed, throttle usage, and steering to really see and compare where the time differences come from? Imagine what a powerful tool you would have for drivers to improve driving and setups in an event where you have limited track time.
Or if you want to go very deep in the process, you can even have remote team members review data from each driver, provide comments, and drivers will receive real-time notifications for comments. This is exactly what TestLogger tools, like Manager, are designed for, and we are constantly developing the tools with the key principle in mind that systematic work and discipline bring results in the long term.
Challenges to handle
As usual, all good things typically have a price. In this case, getting things to work will require coordination and discipline from everyone in the team. It is an effort, but it will improve your team’s performance in the long run, even if you don’t use any tools. TestLogger makes it easier. Therefore, start easy and adopt the process in small steps. It is crucial to build a culture of recording information, staying consistent, and sharing data.
If the team or the drivers haven’t used TestLogger tools previously, it can be a big change to daily routines, so we recommend taking small steps to avoid disrupting performance in the beginning.
If things don’t work, then make small adjustments but don’t give up after the first, second, or third failure. This can take time before things work efficiently, and collaboration typically is challenging to get working in motorsport as people have a tendency to hide information. If you tackle this challenge, then everything else is much easier.
Steps to get started
Create a team
As a first step, you need to create a team in TestLogger Manager and invite the team members. You can only invite users who are already users in TestLogger.
This is the easy part and takes only few minutes.
At the moment all team members can see each others session data but can’t edit the data.
Check global assets
To get the most out of TestLogger Manager, you need to have the base set right. Global assets are global objects in TestLogger Manager that are available for all users. For example, check that the required car models exist and their setup sheet templates are available. Also check tire models and the tracks you regularly use.
Set your goals
Set your goal as a team. Where do you see the team within a certain timeframe? Racing is mostly about having fun and enjoying the hobby, but it doesn’t mean that you can’t set goals and work towards those goals together as a team. Setting goals and writing them down will give a reference for what everyone should expect.
Create the playbook
Playbook defines the team rules for common operations and helps aligning everyone to do the required things.
Decide what data to collect and when it’s collected for the team. The playbook should also define methods for how you communicate as a team.
Define data elements
Data means different things for everyone, so it is important to explicitly define what is expected. Below are items we consider the bare minimum.
Session with team visibility for the event
Run is created everytime car goes to track
Driver feeling/comment after the run
Comment what was changed in the car
Lap times
But there is more data available to choose from. These are important as well to understand what is really going on but can be introduced later after everyone is familiar with the process.
Setup changes
Debriefs
Logged data uploaded to TestLogger (requires Collector)
Tire info recorded to run
Conditions recorded to run
When to collect data for team
Data can be collected at different times, and it is important to set the expectation. For example, is it mandatory to collect data from races or tests? You might even want team members to collect it every time they go to the track, no matter if it’s a test or race.
Communication methods
Perhaps the most crucial aspect to gaining benefits is how to communicate as a team.
Decide if you run commenting system to provide feedback, group in messenging app to discuss or always go with meetings to give feedback.
It is important to keep debriefs so decide the template/agenda and when those are kept.
Learn how to use required functionalities in Playbook
Before you introduce the playbook to the team, train alone with TestLogger tools to learn how to use them, demo the playbook, and help drivers in the beginning.
It is recommended to utilise TestLogger Knowledge base to get more information but also just try it yourself in the tool. If you get stuck, the best place to get help is the TestLogger Discord server.
Review Playbook as a team
After you, as the Team Manager, are happy with the playbook, bring your team together and demo the playbook. Listen to the team for feedback and adjust it accordingly. It is super important to get everyone committed, so listen to the feedback carefully. Even though feedback is important, we don’t recommend creating the playbook with the whole team from scratch unless there are experienced drivers who know what’s required to achieve the goals.
Start working towards your goal
When you have the basics covered, the team should start collecting and inputting data according to the playbook. In the beginning it may require some supervising as people easily forget to do the new things. Based on experience, data need to be input in near realtime or otherwise it won’t get done or data is wrong.
After you collect the data, you do the debriefs and learn how to interpret and analyze the data. Make your observations, change the process, and repeat. The more you repeat it, the more streamlined and easier it becomes.
What’s next
Even though I have mentioned many times that this is hard, we hope you don’t feel discouraged. You may wonder if it’s worth starting. It does, and you should definitely try it! The feeling is great when you get your team working more consistently and gradually starting to bring the results. Just go for it and stick with the process!