DiscoverAI at Work
AI at Work
Claim Ownership

AI at Work

Author: Neil C. Hughes

Subscribed: 12Played: 88
Share

Description

What does AI really mean for the modern workplace, and are we ready for what comes next?

AI at Work is a podcast from the Tech Talks Network, the home of conversations that showcase the voices at the heart of enterprise technology. You may know me from Tech Talks Daily, where we explore a different area of innovation in every episode. This show takes a focused look at one of the biggest shifts in business: how artificial intelligence is transforming the way we work.

From intelligent automation to agentic AI and from the promise of workplace efficiency to the risks of unintended consequences, we aim to provide a grounded and accessible perspective on how AI is shaping the future of work.

If you’re using AI in your business or thinking about how to get started, this podcast is your chance to learn from the people already doing it.

64 Episodes
Reverse
What happens when AI changes the work long before a company changes the job description?In this episode of AI at Work, I speak with Vishnu Shankar, Chief Data Officer at Draup, about a workforce problem that is easy to miss when the public debate remains fixed on jobs being created or removed. Vishnu argues that the faster and more immediate change is happening inside existing roles. Tasks that once took days can now be completed in minutes, but people must verify outputs, understand faulty systems, recognize changing naming conventions and apply the judgment that a model lacks.That is why Draup describes many skills as facing partial obsolescence. SQL, data modeling and similar capabilities do not suddenly become worthless. Their place within the role changes. At the same time, new AI requirements are appearing inside customer support, sales, marketing and software engineering roles. Vishnu says Draup's analysis of Fortune 500 employment data found that dedicated AI roles were growing only marginally, while demand for AI skills within existing roles rose far faster. He also describes increasing skill density, with some software engineering positions asking for 19 skills where 14 may previously have been expected.We discuss why this creates problems for traditional reskilling. Comparing two static lists of skills misses the context in which each skill is used and ignores how the destination role is changing. Vishnu proposes starting with tasks instead. Leaders should identify what AI will automate, what it will support and what continues to require human effort. Only then can they determine which skills a person needs and whether an adjacent career route is realistic.The conversation also turns to capabilities that rarely appear in workforce systems. Communication, for example, is too broad to assess as a single skill. In an HR role, it may mean conducting a difficult performance conversation, challenging a senior stakeholder or running a calibration meeting where managers defend their ratings. Evidence of those abilities may live in project records, manager feedback, review discussions or systems such as Jira rather than in a conventional employee profile.For leaders, the governance question is equally important. Vishnu believes workforce transformation should be led by the CHRO, supported by the CIO's technology roadmap and informed by the CFO's budget authority. He calls for an automation register that records what was automated, where the work previously sat and what replaces it. He also argues that headcount planning becomes less informative when AI changes how much one person can produce. A capability portfolio offers a clearer view of what the organization can actually deliver.We finish with a direct challenge to employers. Training catalogs, completion records and certificates do not prove capability. People need protected time during the working day, practice using real work with real consequences, and a credible route into a named role or family of roles. Work simulations can then test whether employees apply the skill, use the available tools and catch planted errors. Vishnu also explains how unrealistic experience requirements, overloaded job descriptions, slow hiring processes and weak compensation can all be mislabeled as talent shortages.Is your organization measuring the number of people who completed AI training, or whether those skills are appearing in the work they produce? Share your thoughts and experiences with me.
Can a finance team trust an AI answer if the systems underneath it disagree about what revenue, cost or performance actually mean?In this episode of AI at Work, I speak with Matej Trbara, co-founder of Farseer, about the foundations required to use artificial intelligence in financial planning and analysis. Finance teams are being asked to forecast faster, model economic uncertainty and provide answers while decisions are being discussed. At the same time, many of those teams continue to reconcile data across ERPs, BI products, warehouses, planning systems and large collections of spreadsheets.Matej begins by defending Excel. He describes it as a programming platform for people who are not programmers, which helps explain why it remains so deeply embedded in finance. A user can start with a blank sheet, add numbers and formulas, and build a model that reflects the way a business operates. The difficulty begins when that flexibility is stretched across an enterprise. Hundreds of contributors may change structures, formulas and definitions before a finance team attempts to combine everything into one report.This leads to the central argument of the episode. According to Matej, finance often has a data problem before it has an AI problem. Definitions can drift between systems, actuals require reconciliation and different teams may work from different versions of the financial model. Adding AI to that environment can magnify existing inconsistencies rather than correct them.Farseer’s approach separates the natural-language interface from the calculation engine. Matej says AI should translate a request, such as asking for a sales variance analysis, into machine instructions. The company’s Rama database then performs deterministic calculations against a governed financial model. AI reasons over those results, while the user can trace an answer through each level and return to the original system of record.We also discuss how this model changes forecasting and scenario planning. Annual or quarterly forecasts can become outdated quickly when tariffs, energy prices, wars and market conditions affect a business. Matej describes a move toward monthly and continuous planning, where new actuals update the model, responsible people receive a notification and a human either approves the result or adjusts the plan. Farseer estimates that AI-supported workflows could reduce the cost of producing a forecast by between ten and one hundred times. That is a company estimate, but it gives finance leaders a concrete claim to test against their own process.Another practical example comes from board reporting. Matej says some clients now use Farseer AI Analyst during meetings to answer questions that were not anticipated in the prepared deck. Instead of promising a response several days later, finance can question the live model, inspect suspicious results and continue the decision while everyone is in the room.The opportunity is faster planning and greater access to financial analysis. The challenge is resisting the temptation to let a language model become an ungoverned calculator. Could your finance team explain where every AI-assisted number came from, and would that answer survive the scrutiny of the board or auditor? Share your thoughts with me at Tech Talks Network.
If your organization switched off its AI systems tomorrow, would customers, employees or the finance team notice any meaningful difference?In this episode of AI at Work, I speak with Frank Böhmer, founder and CEO of Ninox, about the growing gap between AI activity and measurable business value. Companies can count tokens, prompts, users, copilots and prototypes, but those numbers mainly reveal participation. They do not show whether a customer issue was resolved faster, an audit passed, an error rate fell or a team handled additional work.Frank argues that token consumption is a particularly weak proxy for success. An organization would never judge an employee by the number of meetings attended or the number of words typed into email. Paying attention to how many tokens people consume creates a similar incentive. The CFO wants an operational result, not proof that a model stayed busy.That distinction becomes important as natural language tools make software creation available to people who could not previously build applications. Frank sees genuine value in vibe coding because it reduces the cost of experimentation. Someone can describe an idea and create a convincing prototype in hours. The difficulty begins when that prototype meets the operational world.A production application needs reliable data, authentication, role based permissions, testing, integrations, audit logs and clear ownership. It must continue working as the organization grows, regulations change, employees leave and processes evolve. Frank suggests a more demanding question than asking whether an application can be built in an afternoon: can the company trust it three years later?We discuss where developers fit when AI can generate interfaces and basic code. Frank believes experienced developers move toward architecture, security, integration, data modeling and the consequences of design decisions. Plausible output can conceal incorrect assumptions and forgotten edge cases. As the volume of generated software grows, businesses need people who can distinguish a durable design from a shortcut that only works today.The same reasoning applies to process automation. Automating each step of an inefficient workflow can create a faster inefficient workflow. Frank encourages teams to reconsider the process using the capabilities now available. If AI can bring the right information to the employee immediately, some handoffs, searches and approval steps may no longer be required.For leaders assessing an AI project, Frank offers both a rigorous method and a simple test. The rigorous version begins with a baseline covering process time, cost, errors, delays, people involved and the final outcome. The company then compares those measures with the AI supported version. The simpler test asks what would happen if the agent were switched off tomorrow. If the business barely notices, the project may be an experiment rather than an operating capability.We also revisit shadow IT. Business teams create their own solutions because central IT can never satisfy every request within the available time and budget. Banning creation will not remove that demand. Frank recommends an approved environment where employees can build quickly while identity management, security, backups, auditability and deployment remain under organizational control. This changes IT from the team expected to build everything into the team that provides the safe foundation.Should leaders celebrate wider AI adoption, or reserve the word success for the moment a process becomes measurably better? Listen to the episode and share your thoughts with me.
In this episode of AI at Work, I speak with Rohan Kodialam, co-founder and CEO of Sphinx AI, about the difference between an AI system that sounds capable and one that understands how a business defines truth. Sphinx AI describes itself as an AI research company building human-interpretable context graphs that can support agents across different models and enterprise systems.Rohan argues that consumer AI can feel impressive because many everyday questions are supported by information in the public domain. The situation changes inside a company. Questions about customer churn, product performance, acquisition costs, or operational efficiency depend on definitions, assumptions, and working practices that belong to that organization. A model may reach the data through an enterprise connector and still lack the knowledge needed to interpret it correctly.The most revealing example comes from a retailer using a metric called revenue per store. One team divided revenue by every store in the estate. Another used only stores that were open on the relevant day. Both definitions were reasonable for their intended users, but an AI relying on retrieved documents could select one almost at random and return an answer that looked convincing. The error might remain hidden until somebody compared it with a manually prepared report.Rohan says the problem can be resolved by making the missing business context explicit. In this case, the AI needed a short explanation describing both definitions and when each should be used. It could then consider whether the request came from a real estate or operations user and select the relevant metric. This is a small example of a much larger enterprise problem: the information that separates a useful answer from a costly mistake often lives in people’s experience rather than a formal system.We discuss why retrieval augmented generation can struggle when company material is raw, contradictory, or unsynthesized. Rohan reports that Sphinx AI customers have seen accuracy increases of roughly 35 to 40 percent on existing enterprise benchmarks after curating context, with larger improvements in some cases. These are company observations rather than independent benchmark results, but they show the size of the gap Rohan believes a dedicated knowledge layer can address.Context also changes. Rohan references an example in which an agent reportedly moved from 95 percent accuracy to 65 percent within a month because business processes and priorities had changed. His argument is that companies need context stewards who can review updates, approve definitions, reject unauthorized changes, and maintain an audit trail. He compares this with code review, where machine-generated work still requires accountable human oversight.Security remains part of the design. Rohan says a context layer should explain what information exists while respecting role-based access controls. It should sit virtually above existing systems of record rather than copying sensitive data into a new repository. An agent might know that customer phone numbers exist while remaining unable to retrieve them. It can then tell the user that permission is required instead of inventing an answer or bypassing an established control.Before allowing an agent to act on company data, Rohan recommends two forms of testing. Business experts should create a small gold-standard set of tasks they know well, while the company can build a broader benchmark from repeated work already visible in its operational history. Together, these tests can show whether the agent understands the decisions people actually make rather than performing well on a generic demonstration.Does your organization have a shared, reviewable account of how it defines its most important metrics, rules, and working assumptions? Listen to the episode and share your thoughts.
What should a finance leader be able to prove before giving an AI agent permission to act?In this episode of AI at Work, I welcome Danny Fields, Chief Technology and Customer Operations Officer at Avalara, for a conversation about the distance between a convincing AI pilot and a finance workflow people can trust. We discuss the appeal of faster execution alongside the evidence, controls and business ownership needed when software begins making decisions or recommending actions.Avalara's research provides the starting point. Its global survey of 1,505 CFOs and senior finance leaders found that 92% felt career pressure to demonstrate AI agent ROI, while half reported limited measurable returns. Respondents came from businesses already deploying, piloting or evaluating agents, so these findings describe a particular group rather than every finance department. What interested me was the tension between pressure to demonstrate progress and the work required to make that progress defensible.Danny argues that copying an existing process into an AI workflow can preserve the problems already inside it. He describes why controlled pilots can struggle when production introduces incomplete records and unpredictable inputs. We consider what it means to redesign the workflow, measure accuracy over time and judge value through risk, audit preparation and business outcomes as well as hours saved.We also discuss accountability. Danny's view is that responsibility stays with the team that owns the business outcome, supported by documented roles across finance, compliance, IT and legal. Permission boundaries, recorded approvals and tested incident response become part of the operating model. A CFO may not need to understand the mathematics behind a language model, but should understand what information an agent uses, what it can do and when a person takes over.The conversation closes with a practical test for expanding autonomy: can the business demonstrate value, sustained accuracy, clear ownership, appropriate access and controls that reflect how agents actually work? These are Danny's recommendations, rather than a guarantee of compliance or financial performance. Please share your thoughts with me. What would your team need to see before trusting an AI agent with a consequential finance decision?
loading
Comments