Project overview
In week 11 of training, I took on the role of project manager for our client project. Going into the week, I was nervous. It felt like a lot of responsibility knowing that if anything went wrong, it would ultimately sit with me. To manage that, I leaned heavily on the advice we had been given in training, particularly around preparation. I spent time getting ready for the kick-off call, creating a master document, researching the client, and preparing questions in advance. That preparation helped settle some of the nerves and gave the week a clear starting point.
Taking on the project manager role felt very different to previous projects. Up until this point, I had always had a clear technical task to focus on. This time, my role was about setting direction, coordinating the team, and understanding the project as a whole, while still engaging with the client. I also found the client-facing side more daunting, as it required confidence not just in the work, but in how I communicated decisions and progress.
The experience
At first, not having a defined technical task felt strange. However, as the week progressed, I realised that working from a more ‘outside’ perspective actually helped me understand the project better. Having that overview allowed me to see how everything fit together and focus on leading and supporting the team rather than getting caught up in individual tasks. I found that I enjoyed this balance, particularly being able to guide the work while still staying close enough to understand what was happening.
One of the biggest shifts during the project was fully understanding the consulting side of our role. It was not just about analysing data or building dashboards, but about remembering that we are data analytics consultants. The project reinforced that our role goes beyond analysing data and instead focuses on helping clients think more clearly about their goals and how data can be used to support better decision-making. Being slightly removed from the build helped this click for me, as I could focus more on the ‘why’ behind the work rather than just the output.
Leading the team was also a learning experience. By this point in training, it was our fifth project together, which made a big difference. I trusted the team’s ability to deliver, which allowed me to avoid micromanaging. I focused on listening, setting a clear schedule, making quick decisions when needed, and staying flexible. I found that leading worked best when I adapted to how people naturally work, rather than forcing a rigid structure, while still being firm when decisions had to be made.
Reflections
The client was extremely pleased with the final output, particularly given the short timeframe. The project showed them what is possible to build and explore in Tableau and how useful clear visualisation can be when working with their data. For me, this project felt like a strong demonstration of our consulting skills and a step forward from simply meeting a brief to genuinely adding value.
Overall, this experience helped reinforce my confidence in handling client work and trusting my judgement. It reminded me that leadership is not about having all the answers, but about preparation, listening, making informed decisions, and supporting others. As I move into future projects and placements, I feel more confident taking on responsibility, asking for help when needed, and approaching client work with a more consultative mindset.