Sydney, NSW — Open to enterprise data & AI leadership roles

Turning fragmented data into trusted, AI-enabled decisions — at enterprise scale.

12+ years building and leading data and analytics capability at Cisco. Evidence-led, not adjective-led: every claim below is backed by a number, a delivered outcome, or both.

62%→100%
Executive KPI consistency uplift
200+
Stakeholders protected by platform resiliency
5x
Self-service analytics data capacity for 1.75x the cost
$11M+
Investment decisions supported
$4.3M
Productivity savings across 34.4K employees
40%
Reduction in wasted AI token usage

Seven capabilities where I've delivered, not just advised

Click any capability for the story behind it.

Watch the 1-minute story. Voice-over by Natasha (AI voice), with captions.
Read the transcript

Nobody trusted the numbers. 70+ dashboards, 3-5 leadership escalations a month, and stakeholders double-checking every figure.

Patching dashboards wasn't going to fix that. So I split the team's effort in two: long-term strategic reporting, and self-service for ad-hoc requests.

Then we backed it with single-source-of-truth views, refresh schedules aligned to the warehouse, and tripwires to catch drift early.

Closing the trust gap took just as much work: plain-English data catalogues, dashboards with a clear narrative, agreed measure definitions, and data literacy sessions, so people could challenge the numbers.

The result? KPI consistency went from 62% to 100%, duplicate and end-of-life dashboards fell from 70+ to 46, escalations dropped to zero, and workspace health climbed from 60% to 93%.

It's held ever since, with tripwire alerts still watching for variance above 2%.

That's trusted executive KPI metrics.

A number of high-level service KPIs were telling different stories depending on who you asked.

Numbers spread across 70+ Power BI dashboards had drifted apart, generating 3-5 leadership escalations a month, and stakeholders had quietly stopped trusting any of them, double-checking every number before acting on it.

Rebuilding that trust meant more than patching dashboards, so I split the team's effort in two: long-term strategic reporting on one side, self-service for ad-hoc requests on the other.

  • Backed by single-source-of-truth views
  • Refresh schedules aligned to the warehouse
  • Tripwires to catch drift before it reached anyone's desk

Closing the trust gap itself took just as much work as the platform did:

  • Accessible data catalogues with plain-English explanations in a consistent template
  • Dashboards built around a clear narrative rather than a wall of numbers
  • Upfront agreement with stakeholders on how each key measure should be calculated
  • Data literacy sessions that empowered people to challenge the numbers instead of just accepting them

Within a short time, KPI consistency climbed 62% → 100%, duplicate and end-of life dashboards fell 70+ → 46, escalations dropped to zero, and workspace health rose 60% → 93%.

A result that's held ever since through the same tripwire alerts still watching for variance above 2%.

In early 2025, the IT support function was running lean, fewer support agents after company layoffs, while reskilling toward an AI-enabled support model, and it showed:

  • Case spikes were handled reactively
  • Executive leadership was often the last to know, hearing about problems only once they'd already escalated

This led me to develop a two-tier tripwire system based on standard deviations over six months of case trends, tuned tighter for operations and looser for executives, then led the development of an AI Assistant to summarise the essential pieces of information using prompt engineering techniques such as question refinement, cognitive verifier and few-shot examples.

We then surfaced these tripwire notifications up in IM chat – meeting where the user already is - and have it answer questions straight from a verified, business-ready SQL views.

Case-spike analysis went from half a day to near-instant, and the surprises between operations and executive leadership simply stopped.

Cisco's laptop refresh programme had always run on age, not evidence: three years and you're up for refresh, regardless of whether a device was struggling or still going strong.

That left asset management fragmented, budget handling inefficient, and refresh timing badly out of step with what users actually needed.

Rather than reach for the obvious generative AI answer, I ran a genuine build-versus-buy evaluation, supervised learning, GenAI, pure statistical thresholds, before landing on unsupervised anomaly detection:

  • No training data to maintain
  • None of GenAI's hallucination risk
  • A model that scaled naturally as the device landscape changed

Ranking real performance from CPU, RAM, memory pressure and disk telemetry, combined with app usage-based personas, it became the foundation for AI-enabled laptop performance scoring, an intelligent refresh decision engine and predictive stock forecasting, turning refresh decisions evidence-based and unlocking millions of dollars in potential savings.

Nine quarters, three phases: how Cisco's Data Solutions & Insights capability moved from reporting foundations, through AI-assisted analytics, to persona-based, AI-enabled decisioning.

View the full mapping ↗ Data Strategy & Evolution

When RAM costs rose and new supply tariffs pushed Apple's M5 MacBook Pro pricing up, every future Mac refresh using those models was set to get materially more expensive, a cost increase nobody had budgeted for and nobody had proven was actually necessary.

So I had the team quantify CPU and RAM performance across the entire Mac and Windows fleet, benchmarked it against the new M5 MacBook Air, and forecast the cost avoidance of standardising on the Air instead of the Pro.

The evidence made the decision straightforward:

  • 1.5x the performance of the M4 generation, double the M3
  • 23% less than the M5 14 inch and under half the cost of the 16 inch
  • Comfortably meeting the needs of over 87% of Mac users globally

Enough to make the Air Cisco's new standard on the spot.

As AI tools became part of daily work, the same signal kept showing up in laptop performance and app-usage data: a growing group of engineers and AI developers whose devices simply couldn't keep pace with what their jobs now demanded.

I used Python to analyse historical device performance, isolated the users with anomalous CPU and RAM growth, and cross-checked those spikes against the applications actually driving them, developer tools and IDEs with AI add-ons among them, before building the case for Finance with Power BI visualisations.

I didn't expect it to be approved on the spot, and it wasn't; the goal was to put verified evidence on Finance's radar early and keep advocating with that same evidence into the next financial year, rather than wait for the problem to force a rushed decision.

After the team migrated to Snowflake, we were constantly on the back foot.

Inconsistent changes to data tables triggered rework and re-deployments, and when errors surfaced in the KPIs stakeholders depended on every week, tracing them back through BI tools, transformations and source ingestion took far too long.

Made worse by external teams wanting direct warehouse access, which put over 200 stakeholders at risk every time credentials rotated.

I tasked the data engineers to rebuild around a DBT transformation and governance layer instead:

  • Data lineage for faster root-cause tracing
  • Data warehouse health KPIs alerting the team to ETL failure rates, unexpected ingestion volume changes and load duration
  • Cataloguing moved from Alation to DBT Docs
  • Every table change goes through development, peer review and automated tests to release, with full version history for troubleshooting

External access was replaced with secure AWS S3 data sharing, removing the disruption risk entirely.

Warehouse volume dropped 42% (355 to 205 tables/views), with 517.2M stagnant rows removed and disruptions down from 1-2 a quarter to zero.

The team's skill profile had grown around the old data ops model when powerful data warehouses and AI-infused tools didn't exist.

Analysts were valued for how fast they could turn around an ad-hoc request, spent too much time dashboard-building, and rewarded for describing a situation in numbers rather than building a case for what to do about it.

Speed was the metric. Actionable insights wasn't.

So I rebuilt the model around a different question: not how fast can we answer this, but how well-placed are we to answer the next ten questions like it.

That meant focusing less on building and defining calculations inside the dashboards themselves and more on:

  • Developing robust, custom SQL queries and ETL processes underneath them for dashboards and reports to simply consume
  • Deepening the team's advanced SQL and Python skills and data visualisation fundamentals along the way
  • Building for self-service so people could serve themselves instead of queuing behind an analyst

A stronger SQL layer changes what a team can build. It doesn't change how they work, so alongside it, I:

  • Coached analysts to build narratives that connect the dots and compel decision-makers to act, not just describe a situation in numbers
  • Understood what motivated each person, so the business got their best work and they owned their craft
  • Built and evolved a mission statement together with the team and stakeholders rather than handing one down

What grew out of it was exactly what the old model couldn't produce: a fragmented reporting function turned into a multi-year, AI-enabled analytics capability, focused on setting up self-service analytics for success and future-proofing our data operations.

A third of all data requests were simple enough that no one should have needed an analyst, yet they cost 512 hours of stakeholder wait time and $58K in lost productivity a year, pulling analysts away from the work that actually needed them.

I introduced ThoughtSpot as a self-service layer instead, built entirely on the same verified, governed datasets used for executive KPI dashboards, so speed never came at the cost of trust, then added Spotter as a natural-language GPT layer on top for forecasting and correlation analysis, with new users automatically enrolled in onboarding material from day one.

Adoption grew from 46 to 196 users (+326%), monthly queries from 8.1K to 19.2K (+137%), while the data team's own request workload fell 33%, freeing an estimated 738 hours and $68.9K a year for higher-value work.

ThoughtSpot ran as an internal shared service through Cisco's Data & Analytics Office, and as our user base grew across three other departments, that arrangement stopped making sense:

  • We were being cross-charged at a higher rate than dealing with the vendor directly
  • Administration depended on an internal support team with limited capacity that was slow to respond
  • The DnA Office wasn't upgrading to the latest ThoughtSpot version, so the newest technical and AI capabilities never reached us

Rather than keep absorbing that cost and lag, I partnered with other organisational data leads and went direct to ThoughtSpot's account management team to stand up our own instance.

Negotiating the contract terms and cost ourselves and agreeing to share that cost across the departments now using it, trading a shared service for one we owned and controlled outright.

That direct relationship put full administration and the latest capabilities in our own hands, and gave us the leverage to build the commercial case for a capacity uplift:

  • Switching to a $70K/250M-row option delivered 2.86x better value than the $40K/50M-row option
  • 65% lower cost per million rows
  • 5x the capacity for only 1.75x the cost

Back to top ↑

26 builds across Claude Code and ChatGPT

26 AI builds: 24 in Claude Code and 2 in ChatGPT, grouped into 7 categories. Each one shows when it was built, hands-on build time, how often it's used, and what it delivered and ran into, taken from session logs, run logs and output folders.

26
Builds: 24 Claude Code, 2 ChatGPT
~50h 15m
Claude Code build time (ChatGPT not recorded)
~2h 06m
Average per Claude Code build
20 vs 2
Success vs failures: running vs issues being addressed (3 in development, 1 not set)
92 · ~9h 35m
Claude Code uses and total run time

Back to top ↑

From a business problem to a KPI dashboard

Five AI agents at work with a human in the loop carrying the end-to-end KPI development process on generated test cases.

Each agent has one job, a persona and a clear handover. Select an agent to jump to their focus page. Headshots are AI-generated.

Agent Simulation

A replay of each run, timed from the recorded save and commit times. Pick a project, then watch each agent work, hand over and pass its gate.

Project

Back to top ↑

Token Reduction Journey

Reducing token usage while meeting business objectives and output for each run of the KPI Creator.

By agent (millions)

Ovy: 487.8M487.8M
ClearCompare
  • Ovy487.8
Ovy: 78.6MGary: 11.5MKewpie: 9.5MViktor: 9.5MJennifer: 12.6MStakeholder: 1.8MOther: 1.0M124.4M
Kestrel Medical
  • Ovy78.6
  • Gary11.5
  • Kewpie9.5
  • Viktor9.5
  • Jennifer12.6
  • Stakeholder1.8
  • Other1.0
Ovy: 44.5MGary: 5.5MKewpie: 12.2MViktor: 34.7MJennifer: 20.2MStakeholder: 0.6MOther: 1.0M118.6M
Lumenwire Audio
  • Ovy44.5
  • Gary5.5
  • Kewpie12.2
  • Viktor34.7
  • Jennifer20.2
  • Stakeholder0.6
  • Other1.0
Ovy: 20.5MGary: 2.8MKewpie: 8.6MViktor: 14.8MJennifer: 8.2MOther: 0.8M55.7M
Base to Build (Live run)
  • Ovy20.5
  • Gary2.8
  • Kewpie8.6
  • Viktor14.8
  • Jennifer8.2
  • Other0.8

One dot is 1M tokens. Dots are the same size in every run, so a bigger circle means a bigger run.

Back to top ↑

From Visual Arts to enterprise AI at Cisco

One constant thread, from a Visual Arts degree to enterprise data leadership: turning complex things into something other people can understand and act on.

Jun 2019 – Jul 2026 · 7 yrs
Data Solutions & Insights Lead / Product Owner
Cisco, Sydney

Led a global, multidisciplinary team of analysts, data scientists and engineers, building Cisco's enterprise data and analytics capability into a trusted, AI-enabled decision-making function.

Jun 2017 – Jun 2019 · 2 yrs
Lead Analyst
Cisco, Sydney

Took on Cisco's first dedicated data leadership remit, laying the groundwork for the Data Solutions & Insights function that followed.

Jul 2012 – Jun 2017 · 5 yrs
Senior Business/Data Analyst
Cisco, Sydney

Built the hands-on reporting, analysis and stakeholder relationships that the Data Solutions & Insights capability would later be built on.

Sep 2011 – Jul 2012
Data & Reporting Analyst
Dept. of Innovation, Science & Research, Canberra

Analysed research data from 42 universities to support the accurate allocation of $1.64B in government research grants.

Mar 2009 – Feb 2010 · 1 yr
Project Officer
Australian Competition and Consumer Commission, Brisbane

First step into data and reporting itself, redesigning processes across the Product Safety Group to cut duplication and improve transparency.

Apr 2007 – Mar 2009 · 2 yrs
Chief Corporate Trainer
Procter & Gamble, Osaka

Designed and delivered communication skills programs across P&G Japan and South Korea, including assessments used in employee promotion decisions.

Feb 2006 – Apr 2007 · 1 yr
English Instructor / Course Developer
Lado International College, Osaka

Designed courses and coached students one-to-one, translating advanced material into something a mixed-ability class could actually use.

Aug 2002 – Feb 2006 · 3.5 yrs
Assistant Trainer / Branch Manager
Nova Group Japan, Osaka

Spent three and a half years teaching, coaching and eventually managing a branch, learning to make complex material land with people who didn't yet understand it.

2001
Bachelor of Arts, Visual Arts
Australian National University, Canberra

Where it started: learning to observe, interpret and communicate meaning, years before any of that met data.

Back to top ↑

What I bring day to day

Leadership & strategy

  • Data & analytics strategy
  • People leadership
  • Roadmap prioritisation
  • Stakeholder engagement
  • Executive storytelling

Insights & decisioning

  • Insights-led commercial outcomes
  • KPI frameworks
  • Forecasting & trend analysis
  • Predictive / prescriptive decisioning
  • Executive data storytelling

Data product & enablement

  • Data product ownership
  • Agile backlog management
  • Self-service analytics
  • Jira Cloud / Align

AI, governance & platforms

  • Prompt engineering & tokenisation
  • AI-enhanced analytics & AI assistants
  • Data quality, privacy & governance
  • Snowflake / DBT — SQL / Python
  • Power BI / ThoughtSpot / Tableau

Back to top ↑