Creating calm in complexity through data leadership

Leadership in data and analytics is not about having all the answers, it is about asking the questions others hesitate to raise, so teams can tackle the real challenges with confidence.

What's shifted for me over my leadership journey, is a greater willingness to surface assumptions early. Even if that means asking something that seems obvious. Misalignment is a far costlier problem than a moment of awkwardness.

From Engineering to Data Science: A Non-Linear Path into Analytics Leadership

My career has spanned automotive engineering in Canada, large-scale rail infrastructure projects in Melbourne and now senior leadership across more than 20 live tech, digital and analytics projects nationwide for data and digital analytics firm Notitia.

Like many others, my path into tech and data wasn't linear. I completed a double degree in chemical engineering and business management in Australia, with a master's degree in mechanical engineering in the United States, specialising in automotive systems. 

I had the option to continue my academic work or move into the workforce; I chose the latter - calibrating engines in Canada, before returning home to Australia to join Ford Motor Company.

At Ford, I moved from test planning into engine calibration (a rare skillset locally at the time). Later, I moved into rail infrastructure, working as a Risk and Systems Safety Assurance Officer on Melbourne's Level Crossing Removal Project and the Metro Tunnel.

Managing engineering risk across multi-company alliances sharpened my ability to navigate high-pressure technical environments.

In engineering, the fires don't take turns. It taught me to allow yourself a moment to acknowledge the situation. Then calmly take stock of where you are, what your options are, and move deliberately.

It was through my work in engineering that I identified where my interests truly lay - in the data. 

It sparked the motivation to complete a data science qualification (while working full time, studying one day a week on site and several nights a week) to formally pivot into analytics.

Servant Leadership in Technology: Removing Barriers So Teams Can Perform

Engineers are trained to solve problems in grey space with many unknowns. What drew me to data science was the thrill of solving a complex problem by getting genuinely curious, paying attention to details others might miss, and using tools to do in hours what would otherwise take years. 

But the work has to land somewhere real.
The answer needs to matter to someone.

That mindset now underpins my leadership approach at Notitia where I oversee a portfolio of complex analytics, reporting and digital projects across government and commercial sectors.

As Senior Analytics Manager, I'm responsible for delivery, balancing client expectations, technical capability, timeframes and resourcing across multiple teams.

I would describe my leadership style as "servant leadership" focused on removing barriers and ensuring my team has clarity from the outset.

What I found difficult, in the past, was the assumption that context didn't need to be shared. Without understanding the why behind a problem, you can only ever do part of the job.

To address this, I make a point of building that infrastructure from the start - clear documentation, timelines, defined communication channels. 

When people have what they need, they perform. 

And honestly, watching that happen, seeing the team at their best, hearing it reflected in client feedback, that's the best part of the job.

Why Early Problems Are "Cheaper" Problems

Translation is my greatest professional strength - identifying both the spoken and unspoken concerns in a room and guiding them to resolution.

With my background, I can understand the whole picture: technical roles, business pressures and client perspective. My job is to translate between them so everyone feels confident in what's being delivered.

In data teams operating under pressure, psychological safety is critical.

My team is always doing their best, that's something I genuinely believe. 

So when things don't go to plan, I want to know early. Not because I need to manage them, but because I'm in a position to help, and I really want to. 

Problems that get raised early stay manageable. As time passes, our options narrow. When people feel safe bringing problems forward, the whole team carries less weight - and small problems stay small.

What Quality Leadership in Technology Really Means

For those entering leadership in technology and analytics, closing information gaps is central to good leadership. 

The instinct is to explain what you know, but the better question is: what are they missing? I think of understanding like a puzzle. Good leadership is often identifying which piece someone needs and offering it to them. 

Over time, my own confidence has come from being willing to return to fundamentals.

When there's confusion or people can't agree, I go back to square one. Check the foundations, make sure everyone is working from the same understanding. More often than not, technical issues arise from flawed assumptions, not capability.

This approach - building context, creating safety, bridging perspectives - is not incidental to good technical leadership. It is what good technical leadership looks like.

On International Women's Day, I hope the conversation shifts beyond representation to the quality of leadership in technical fields.

Effective data leadership isn't about ego.

It's about creating calm in complexity, asking better questions and making sure what you create is genuinely useful to the people who rely on it.