When I finished my Data Analytics certificate, I faced a challenge that a lot of people hit after completing a course: taking polished theory and applying it to a real, open-ended project with no guardrails and no answers at the back of the book.

The Bellabeat Case Study became that challenge. And I used AI as a project partner throughout — not to generate my analysis, but to stress-test it, sharpen it, and make sure what I'd found actually came across in the final report. Here's an honest account of how that worked.

📊
The project
Bellabeat Case Study — Google Data Analytics Capstone
Analysis of 30 Fitbit users' activity, sleep, and heart rate data. Goal: identify which product feature Bellabeat should prioritise next, backed by data. Tools: SQL (BigQuery), R / tidyverse, Tableau.

The analysis itself — every line of code, every visualisation, every data cleaning decision — was mine. What AI helped with was the layer on top: making sure the insights I'd found were communicated as clearly and persuasively as the data deserved.

Three roles AI played — and what I actually asked it to do

01
Role one
Post-certificate instructor

After completing my analysis, I needed to know if my argument was strong enough for a professional audience. I used AI as a reviewer — not to tell me what to think, but to tell me whether what I thought was coming across.

My work
Completed analysis identifying new features based on user data patterns.
AI's role
Checked argument strength, data support, and final strategy against the brief. Confirmed the what but pushed me to improve the how.
02
Role two
Structural assistant

The most powerful help came in turning good analysis into a great report structure. My data showed two distinct user groups — a Majority Audience and a High-Risk segment — but I was treating them as separate findings rather than a connected argument.

My work
Identified the two user segments. Hadn't explicitly linked them in the executive summary.
AI's role
Challenged me to connect them. Helped draft a paragraph that turned a good finding into the central strategic justification for the entire project.
03
Role three
Final validator

Before finalising, I had a structural question: was it okay for my Key Findings section to contain mini-recommendations when my Executive Summary also had big-picture recommendations? I wasn't sure if that created confusion or useful layering.

My question
Does the two-level recommendation structure undermine the executive summary or support it?
AI's role
Confirmed the structure is ideal for multi-stakeholder reports. Findings give proof; summary gives mandate. That distinction gave me the confidence to leave it as designed.
The key finding — The Compensation Discovery
Users who slept badly trained harder the next day — not less
The data showed a clear compensation pattern: poor sleep was followed by elevated activity, not recovery. That finding ran counter to the original hypothesis and ended up validating a Burnout Prevention feature over a performance optimisation one. Every bit of that insight came from the data. AI helped me make sure the report made it impossible to miss.

The principle behind all of it

Looking back, there's a clean logic to how AI contributed at each stage — and a clear boundary it never crossed.

🧠
Mine
The thinking, the analysis, the insight
→
🤝
AI's role
The review, the structure, the communication
"AI served as a project manager of sorts — one that ensured my insights were communicated clearly, strategically, and with maximum impact. It took my raw analysis and helped me refine it into something a professional audience could act on."

Why this matters beyond one project

I tell this story because it's a concrete example of the kind of AI use that actually delivers value — and that's often missing from the conversation. The debate tends to swing between "AI wrote everything" and "AI is cheating." Neither captures what's actually useful.

What's useful is treating AI the way you'd treat a very capable colleague who has no context about your work, your client, or your goals — but who can give you honest, structured feedback the moment you bring them up to speed. That framing changes what you ask for, how you interpret the response, and what you do with it.

The output quality in the Bellabeat project was higher because I used AI at the right stage, for the right job, and kept the actual thinking where it belonged: with me. That's not a compromise. That's just good collaboration — with a new kind of partner.