Using TestLogger as a team

TestLogger products give you great possibility to improve your team performance by sharing data and requiring drivers to use systematic approach to their testing and races.

What this means in practice? Imagine that you have run data like laptimes, comments and conditions from each team driver in same table. Add setup sheet in comparable format to the equation. This gives the team manager and drivers powerful way to analyse and finding trends what to do with setup just based on comparing meta data from runs.

Now let’s take this potential vision to new next level. What if all drivers would have Collector in the car and you have the measured data like speed, throttle usage and steering from each car to really see and compare where the time differences come from? Imagine how powerful tool you would have for drivers to improve driving and setup 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 person(s) to look the data from each driver, comment the data and driver will get real time notification for the comments.

As usual, all good things typically have a price. In this case getting thing to work, it will require coordination and discipline from everyone in the team, but that is not a bad thing as that will improve your teams perfomance in long run even you don’t use any tools. Therefore start easy and do it small steps. It is crucial to build the culture to mark down the things, being consistent and sharing info. If the team or the drivers haven’t used TestLogger tools previously, it can be a big change to the daily routines so recommendation is to take in small steps to not to disturb the performance in the beginning..

What next?

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.

Set your goals

Set what is your goal as a team

Set the playbook and instruct team members

• Decide what is the minimum data to input. Here are some proposals where you can choose from.

  • Session with team visibility for the event

  • Session team visibility for team test days

  • Run

  • Driver feeling/comment after the run

  • Setup changes

  • Laptimes

  • Logged data

  • Tires

  • Conditions

• Agree if team will provide feedback to run comments or is the system just collect things together.

• Keep debriefs after each or session if possible.

• Debriefs should always follow same agenda.

• Write these in to Manager Notes.

• Communicate play book with all team members. Everyone needs to commit to it.

If things don’t work, then do small adjustments but don’t give up after first, second or third failure. This is not easy and collaboration typically is challenging to get working in motorsport. One big reason for it is that people don’t want to share info/data. If you tackle this challenge then everything else is much easier.