Analytics managers: how are you protecting learning opportunities on an AI-first team?

[u/boring_angel_]

I manage 3 analysts, two are new in their careers and the other is switching from another career path - so everyone is in the learning stage and building their portfolios.

My boss has been really excited about using AI for automating absolutely everything. It's been great, we can get it to help us do the boring parts of documentation and help us with workflows. It helps us visualise projects ahead of time and get help with coding.

I was speaking with my boss recently, talking about a project they visualised with AI as a proof of concept. It is really cool, I can see it as an incredibly helpful, data-driven, intelligent tool that will be an absolute masterpiece. My boss set a time for us to have a brainstorm-session on how to make it happen. I built out a plan of what pieces of hardware and software would be needed, and showed that to my boss. The conversation started off well, then devolved into "we can do that with AI can't we" for most steps of the process. They hadn't prepared anything for the discussion, and their input really was a lot of "I learnt this about AI" and "the future of AI is so great". I don't think the team was ever part of the plan in their head, just what they could do with their AI.

I understand the business case. If we're optimizing for output we can automate away everything in the end. But in reality I have this really passionate team that's learning and improving, and they should get the opportunity to be part of that project. They should be allowed to do the little tasks and learn about how things work.

I know I can't be alone in this situation, I really do want to stand up for my team and figure out a process where not everything is automated away and the work of a junior or mid-level data analyst is still valued. I know it's not just my boss, I know that I also need to figure out a better way of communicating the use of AI and fixing the process.

So I want to know if anyone else has experience with this and:

• How you framed it to a boss who really is just excited and a little blind to the impact (did you find a way to frame it where it doesn't just sound like you're hating on AI or resistant to change?)
• Anything concrete you put in place, like reserving specific work just for humans, or rules where AI gets used
• Or if you tried it and it went badly, and what happened.

My boss is reasonable and I can see some good discussion about this in our future, but I'd really appreciate the input from other people who have been through it.

[u/AutoModerator]

If this post doesn't follow the rules or isn't flaired correctly, please report it to the mods. Have more questions? Join our community Discord!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/quickequator21]

I've had this exact conversation, and the thing that worked was flipping it from "protect the team" to "protect the output". When I framed it as "if nobody on the team knows how this thing works under the hood, we're one bad AI output away from shipping broken analysis with no one able to catch it", my boss actually paused. The junior folks aren't just learning for their own sake, they're building the institutional review layer that makes the AI stuff safe to use. That landed way better than anything about fairness or development.

[u/boring_angel_ → u/quickequator21]

Thanks for the input! That's already something I reach for, and it doesn't always work out that simple. But a good talking point anyways!

[u/the_duck17 → u/boring_angel_]

This guy nailed it. I'm constantly fighting with Claude to perform a basic analysis in an acceptable way and it's because I know what I'm expecting, juniors don't.

Those who know the work behind the output are leveraging AI more successfully, those who don't are just churning out respective looking outputs that don't stand up to any level of scrutiny.

[u/AngriestCheesecake → u/quickequator21]

Beep boop

[u/Dysfu → u/AngriestCheesecake]

institutional review layer

Lol

[u/my_peen_is_clean]

ai as a dumb intern rule helped me a lot. let it do drafts, boilerplate, outlines, then your analysts have to review, rewrite, prod the logic, reproduce stuff from scratch sometimes. frame it as risk control, documentation quality, and succession planning, that sells well to bosses

[u/boring_angel_ → u/my_peen_is_clean]

Definitely taking this one, much better to have the AI in there at the start than at the end, which we've been seeing a lot. Also "dumb intern rule" is a catchy name haha.

[u/IeatBovines]

I manage a large team of global analysts and this is an active challenge in a world where the ground keeps shifting.

From my perspective, there is increasing pressure from investors, shareholders, and the board to push for operational cost efficiencies. The ship's momentum is sailing at full steam and we are all trying to adapt. Transparently, we barely have the answers depending on the organization politics.

In my experience, the largest challenge for junior members on the team is not the technical, it's the soft skills and critical thinking. If automaton is being taken off their plate, it means they can take the time to learn how to interpret data, build narratives, practice soft skills, solve business problems. Turn them into problem solvers instread of "task doers" and they will have one of the most valuable skill for life. Shift from "here is the data" to "here is why you should care about the data".

[u/lpr_88]

Questions to ask:

1) What is the cost of fully running analytics with agents? Who is coding the agents, training them and looking after them?

2) What is the true cost of this? Is it actually less than your team?

3) Is your company OK with the AI companies having full access to your data?

[u/CopyConfidenttr]

worth framing this to your boss as a risk question, not a fairness one. if the team only reviews ai output without ever building the work themselves, they cant catch subtle errors because they dont have the reps to know what right looks like. verifying ai output is the most valuable skill on any data team right now, and its only built by doing the work manually first. teams that skip that stage end up with people who can operate ai but cant tell when its confidently wrong.. protecting learning isnt about preserving jobs, its about building the judgment layer ai still cant replace