Why AI Won't Replace Your Job But Will Change How You Do It | Allison McMillan / Tavlin Consulting

04-Aug-2026 by Allison McMillan Read Time: Approx. 7 minutes

Why AI Won't Replace Your Job But Will Change How You Do It

So many conversations these days revolve around AI... even when we know there are lots of other things to talk about. In almost every conversation I have these days, whether it's with CTOs, nonprofit Executive Directors, fellow fractional executives, team managers, or ICs, AI is truly the next frontier in that it's changing so much about the world around us. And with that comes lots of questions, fears, concerns, and new decisions we're making every day so I thought I'd start by writing about what I think is changing and how to think about all of these new AI tools and capabilities.

Even though AI tools have been around for a long time, in the past couple of years, generative AI has become much more accessible to the general public. The tools that allow us to interface with artificial intelligence and its ability to effectively create new works significantly change what we can utilize AI for and WHO can utilize AI. As with most things, the more people that adopt this new technology, the more known it becomes as well. People pass along ideas of what they're doing and how they're doing it. People build tools and workflows that are open sourced so that everyone can use them. And in today's world of being able to get so much information so quickly, not only through the internet, but via multiple streams of social media and communication, the proliferation of AI ideas, approaches, and how-tos are nonstop. And all of this constant information coming our way does two things. First, it creates an incredible hype cycle because of course I would love an army of agents to run my business for me (and on the surface, that looks reliable, doable, cheap, and easy to do). Second, it creates a massive sense of FOMO (fear of missing out) and it looks like everyone else is so far along with using AI and AI tools so you want to be there too, experimenting, utilizing the latest and greatest. And finally, that mix of hype and FOMO feed directly into our fears and concerns. What will happen to our jobs? What industries will AI replace? How will it affect our marketability, the economy, and lots of other aspects of our current day-to-day life in the next 10 years?

And realistically, from my perspective, it's a bit of all of it... everything is changing, but it's also ok. This piece came out a few months ago and I saw it passed around in almost every space I am in, from non-technical to technical, from nonprofit to corporate, but with a variety of reactions. Some people read it and got scared, others nodded their heads because they've been seeing exactly this in the spaces they work in, and others said certainly this piece is fear-mongering and we're no where near this level of change. Change is hard.

Here's what I truly think is changing: mostly, the parts of our work that feel tedious, time-consuming, and unenjoyable are outsourceable now. It is becoming much easier to accomplish more, especially related to the types of work or tasks you need to do that YOU are slower at. For different industries and functions, this means different things. It CAN be things that people consider core to their jobs - coding, strategy planning, marketing, growth messages, etc. And at the same time, for every person who has those tasks as a core part of their role, there are five people who need to do those things but it's NOT the core of their role. There is a key question here of what can AI do better than I can, and that's going to be different for different people. It's NOT a one-size-fits-all answer.

And also, for some people, there are core parts of their role that make sense for AI to do, but that doesn't mean their role is obsolete. I'll talk about software engineering for a moment because I think that functionality is changing the most and has the most pressure to change right now. It is becoming more and more apparent that having AI write code is the way to go. I know that's a tough statement for many people who love to craft their code, and who haven't seen great output from AI when it codes, but it's becoming more and more true. HOWEVER, this isn't a blind prompt of telling AI to build a specific feature. Before that happens there are so many steps: understanding any codebase patterns or styles that need to remain consistent, planning what the code will look like and choosing the right approach (which involves both understanding and asking the right questions about tradeoffs, gotchas, or other issues), understanding scale and security implications, making the codebase one where AI can effectively create code for it, and then once the code is written, doing a thorough code review and spending time understanding what the code is doing (trust me, you'll want to spend a little bit of extra time here so you're not doing...