Blogs

Lunch With a Leader: Chapter 3 – Nadia Leung

Welcome to Lunch with a Leader, where the Tech & Data People team sits down with IT leaders to uncover their career insights, challenges, and industry perspectives. Each conversation brings valuable lessons, trends, and advice to help our community grow and thrive.

Grab a seat at the table and take in the insights from some of the best in the business.


Nothing about IT project delivery is static, and that’s exactly why leaders like Nadia Leung – Managing Director of Tech on Track - are in such high demand. With clients pushing for faster outcomes, leaner solutions, and measurable value, she’s built a consultancy that thrives on agility, real-time visibility, and deep stakeholder alignment.


In this chapter, she shares how Tech on Track adapts to rapidly changing methodologies, why mindset still trumps tools, and how being accountable to your own brand name changes everything about the way you deliver.


Navigating Project Delivery in a Shifting Landscape


1. How does Tech on Track adapt to the rapid changes in IT delivery methodologies and client demands in project management? What do you have in place to keep up and adapt as things evolve?

Great question! AI has the potential to seriously shake up project delivery. Think better predictions, smarter schedules, and easier risk management.


But in Australia, it's still a bit of a mixed bag. While the tools are definitely out there, not everyone is jumping in. Many mid-sized businesses just don't have the resources to invest in AI at this stage - it's really the larger organisations who are leading the charge and seeing the benefits. Even when the tech is available, there’s still a skills gap. There just aren’t enough professionals with the expertise to implement and get the most out of AI tools in delivery environments.


So, in the meantime, many companies are turning to practical workarounds — tools like Monday.com and Zoho Projects are popular choices for managing schedules, risks, and issue tracking without the overhead of complex AI integrations.

We're also seeing a shift away from purist Agile. The reality is, full-scale Agile delivery just doesn’t fit every business. Smaller and mid-sized companies often aren’t structured or trained to adopt Agile in its strictest form — even if their delivery partners are Agile-certified, their clients often aren’t.


At the same time, clients are under pressure to deliver faster results and get more value for their investment. That’s where Tech on Track comes in — we offer flexible delivery models where clients only pay for the support they actually need, rather than locking in a full-time Project Manager they might not use.


2. How do you juggle delivering quick project wins while still keeping an eye on the bigger picture when it comes to IT strategy and infrastructure?

How I usually prioritise projects is by splitting them into two main buckets:

  • Quick wins
  • Long-term strategic initiatives


Quick wins give us fast outcomes, while the strategic projects focus on bigger-picture innovation. That balance helps make sure we’re not just ticking boxes in the short term but also building towards something more sustainable.


Agile really supports this approach. It’s designed to speed up time to value, while still giving us room to adapt and scale. Whether it’s two- or three-week sprints, the aim is always to deliver meaningful progress early.


It also gives clients a seat at the table when priorities shift. You might start with one focus, then a few weeks in, something changes. Agile gives us the flexibility to pivot without losing momentum.


3. With Tech on Track handling some pretty complex IT projects, how do you keep communication flowing smoothly and collaboration between different teams and departments, especially when you've got a mix of technical specialists working together?

When I start working with a new client, one of the first things I do is set up a clear communication plan. It’s about making sure everyone’s aligned on how we’ll work together — how often we meet, how reporting will work, and who to go to if something comes up.


I also make a point of connecting early with senior leaders across departments. Everyone has different priorities and preferences, even within the same organisation, so it’s important to understand what they care about and how often they want updates.


Having that broader view of organisational goals is key when managing complex projects. One thing we always focus on to keep things running smoothly is how we provide updates. We're always looking at tech to help us give those updates in real-time.


On a recent engagement, I implemented a project management tool that gave stakeholders real-time visibility across all active projects. Senior leaders could log in anytime to view a dashboard with the latest status updates, while project managers refreshed their reports every couple of weeks. Tools like Jira and Confluence are great for this — they allow us to centralise reporting so execs don’t have to sit through every meeting to stay in the loop.

More and more, we’re seeing that real-time reporting is crucial and expected. Everyone’s busy, and not everyone can make every meeting, so giving people on-demand access to the info they need has become a non-negotiable for project success.

4. How do you show clients the real impact of Tech on Track’s work? What are the key metrics you use to demonstrate the value you’ve delivered?

We track several key metrics, tailored for each organisation and project, including:

  • Project governance compliance (adherence to the framework)
  • Risk management effectiveness (number of risks mitigated)
  • Change control efficiency (timeliness of addressing change requests)
  • Team collaboration score (gauged via surveys)
  • Decision turnaround time.


We offer clients a selection of these metrics to align with their specific needs and translate project management concepts into their terminology.


5. Strong project delivery depends on collaboration. How do you build a culture of cross-functional teamwork, both within Tech on Track and when working with client teams, to keep projects on track and successful?

What really drives project success is knowledge-sharing and learning from past experiences. It's way more important than just being a tech whiz. A lot of organisations focus on hiring project managers with specific tool experience, like SAP or Microsoft Dynamics. But in reality, a great project manager knows how to apply lessons learned across different environments.


Where projects often come unstuck is culture and structure. Every company is unique, whether it has a formal PMO, an IT governance model, or something more ad hoc. It’s these internal dynamics, more than the technology itself, that tend to trip up delivery.


Projects usually fail because of fuzzy processes, unclear roles, or inconsistent ways of gathering requirements. If the people responsible for defining requirements aren’t equipped or supported to do it well, things can go off track before the build even starts. In the end, many delivery issues trace back to how the project was set up from day one.


6.  What advice would you give to someone who wants to take the leap and start their own consultancy?

It's seriously tough work. There's so much that goes on behind the scenes. I've been fortunate to leverage my talented network and have worked with innovative organisations like Accenture and Ericsson.


That said, I think more people should consider starting their own consultancies as there's a real need for it. When it's your name on the line, you work differently. For me, Tech on Track is my brand and I can't afford to have a project fail.


As a delivery professional, I'll work day and night to make sure it's a success. That's what clients are paying for. It's a different mindset. You bend over backwards, go the extra mile, and when it all pays off, it’s incredibly rewarding to make a project a success. There’s nothing quite like finishing a project and getting that positive feedback, it makes it all worth it.


Aidan Quieros

State Lead, VIC

August 20, 2026
A great technology job description does more than list responsibilities and technical requirements. It helps the right candidates understand the opportunity, see where their skills fit and decide whether the role is worth pursuing. In a competitive technology talent market, getting your job description right can make a significant difference to the quality of candidates you attract and how quickly you fill the role. Here are seven things every technology job description should include. 1. Start with the problem you're hiring someone to solve One of the most common mistakes in technology job descriptions is focusing too heavily on tasks and responsibilities. Instead, start with the business problem. What has created the need for this role? Is the organisation implementing a new platform? Scaling its cloud environment? Modernising legacy systems? Improving data capability? Delivering a transformation program? Candidates want to understand what they will actually be responsible for achieving. Instead of: "Responsible for developing and maintaining applications." Try: "You'll help modernise our core applications as part of a broader digital transformation program, working closely with product and engineering teams to improve scalability, performance and customer experience." The second version gives the candidate context, purpose and a clearer picture of the opportunity. 2. Separate must-have skills from nice-to-have skills Technology job descriptions can quickly become a wish list. Employers may ask for years of experience, multiple programming languages, several platforms, industry experience, specific certifications and a long list of tools...all for one role. The problem? Your ideal candidate may not exist. Before publishing the role, identify the capabilities that are genuinely essential to success. A more focused brief can open the talent pool without compromising the quality of your shortlist. Ask: What does this person need to be able to do from day one? Which technical skills are genuinely non-negotiable? Which skills could be developed once they join? Are we asking for experience with a specific tool when transferable experience would work? Would we reject an otherwise strong candidate because they don't meet one requirement? 3. Be specific about the technology environment Technology professionals want to know what they will actually be working with. Rather than simply saying "strong technical skills required", provide useful detail about the environment. Depending on the role, this could include: Technology stack Cloud environment Platforms and applications Programming languages Data architecture Development methodology DevOps practices Security environment Transformation projects underway You don't need to list every technology used across the organisation. Focus on the technologies that are relevant to the role and its objectives. 4. Explain what success looks like A strong technology job description should help a candidate understand what success looks like beyond simply completing their responsibilities. Consider including three or four outcomes for the first 6–12 months. For example: In your first six months, you will: Lead the migration of key workloads to the cloud Improve platform reliability and performance Establish improved monitoring and reporting Partner with internal stakeholders to define the next phase of the technology roadmap This gives experienced candidates something tangible to assess themselves against and helps employers attract people who are motivated by outcomes rather than simply a list of tasks. 5. Sell the opportunity, not just the organisation The best technology professionals are evaluating the opportunity too. A job description should answer the question: "Why would I want to do this job?" Think beyond generic statements about being a "fast-growing organisation" or having a "great culture". Talk about what is genuinely interesting about the role. The more specific you can be, the more compelling the opportunity becomes. Is there a major transformation underway? Will they have the opportunity to introduce new technology? Will they work with modern platforms? Will they have genuine influence over architecture or strategy? Is there a clear pathway into leadership? Will they work closely with senior stakeholders? Is the organisation investing in technology? 6. Don't make the interview process a mystery While this doesn't always sit within the job description itself, being transparent about the hiring process can significantly improve the candidate experience. If there are three stages, say so. If the role involves a technical assessment, explain what candidates can expect. If the hiring manager wants to meet shortlisted candidates within a particular timeframe, communicate that. Technology professionals are often managing multiple opportunities at once. A clear and efficient hiring process can help employers remain competitive once they have attracted the right people. 7. Get the salary and flexibility conversation right Salary and flexibility are increasingly important considerations for technology professionals. If you can provide a salary range, do it. It helps candidates assess whether the opportunity is relevant before investing time in the process and can reduce unnecessary conversations later. The same applies to working arrangements. Rather than simply stating "hybrid working", explain what that means. For example: "This role is based in Sydney with three days in the office and two days working remotely." Specificity builds trust and gives candidates a realistic understanding of the opportunity. A simple technology job description framework Before publishing your next technology role, make sure your brief answers these questions: The opportunity What problem are we hiring this person to solve? The impact What will they be responsible for achieving? The technology What platforms, systems and technologies will they work with? The essentials Which skills and experience are genuinely required? The environment Who will they work with and where does the role sit within the organisation? The opportunity Why would a strong technology professional want this role? The practical details What are the salary, location, working arrangements and hiring process? If you can answer all seven clearly, you're already much closer to a job description that attracts the right people.
Purple and blue neon light bars glowing over a reflective dark surface in a futuristic abstract scene
July 16, 2026
The latest Cloud DevSecOps trends explained: how security, automation and collaboration are changing the way modern technology teams build and deliver software.
Hand reaching toward floating notes and a glowing counteroffer card in a neon city scene; “We need you to stay” text.
June 29, 2026
Why do employees leave despite counteroffers? Explore the real drivers behind tech talent retention, from career growth to leadership and culture.
Purple-lit futuristic conference room with people working at glowing digital displays and holographic interfaces
May 8, 2026
As return-to-office incentives evolve, organisations are rethinking visibility, performance and fairness in hybrid work environments.
A digital world map made of glowing purple nodes and circuit-like lines on a dark, technical background.
April 8, 2026
Tech may be constantly shifting, but TDP recruiters know how to chart the path to the right talent.
March 19, 2026
What does working at Tech and Data People actually look like day to day? We asked Aidan to share his experience - what stood out, how he’s grown and what it takes to build momentum here. It’s a straightforward look at the environment, expectations and opportunities that shape a career at TDP . 1. What attracted you to Tech & Data People in the first place? I was immediately drawn to Tech & Data People because of the clear growth trajectory the business offers. It’s an environment where ambition is encouraged, development is prioritised and there’s a genuine opportunity to make a long-term impact. The combination of a strong vision and a supportive leadership team made it an easy decision. 2. What surprised you most once you started? Nothing in particular surprised me, but I was genuinely impressed by how supportive and collaborative the environment is. The office culture, along with the connection to our sister organisations - Design & Build and Public Sector People - creates a network of people who are welcoming, engaged and always willing to help. It’s a place where you feel part of something bigger from day one. 3. How would you describe the culture at TDP in three words - and why? Autonomy – You’re trusted to take ownership of your work and shape your own success. Trust – Leadership empowers you to make decisions and manage your desk with confidence. Care – There’s a genuine focus on people, both professionally and personally, which creates a healthy and motivating environment 4. What does a “good week” look like for you here? A good week is one where I’m actively picking up new roles, uncovering fresh leads, engaging candidates, scheduling interviews, and ultimately closing deals. It’s a balance of momentum, productivity and meaningful progress across my pipeline. 5. How does TDP support your growth as a consultant? TDP supports growth through a blend of autonomy, trust and care. I’m given the freedom to run my desk, the confidence from leadership to make decisions, and the personal support needed to continue developing both my skills and my career. It’s a structure that encourages independence while ensuring you’re never on your own. Our Head of People Development, Leanne Kemp , does a great job at keeping our knowledge and processes up to date too! 6. What’s different about recruiting in tech at TDP compared to other environments you’ve worked in? The biggest difference is the level of autonomy and trust. I’m empowered to do my job without unnecessary constraints, and leadership genuinely believes in my capability. Beyond that, the care extends well beyond the boardroom. There’s a real interest in my wellbeing and success outside of work, which ultimately strengthens my performance within it. 7. How would you describe the expectations here? Expectations are clear, transparent and aligned with the company’s broader goals. You always know what success looks like, and you’re given the tools and support to achieve it. 8. Who thrives at TDP? What Would you say to someone considering joining? People who are self-driven, resilient and eager to grow tend to excel here. Those who value autonomy, embrace accountability and enjoy being part of a collaborative team environment will find TDP a place where they can truly thrive. If you’re looking for genuine growth opportunities and a place that invests in your development, TDP is absolutely worth it.
By Kara Porter February 6, 2026
How many “unicorn” hires has your team lost in the past year? You know the type: the mythical full-stack engineer who codes, designs, manages projects AND mentors juniors - all without breaking a sweat. Companies spend months hunting for these elusive candidates, convinced that landing one will solve every team problem. Here’s the hard truth: unicorns are rare and chasing them often slows hiring, burns out teams and leaves critical projects stalled. Instead of relying on a single superstar, the smartest tech teams focus on building scalable, resilient teams. The kind where collaboration and complementary skills do the heavy lifting.
By Kara Porter January 13, 2026
The start of a new year is an opportunity to reflect, reassess and make intentional decisions about your career. For tech professionals, planning now can help you take advantage of opportunities, navigate emerging trends and advancing your career. This guide offers practical steps to help you consider, prepare and take confident action in the months ahead. Reflect on your career to date Review your achievements, projects and skills gained over the past year. Consider what worked well and what you’d like to change in your next role. Factor in responsibilities, team dynamics and company culture. Identify gaps in your knowledge or experience and set concrete goals to address them. Tip: Focus on showing how you apply your skills in real contexts. Link them to projects, roles and education to help hiring managers understand your impact. Suggesting clear examples and outcomes makes your profile stand out. Helpful resource: How to Highlight Skills on LinkedIn to Get Noticed (LinkedIn Business Talent Blog) provides tips on listing and structuring skills that attract recruiter attention. Understand the tech market Look at which areas of tech are hiring and in demand (e.g., data, cloud, cybersecurity). Track early hiring signals - new team expansions, company announcements, published salary guides or roles being filled quickly. Consider how your skillset aligns with market demand and where you could add unique value. Helpful resource: Stay up to date on tech hiring trends and market insights by following Tech & Data People on LinkedIn 
By Kara Porter December 17, 2025
The body content of your post goes here. To edit this text, click on it and delete this default text and start typing your own or paste your own from a different source.
Two glowing purple cyborgs in front of a futuristic city skyline.
By Kara Porter November 12, 2025
As AI shifts from experimentation to enterprise, businesses are rethinking what roles truly drive value. Discover how the next wave of AI talent is turning data into decisions.