Episode 05 · August 21, 2026 · 53 min
Why This CIO Says AI Will Never Take Your Job (But Might Take Your Task)
With Amel Edmond, Chief Information Officer at Withum
Amel Edmond, CIO at Withum, traces a path from taking things apart as a kid to running technology at a professional-services firm. Along the way he draws a clean line between automating a task and replacing a job, and another line between a manager and a mentor.
What you’ll take away
- AI replaces the task, not the job.
- A manager assigns work. A mentor tells the truth.
- Cybersecurity is a business reality. Human error is not optional, so culture is the control.
- Stop asking if you will be tested. Prepare for when.
In this conversation
- AI and the shape of IT work
- Mentorship versus management
- Cybersecurity as culture
Episode recap
Editorial summary of the conversation, not a verbatim transcript.
Host Bob Hansen welcomed Amel Edmond, the Chief Information Officer (CIO) at Withum, to The Technology Vanguard to discuss his unique career trajectory, leadership philosophy, and the rapidly evolving landscape of artificial intelligence and cybersecurity.
Edmond traced his roots as a technologist back to his early childhood, recalling how, at four or five years old, he would dismantle his father’s clocks and, later, an expensive VCR, just to figure out how the machinery connected. This innate curiosity eventually led him through engineering school, the military, the legal sector, and finally to his current role at Withum, where his background in cybersecurity and infrastructure helped him ascend from head of infrastructure to CIO.
When Hansen asked about the evolution of his leadership style, Edmond contrasted his early experiences with his current mindset. At twenty years old, steeped in military ROTC culture, leadership meant strictly following the orders of a lieutenant or major. Over time, that military mindset evolved into something more supportive. Edmond noted that true leadership was about being a mentor and an advocate who showed the right way, rather than merely dictating tasks. He emphasized that this supportive guidance highlighted the core difference between managers and true leaders.
Edmond stressed that mentors could be found anywhere—from family members and college professors to early career bosses who built NT servers. He added that mentors did not always have to be older; he frequently gained valuable insights by consulting junior technologists and staff accountants. Early in his career, a mentor taught him that while raw intellect was enough to get hired, soft skills were mandatory for advancement. As Edmond phrased it, intelligence was great to get in the door, but being strategic helped him stay in that door.
Hansen prompted Edmond to share a moment of doubt or struggle, leading Edmond to recount a grueling network conversion project in a data center. Facing a tight 24-hour window, the team worked deep into the night. By 2:30 or 3:00 a.m., Edmond saw his team running on fumes, surviving on coffee and nearing burnout. Instead of letting them rest and tackling the problem the next morning, he pushed forward, relying too heavily on his own individual intelligence rather than trusting his team's limits. He decided to handle a heavy server himself, which he ended up dropping. That single mistake extended a 24-to-36-hour migration into a 72-hour ordeal, costing the organization significant money. The failure taught him a vital lesson: even if one could do a task alone, the real question was whether they should, and that pushing a fatigued team was a recipe for failure.
When asked about the worst advice he ever received, Edmond offered two examples. The first was the cavalier IT phrase, "It's okay to restart it, what's the worst that can happen?" The second was the blanket advice to "trust your team" without the crucial caveat of verifying the work. Edmond explained that heavy lies the crown, and relying on unverified, inaccurate information from a team ultimately fell on the executive's shoulders. Conversely, his best advice was about surrounding oneself with the right network. "They're like buttons on an elevator," Edmond remarked, noting that the people in one’s circle could either bring them up or pull them down.
Hansen then pivoted to Edmond’s written thoughts on AI, specifically referencing his LinkedIn articles on AI strategy. Edmond clarified that AI was not a replacement for headcount; rather, organizations wanted to use AI to make their current staff ten times more productive. He described a concept he termed "work slop"—the mundane, repetitive administrative tasks that bogged down IT departments. Edmond explained that AI was perfectly suited for automating "work slop," such as standardizing user onboarding, generating IT accounts, or managing the logic for shipping laptops based on local state regulations. However, he warned against letting AI handle highly sensitive data autonomously, stressing that a system should never autonomously route payroll or disability information.
Edmond further discussed his concept of "AI without atrophy," warning against the erosion of human judgment. He noted that if a junior developer used AI to generate code that looked visually correct but was fundamentally flawed, the developer still needed the underlying expertise to catch the error. Edmond argued that organizations needed a "human in the lead" rather than just a human in the middle, ensuring that critical thinking did not atrophy as tools became more advanced.
Touching on the intersection of AI and cybersecurity, Edmond acknowledged extreme concerns in the industry. He pointed out that AI platforms had been restricted due to their potential to aid hackers in launching sophisticated attacks. Looking toward the horizon, Edmond warned of the coming era of quantum cryptography, which would have the power to decrypt data at unprecedented speeds. He cautioned that layering quantum capabilities with AI effectively equated to building "Skynet."
Despite these looming threats, Edmond expressed immense pride in his own team's cybersecurity culture. He shared a story about testing his staff by plugging a USB drive loaded with questionable applications into his work laptop. Almost immediately, the security team locked down his computer and his entire account because a specialized hacker tool spun up and initiated wireless network sniffing. They had detected "Jack the Ripper," a notorious password-cracking tool. The incident proved his team was hyper-vigilant, treating the CIO with the same strict protocols as any other user. Edmond proudly stated that his infrastructure team stayed toe-to-toe with the biggest threats in the industry.
Wrapping up the interview, Edmond offered advice on strategic IT planning. He advised against planning further than five years out due to rapid technological shifts. Instead, he recommended focusing on large "boulders"—deploying a major platform like Workday one year and a CRM the next. He warned against trying to push five boulders simultaneously, as it would inevitably cause change fatigue, break systems, and burn out the staff.

