Why do increasingly capable AI models struggle to produce reliable answers inside large organizations?

In this episode of Tech Talks Daily, I speak with Misti Vogt, SVP of Engagement at Orange Logic. Her career spans military intelligence, data science, and enterprise content technology, and she also teaches in the DAM and AI program at Rutgers University. That combination gives her an unusually practical perspective on how machines interpret information and why business meaning cannot be assumed.

Misti argues that enterprise AI reliability depends on the context surrounding company data. A model may be technically impressive, but it needs to understand relationships, rules, metadata, rights, and intent. Without that layer, it reasons over information originally organized for people rather than machines. The result may sound convincing while remaining disconnected from the way the business defines accuracy, trust, and permitted use.

We discuss three forms of context. Static context reflects accumulated knowledge. Transactional context develops through projects and outside information. Semantic context helps systems interpret meaning and relationships across large collections of information. Misti compares this with human conversation. When an answer misses the point, we add information until the other person understands what we mean.

Digital asset management sits at the center of this discussion because DAM platforms already organize master data, metadata, transactional data, governance, relationships, and usage rights. Misti believes those structures can give AI applications a stronger business foundation. She also argues that content should become self-aware, carrying information about when it was created, how it was produced, its intended audience, where it has appeared, and how it has performed.

Natural language search provides a useful example of why this matters. An employee might ask for creative assets suited to a campaign and welcome a broad set of suggestions. The same employee may then ask for assets licensed for the United Kingdom and United States, with print and web rights for the next 12 months and no use in another campaign during the previous six months. That second request carries business consequences, so the system needs deterministic rules alongside creative choice.

Misti also shares an Orange Logic customer example involving a conglomerate with several brands. The company consolidated seven platforms, including three DAM deployments and local storage. Orange Logic then supported shared governance across the group while preserving autonomy for individual brands. Misti says the early results include time savings, improved efficiency, richer metadata collection, and lower costs, although no quantified figures were provided in the recording.

The wider question is whether businesses are spending enough time on the information surrounding their content before expanding AI use. Could better metadata, rights management, and business logic produce greater value than another round of model upgrades?

Listen to the conversation and share your thoughts with me.

What if every market research project could continue contributing to business decisions after its original question had been answered?

In this episode of Tech Talks Daily, I'm joined by Phil Ahad, Managing Director of Data at Cint, to discuss why he believes companies should move away from disposable research. For decades, the familiar model has been straightforward. A business asks a question, commissions a study, receives the answer and begins again when the next question appears. Phil argues that this process wastes useful information and repeatedly asks people for details that may already be available.

His alternative is an always-on human data engine that allows new studies to build on previous research. Existing responses can be combined with first-party information, third-party sources, transactional records and behavioral signals. Phil says this can help organizations answer new questions faster while reducing the burden placed on respondents.

That burden matters because survey fatigue is often misunderstood. Phil does not believe people have stopped wanting to share opinions. The problem is the experience. Customers are repeatedly asked long batteries of familiar questions, often after everyday transactions, because the structure of data collection has changed remarkably little since paper surveys. If researchers already know much of the background, they can ask fewer questions and focus on the reasons behind a person's decision.

We also examine synthetic data, a term Phil openly dislikes, and the growing use of AI personas or digital twins. At one end of the spectrum, a model might add 200 modeled responses to an 800-person study so researchers can work with a sample of 1,000. Phil says this extends an existing data set rather than creating genuinely new insight. At the other end, a company may create a digital representation of a person from survey responses, purchasing patterns, mobile activity and other signals, then ask that representation new questions.

The opportunity is faster research with less repeated questioning. The risk is believing the model knows a person better than the evidence allows. Phil says the industry must test how much information is required to predict an answer with an acceptable level of confidence. He expects progress to come from repeated comparison and validation rather than a single certification method or technical shortcut.

For business leaders, this makes transparency as important as speed. Before relying on AI-augmented research for a major decision, they need to understand where the original data came from, how modeled responses were created, how performance was tested and where human judgment remains involved. Phil also notes that strong decisions rarely rely on a single input. Companies bring together research, customer records, benchmarks and other sources before deciding what to do.

Cint's ambition, as Phil describes it, is to turn recurring tracking studies into a continuing source of insight. He says roughly one million people pass through the company's ecosystem each day, giving Cint an asset that can be combined with increasingly accessible technology. The larger challenge is making useful sense of growing data volumes at business speed.

Could continuous research help your organization ask people fewer, better questions, or would AI-generated responses introduce uncertainty that outweighs the speed gained? Listen to the episode and share your thoughts with me.

What would change if your building could help explain what needs attention, why it matters, and whether the action you took actually worked?

In this episode of Tech Talks Daily, I welcome Bert Van Hoof, CEO of Willow, back to the show to discuss operational AI for buildings and infrastructure. Bert spent about 20 years at Microsoft, where his work included launching Azure Digital Twins. He now works with environments such as hospitals, airports, universities, corporate campuses, and data centers, where the condition of a physical space can directly affect the work happening inside it.

We begin with a problem familiar to many facilities teams. Buildings already have sensors, management systems, meters, maintenance records, and dashboards. Having access to information does not necessarily help an operator decide what to do next. Bert describes operational AI as a way to move through a sequence of questions: what is happening, why is it happening, what might happen next, what should we do, and did the action produce the expected result?

Context gives those questions meaning. A temperature reading alone cannot tell us whether a room is operating correctly. We need to know the room's purpose, occupancy, equipment, weather conditions, and recent maintenance history. Bert explains how digital twins and knowledge graphs connect those relationships so that a system can assess the situation rather than interpret a sensor value in isolation.

The discussion then turns to predictive maintenance. A probability of failure may be useful to an analyst, but a technician also needs to understand the consequence, urgency, and next step. Bert describes how condition-based maintenance can support equipment decisions and how earlier detection can reduce the disruption caused by refrigeration problems or water leaks.

These are practical examples of the types of outcomes Willow targets, rather than a claim that every customer will achieve the same result.

There is a human side to the conversation too. Bert describes operators opening numerous browser tabs each morning to assemble a picture of their buildings. Daily briefings and natural-language questions could reduce that search effort, helping teams focus their attention on the issues that deserve it.

We also discuss the relationship between occupancy, ventilation, energy consumption, comfort, and maintenance. Bert describes Willow's Active Control and the use of schedules and occupancy signals to help buildings respond to how spaces are being used. His argument is that these decisions should account for the whole environment. Saving energy in isolation can create different problems if comfort, reliability, or safety is overlooked.

Trust runs through the interview. A poor recommendation in a hospital has different consequences from an awkward paragraph in a document. Bert argues for explainable recommendations, operational evidence, defined limits, and verification after an action. He also sees experienced facilities engineers as part of the solution, with responsibility for setting objectives and judging trade-offs.

For me, the larger question is how building operations connect with the organization's purpose. A hospital needs spaces and equipment ready for patient care. An airport needs to account for passengers, flights, gates, and changing demand. Understanding the environment means understanding what it needs to support.

Where would operational AI make the most useful difference in your buildings, and what evidence would you want before allowing it to take action? Please listen and share your thoughts.

What happens when attackers can discover and exploit a weakness faster than your organization can patch it?

Recorded at Barracuda TechSummit 2026 in Alpbach, Austria, this conversation features Arve Kjoelen, CISO at Barracuda. Arve is responsible for protecting Barracuda's systems, environment, and code, which makes him the person answering the familiar question of who checks the checker.

Our conversation begins with the collapse in response time. Security teams once had hours or days to investigate suspicious activity. Arve explains why they may now have minutes or seconds, while vulnerabilities can move from disclosure to exploitation within days. Traditional weekly scans and handoffs to patching teams struggle when attackers operate at machine speed.

Arve offers a useful framework for understanding security posture through threats, exposures, assets, and controls. Technology changes constantly, but these categories give leaders a way to assess risk without chasing every new term. He also explains why reducing attack surface can begin with basic questions. Does a system need to be accessible from the internet? Does a web server also need remote management exposed? Does a midsize business benefit from spreading its workloads across every major cloud provider?

We examine the difficult balance surrounding AI adoption. Blocking every new tool can prevent employees from benefiting from useful technology, but allowing unrestricted adoption creates new exposure. Arve argues for deliberate choices and guidance that reduce risk without stopping progress.

The conversation also addresses AI-guided remediation. Barracuda uses AI internally to identify vulnerabilities, but Arve is cautious about fully automated fixes. An AI system may identify a problem and suggest a solution, while a human remains responsible for judging whether the proposed action could damage a production environment. Faster decisions are valuable only when organizations understand the consequences.

Arve also considers how entry-level technology roles may change as AI performs more coding and analysis. His view is that people will need to understand how to work with AI, evaluate its output, and carry an idea from design through secure implementation. The role changes, but the demand for human judgment remains.

We finish with model sovereignty, data trust, and provider dependency. If a security capability relies on one AI model, leaders need to know whether they can move to an alternative if access, performance, pricing, or policy changes. Arve also explains why Barracuda is preparing to support both open and closed models while the market develops.
Where should your organization use AI to accelerate defense, and which security decisions should remain firmly under human control? Listen to the full conversation and share your thoughts with me.

What happens when artificial intelligence moves beyond helping marketers create content and begins making decisions on their behalf?

Recorded at Forge 2026 in Las Vegas, I speak with Astha Malik, Chief Business Officer at Braze, about how AI is changing customer engagement and what marketers should retain control over as more operational work is handed to software.

Astha explains why the long-standing promise of genuine one-to-one personalization has been so difficult to deliver and why she believes AI can finally help brands move beyond broad segments toward individual decisioning. We discuss Decisioning Studio Go, where AI can optimize content, timing, and frequency for different customers, while marketers continue to define the objectives and brand boundaries within which the system operates.

But greater automation creates new questions. If AI can generate more campaigns and messages, does marketing simply become noisier? Astha talks openly about the danger of "AI slop" and why using the same models and tools can make brands increasingly forgettable.

We also discuss Agentic Standards and the idea of AI checking the work of other AI systems before campaigns reach customers. Astha argues that organizations need controls around agents in much the same way they already have quality processes around human teams.

Our conversation also moves beyond marketing into the changing enterprise software interface. Operator Connect allows Braze capabilities to be accessed through environments such as ChatGPT, Claude, and Microsoft Copilot, raising questions about whether employees will increasingly interact with business systems through AI assistants rather than traditional applications.

Finally, we examine how organizations can prove AI is creating measurable value, why some businesses remain trapped in experimentation, and Astha's advice for leaders overwhelmed by the pace of change.

Her recommendation is simple: start experimenting rather than waiting for certainty.

As AI takes on more decision-making and execution, which parts of marketing should remain firmly in human hands? Listen to the conversation and share your thoughts.

How should a business measure AI success when employee adoption tells leaders very little about revenue, savings, risk, or better decisions?

In this episode of Tech Talks Daily, I speak with Thomas Robinson, better known as T-Rob, who recently moved from Chief Operating Officer to CEO of Domino Data Lab. After ten years inside the company, he has seen enterprise AI move through several phases, from specialist data science projects to generative AI tools available across the workforce.

T-Rob argues that businesses have become too focused on the technology itself. Generative AI has attracted attention because almost anyone can use it, but an individual productivity tool is very different from an AI system making decisions about mortgages, clinical trials, financial markets, or defense operations.

As the potential value of a decision rises, so does the financial, regulatory, and operational risk. That is why T-Rob believes governance should be built alongside AI development rather than added after a system has been completed.

He compares the process with constructing a building. Engineers do not wait until the work is finished before checking whether it has been designed and assembled correctly. Reviews happen throughout construction. Domino applies the same principle to AI through policy controls, production monitoring, tracing, and continued human oversight.

We also discuss why companies should avoid beginning with a fashionable tool and searching for somewhere to use it. T-Rob recommends starting with the company's primary business measures and working backward. A pharmaceutical business may examine the number of promising therapies entering its pipeline, revenue, and risk. The appropriate AI system can then be designed around those outcomes.

That system may combine large language models with computer vision, statistical models, rules, and company data. T-Rob believes the assumption that every business problem requires the latest frontier model can waste money and produce weaker results.

People remain a major part of the equation. T-Rob has seen companies reduce headcount in anticipation of AI replacing employees before the technology was ready. He argues that domain experts become more valuable because they understand the business history, operating environment, exceptions, and consequences that a model may miss.

The conversation also considers model independence and AI sovereignty. Many enterprises became dependent on a single cloud provider by building their own technology on proprietary services. T-Rob believes businesses should avoid repeating that decision with AI models. Open systems can allow companies to replace models as prices, capabilities, regulations, and operational needs change.

For organizations handling sensitive intellectual property, sovereignty also raises questions about what information leaves the business when employees prompt external models. T-Rob describes the risk of enterprise knowledge being absorbed into future model development, even when information has been anonymized.

Perhaps his strongest argument concerns measurement. He calls consumption and adoption terrible measures of success because they mainly reveal cost. Giving every employee an AI tool does not mean the entire company becomes proportionally more productive. Real return comes from improving the business processes that generate revenue, reduce expense, control risk, or support better decisions.

Are businesses ready to stop measuring AI by logins and start measuring what it changes inside the company?

Listen to the episode and share your thoughts.