Over the course of this series, I’ve explored how Oracle Fusion AI Agent Studio is changing, why the Builder Assistant matters, the building blocks that sit behind Agentic Apps, and some of the design principles that can help organisations create meaningful solutions. Throughout all of those discussions, one theme has consistently emerged. The technology itself is only part of the story. What’s really interesting is where this might lead.

Whenever a new technology appears, there’s a tendency to focus on what it can do today. That’s understandable. Organisations want to understand the practical use cases, the risks, the costs and the potential benefits before investing time and effort. But sometimes it’s worth stepping back and thinking about the broader direction of travel. When I look at Agentic Apps, I don’t see another reporting tool, dashboard framework or application development platform. I see the beginnings of a different way of interacting with enterprise software.

For most of the history of business applications, software has been built around transactions. An employee updates their details. A manager approves a request. A finance team processes an invoice. A procurement specialist creates a purchase order. Applications have traditionally been designed to help users complete specific tasks as efficiently as possible. There’s nothing wrong with that approach. In many cases, it’s highly effective.

However, organisations today are dealing with increasing levels of complexity. Decisions are rarely based on a single transaction. They often require information from multiple systems, multiple teams and multiple business processes. This is where I think Agentic Apps become particularly interesting. Rather than simply helping users complete a transaction, they have the potential to help users navigate an entire business outcome. That’s a very different objective.

One of the ideas I find most compelling is the shift from process-centred thinking to journey-centred thinking. Take something as common as onboarding a new employee. Traditionally, onboarding spans numerous activities across HR, IT, Facilities, Security, Payroll, Learning and line management. Each team plays an important role, but the overall experience is often fragmented because it spans multiple systems and processes. From the employee’s perspective, however, there is only one journey. The same principle applies to customer experiences, supplier management, project delivery and countless other business activities.

We tend to organise systems around organisational structures. People experience them as journeys. Agentic Apps have the potential to bridge that gap by bringing together information, actions and communications from across multiple processes into a single, outcome-focused experience. Instead of asking users to navigate organisational complexity, the technology could increasingly help manage that complexity on their behalf.

Many of today’s business challenges don’t fit neatly within departmental boundaries. Employee retention isn’t just an HR issue. Supplier performance isn’t just a procurement issue. Project success isn’t just a project management issue. The factors influencing those outcomes often span multiple teams, multiple data sources and multiple business processes. This is where traditional applications can sometimes struggle. Each application does its job well, but no individual application has visibility of the complete picture.

Agentic Apps offer the possibility of bringing those perspectives together. Imagine a manager being able to view workforce data, project commitments, learning progress and performance indicators in a single context when making a resourcing decision. Imagine procurement, finance and supply chain teams working from the same set of insights when managing a critical supplier issue. Imagine employees receiving support that reflects their entire journey rather than the individual processes sitting behind it. The technology is still evolving, but the direction feels increasingly clear.

One challenge I hear repeatedly from customers is that the pace of business continues to accelerate whilst organisational complexity continues to increase. There are more systems. More data. More regulations. More stakeholders. More expectations. The result is that people spend an increasing amount of time gathering information and coordinating activities rather than focusing on high-value decision making.

I don’t believe Agentic Apps will eliminate complexity. Business will always be complex. What they can potentially do is make that complexity easier to navigate. Rather than expecting individuals to manually bring together dozens of signals from across the organisation, an Agentic App can help surface what matters, explain why it matters and support the next action. In many ways, that feels like the natural evolution of enterprise software. For years we’ve focused on capturing information. The next phase may be helping organisations make better use of it.

Of course, technology alone isn’t enough. One thing I’ve learned from years of transformation programmes is that successful adoption rarely depends entirely on the software. Culture matters. Leadership matters. Governance matters. Trust matters.

Organisations exploring Agentic Apps should be thinking about these areas now. How much autonomy should agents have? Which decisions require human approval? How will recommendations be reviewed and governed? How will users understand and trust the outputs being generated? These questions are every bit as important as the technical architecture. In fact, I would argue they’re more important.

The organisations that achieve the greatest success with Agentic Apps are unlikely to be those with the most sophisticated technology. They’ll be the organisations with the clearest understanding of where AI can support people whilst maintaining appropriate governance and accountability.

Whenever discussions turn to AI, there is often concern that technology will replace human expertise. Personally, I don’t think that’s where the greatest opportunity lies. The most valuable decisions organisations make often require context, judgement, empathy and experience. These are qualities that remain fundamentally human.

What Agentic Apps can potentially do is reduce the amount of time spent gathering information, navigating systems and managing administrative tasks. That creates more time for the activities people are uniquely good at. Leading teams. Building relationships. Solving problems. Managing change. Making informed decisions. If organisations approach Agentic Apps with that mindset, the conversation becomes much more constructive. It stops being about replacing people and starts being about helping people be more effective.

Perhaps the thing that excites me most about the future of Agentic Apps isn’t a specific feature or capability. It’s the possibility of making enterprise software feel more human. For years, users have adapted to systems. They’ve learned processes, navigated menus, searched for information and worked around organisational boundaries. Agentic Apps have the potential to reverse that relationship. Instead of people adapting to software, software can increasingly adapt to people. It can understand context. It can bring together information. It can help guide users towards better outcomes. That’s a powerful idea. And whilst we’re still in the early stages of that journey, I think we’re beginning to see what that future could look like.

When I started exploring Oracle Fusion AI Agent Studio, I expected to spend most of my time learning about agents, prompts, workflows and integrations. Those things are important, and they will continue to evolve rapidly over the coming years.

But the more time I spend with these capabilities, the more convinced I become that the most important conversation isn’t about the technology itself. It’s about outcomes. It’s about helping organisations deal with increasing complexity. It’s about helping people make better decisions. And ultimately, it’s about creating experiences that feel less like software and more like support.

Whether you’re just starting to explore Agentic Apps or already experimenting with your first use cases, I think that’s the question worth keeping at the centre of the conversation. Not what the technology can do. But what outcomes it can help your organisation achieve.

Please note that all screenshots are the property of Oracle and are used in accordance with Oracle’s Copyright Guidelines.

Over the past few articles in this series, I’ve talked about how Oracle Fusion AI Agent Studio is shifting the conversation away from technology and towards business outcomes. I’ve explored how the Builder Assistant is helping reduce the gap between an idea and a working solution, and I’ve looked at the key building blocks that sit behind Agentic Apps.

But there’s another question that’s arguably even more important. Just because we can build an Agentic App, does that mean we should? As organisations begin exploring AI Agents, there’s a natural temptation to automate everything. Every process starts to look like a candidate for AI. Every challenge appears to need an Agent. Every requirement seems to demand its own intelligent assistant. In my experience, that’s rarely the right approach.

The most successful Agentic Apps aren’t the ones using the most sophisticated technology. They’re the ones solving a genuine business problem in a way that feels intuitive, useful and trustworthy. The technology matters, of course. But good design matters more.

One of the biggest mistakes organisations make when introducing new technology is trying to recreate existing processes in a new tool. We’ve all seen it happen. Paper forms became electronic forms. Manual approvals became digital approvals. Reports became dashboards. The underlying process remained largely unchanged. There’s a risk of doing exactly the same thing with Agentic Apps.

Instead of asking how AI can support an existing process, I think organisations should start by asking a different question. What business outcome are we trying to achieve? For example, an organisation might say they want an AI solution for employee retention. But employee retention isn’t really the outcome. The outcome is helping managers identify people who need support before they choose to leave. Similarly, a procurement team might think they need an AI solution for supplier management. In reality, the outcome is reducing the likelihood of supplier issues disrupting operations. When you focus on outcomes rather than processes, the design conversation changes completely. You stop asking how to automate existing steps and start asking how to help people make better decisions.

This might sound strange coming from someone writing a series about Agentic Apps, but not every business challenge requires an Agent. Sometimes a report is enough. Sometimes an alert is enough. Sometimes a workflow already works perfectly well. I think one of the most important design principles is understanding where an Agent adds genuine value.

Generally speaking, I see Agentic Apps delivering the greatest benefits when people need to combine information from multiple sources, understand a situation, make a decision and take action. Those are activities that often involve context, judgement and prioritisation. By contrast, simple and highly structured processes are often better handled through traditional automation. If the answer is always the same and the outcome is completely predictable, an Agent may simply introduce unnecessary complexity. The goal shouldn’t be to build more Agents. The goal should be to solve more problems.

Most organisations don’t suffer from a lack of data. If anything, the opposite is true. The challenge is usually information overload. Managers have dashboards. Leaders have reports. Teams receive alerts. Yet people still struggle to know where to focus their attention. This is where I think many organisations can unlock the greatest value from Agentic Apps. A good Agentic App doesn’t simply surface more information. It helps users understand what matters.

Imagine two different approaches to workforce management. The first presents pages of employee data, engagement metrics, performance ratings, salary information and talent profiles. All the information is available, but the user still needs to interpret it and decide what to do next. The second identifies three employees who may require attention, explains why they have been highlighted and suggests possible next steps. The underlying data may be exactly the same. The experience is completely different. One focuses on information. The other focuses on decision-making. That’s where Agentic Apps should aim to deliver value.

Whenever AI becomes involved in business processes, governance inevitably becomes part of the conversation. And rightly so. The most successful implementations I’ve seen use AI to support decision-making rather than replace it. For example, if an Agent identifies that an employee’s visa is approaching expiry, it can highlight the issue, gather relevant information and even prepare a communication. But deciding whether to send that communication remains a human decision.

Similarly, if an Agent identifies a supplier risk, it can explain the concern and recommend an action, but accountability for the final decision remains with the person responsible for that supplier relationship. I think this balance is incredibly important. AI should help people make better decisions. It shouldn’t remove people from decisions that require judgement, accountability or context. The organisations that get this balance right are much more likely to build trust in their AI solutions.

One lesson I’ve learned from years of delivering technology projects is that users don’t adopt systems because they’re clever. They adopt systems because they’re useful and trustworthy. An Agent can generate incredibly sophisticated outputs, but if users don’t understand where the information came from or why a recommendation was made, trust quickly disappears. That’s why explainability matters. Users need confidence that recommendations are based on reliable information. They need to understand what data has been considered. They need to know when human review is required.

Most importantly, they need confidence that the system is helping them achieve better outcomes rather than creating additional work. A simple, transparent Agent that consistently provides useful guidance will almost always deliver more value than a complex Agent that nobody trusts.

One thing I’ve noticed when watching AI demonstrations is that they’re often designed to showcase what’s possible. Real business environments are different. The question isn’t whether an Agent can do something impressive. The question is whether people will use it on a busy Tuesday morning when they have ten competing priorities. That means designing experiences that fit naturally into the way people work. It means presenting recommendations in context. It means minimising unnecessary complexity. And it means ensuring users can act on insights quickly and confidently. The most successful Agentic Apps won’t necessarily be the most innovative. They’ll be the ones that people actually use.

Traditionally, technology projects have often been measured using delivery metrics. Did the system go live? Was it delivered on budget? Were the requirements completed? Whilst those measures remain important, I think Agentic Apps need additional measures of success. Are decisions being made more quickly? Are managers identifying issues earlier? Are employees receiving better support? Are risks being addressed before they become problems? Are users spending less time searching for information?

Ultimately, the value of an Agentic App isn’t determined by how many features it contains or how many AI models sit behind it. It’s determined by whether it helps people achieve better outcomes. That’s the measure that really matters.

As organisations continue exploring Agentic Apps, I believe the conversation will gradually move away from technology and towards design. The organisations that achieve the greatest success won’t necessarily have the most advanced AI. They’ll be the ones that understand the problems they’re trying to solve, focus on outcomes rather than processes and place people at the centre of the experience. Good Agentic Apps don’t exist because AI is available. They exist because there are business challenges worth solving. And that’s where every design conversation should begin.

In the final article in this series, I’ll look beyond today’s capabilities and explore where Agentic Apps could take Oracle Fusion next, along with some of the opportunities and challenges organisations should be thinking about as this technology continues to evolve.

Please note that all screenshots are the property of Oracle and are used in accordance with Oracle’s Copyright Guidelines.

In the previous article, I talked about the importance of trust in enterprise AI and why capabilities such as human approvals and deterministic policy controls may ultimately prove just as important as the intelligence of the agents themselves. But even if an organisation is comfortable with how decisions are governed, another challenge remains. How do you know an agent will behave as expected when it reaches production? That’s where things become interesting.

Building an AI-powered prototype has become relatively straightforward. Building something that can operate reliably, safely and consistently within a complex enterprise environment is considerably harder. Traditional software development teams have spent decades refining processes for testing, quality assurance, security and governance. Those disciplines don’t disappear simply because AI is involved. If anything, they become even more important.

One of the things that has impressed me most about Oracle’s vision for AI Agent Studio is the amount of attention being given to the practical realities of operating enterprise AI at scale. The focus isn’t just on building agents. It’s on testing, validating, securing and improving them throughout their lifecycle.

When we think about testing traditional applications, the process is usually fairly straightforward. If I enter a specific value into a field, I expect a predictable result. If I click a button, I know which process should execute. If something changes unexpectedly, it’s usually possible to identify the source of the issue reasonably quickly.

Agentic applications are different. They may involve multiple agents, connectors, data sources, workflows and models. They may depend on information that changes daily, external services that evolve over time and AI responses that aren’t always identical from one execution to the next. This creates a new challenge. It’s no longer enough to test whether a workflow executes successfully. You also need confidence that the outcome remains appropriate.

Oracle describes this as one of the key challenges facing agentic applications and has introduced ATLAS, the Agentic Testing and Lifecycle Automation Suite, to address it. ATLAS is designed to validate workflow behaviour, generate and maintain test scenarios, assess output quality and support optimisation throughout the development lifecycle.

One of the limitations of traditional testing approaches is that they often assume a predictable environment. Enterprise AI doesn’t always operate in one. Data changes. Business processes change. Models improve. Users behave differently. Without effective testing, organisations can quickly lose confidence in the outputs being generated.

What I find particularly interesting about Oracle’s approach is that testing isn’t positioned as something you do at the end of a project. It’s presented as an ongoing discipline that supports the entire lifecycle of an agentic application. ATLAS can generate scenarios, replay real business data, evaluate workflow paths and assess whether outcomes remain aligned with expectations. It can also help organisations compare models, optimise performance and identify areas where improvements may be required. That feels less like traditional software testing and more like continuous validation. Given the pace at which AI technologies evolve, I think that’s exactly the right mindset.

Trust is difficult to establish when nobody understands how a system reached a particular conclusion. This has been one of the most common concerns surrounding AI since the earliest machine learning solutions. People are often willing to accept recommendations. They are far less willing to accept recommendations they cannot understand. This is where debugging and observability become incredibly important.

Oracle’s debugging capabilities allow builders to inspect workflow execution, pause processes, review variables, replay previous executions and compare the impact of changes made to prompts or configuration settings. Previous runs can be analysed and replayed, allowing organisations to investigate why a particular outcome occurred.

Whilst this might initially sound like a feature aimed at developers, its significance extends much further. If an employee questions a recommendation, you need to understand how it was generated. If a customer challenges an outcome, you need to explain the reasoning. If a process isn’t producing the expected results, you need to identify why. You can’t improve what you can’t see. And you can’t build trust in something that behaves like a black box.

Whenever I discuss AI with customers, security inevitably enters the conversation. And rightly so. AI systems frequently require access to business data, enterprise systems and organisational processes. The more valuable the AI becomes, the more important it is to ensure access remains appropriately controlled.

Oracle’s approach incorporates multiple layers of security and governance, including role-based access controls, instruction guardrails, detection mechanisms designed to identify unsafe inputs, encryption and enterprise identity management. Access to connectors, enterprise data and AI capabilities sits within the wider security model provided by Fusion Applications.

I think this is one of the biggest differences between consumer AI and enterprise AI. Consumer AI often focuses on capability. Enterprise AI must focus equally on control. The most useful AI in the world becomes a liability if organisations cannot manage who can access it, what it can see or how it behaves.

The word governance often sounds bureaucratic. It conjures images of policies, committees and governance meetings. In practice, good governance is simply about ensuring technology behaves in a way that organisations are comfortable with.

Oracle’s governance framework includes guardrails, policy enforcement, role-based security controls and centralised management capabilities designed to help organisations maintain oversight of their AI estate. AI can be constrained by rules, escalation paths, approved tools and runtime controls defined by the organisation.

What I particularly like about this approach is that governance isn’t being added after the fact. It’s part of the architecture. As organisations move from isolated AI experiments to broader adoption, I suspect governance will become one of the most important differentiators between successful and unsuccessful implementations. Not because it’s exciting. But because it enables scale.

One of the questions organisations increasingly ask is not just what happened, but how did it happen? If an AI recommendation influenced a business decision, could somebody review that decision six months later? If an agent triggered an action, can the organisation identify who initiated it, what information was used and what approvals were obtained? These questions are becoming increasingly important, particularly in regulated industries.

Oracle’s auditability and traceability capabilities are designed to address this challenge. Agent actions, tool invocations, data access, approvals and execution paths are captured automatically, allowing organisations to reconstruct historical activity and understand exactly how outcomes were reached. Audit information aligns with existing Fusion governance and retention approaches. For many organisations, this level of transparency will be essential. Trust isn’t simply about accuracy. It’s about accountability.

When AI demonstrations are shown at conferences or webinars, it’s easy to focus on the intelligence. The recommendations. The conversations. The automation. But real-world deployment requires something more. It requires confidence. Confidence that the solution behaves consistently. Confidence that it can be secured. Confidence that it can be governed. Confidence that it can be tested, monitored and improved over time.

That’s why I think capabilities such as testing, debugging, security, governance and auditability deserve far more attention than they often receive. They’re not the features that generate the loudest applause. They’re the features that make long-term adoption possible.

As AI Agent Studio continues to evolve, I think we’ll see increasing focus on the operational realities of enterprise AI. Not just how quickly agents can be built. But how effectively they can be managed. Not just how intelligent the outcome is. But how confidently organisations can depend upon it. Because ultimately, enterprise AI isn’t simply about creating capabilities. It’s about creating confidence. And in many cases, confidence will prove far more valuable than intelligence alone.

In the next article, I’ll return to the design of Agentic Apps themselves and explore what separates a genuinely useful Agentic App from one that simply showcases impressive technology.

Please note that all screenshots are the property of Oracle and are used in accordance with Oracle’s Copyright Guidelines.

Whenever I speak to customers about AI, the conversation often follows a familiar pattern. We start by discussing possibilities. We explore use cases. We talk about the potential benefits. We look at how AI might streamline processes, surface insights or improve decision making. Then, sooner or later, somebody asks the question that matters most. “How do we know we can trust it?” It’s a fair question.

In fact, I would argue it’s the question organisations should be asking before they worry about models, prompts or agents. Because whilst intelligent systems can generate excitement, trust is what determines whether they ever make it into production.

Over the past few years, we’ve seen organisations experiment extensively with AI. Many have built prototypes. Others have run proofs of concept or adopted individual AI-powered features. The challenge isn’t generating interest. The challenge is moving from experimentation to everyday business use. That’s where Oracle’s approach to AI Agent Studio becomes particularly interesting.

The more time I spend exploring the platform, the more convinced I am that Oracle’s biggest investment isn’t in creating more intelligent agents. It’s in creating an environment where organisations can trust those agents to operate safely, consistently and responsibly. Trust, governance and enterprise controls are built into the platform from the outset rather than being treated as optional extras.

One of the misconceptions surrounding AI is that success means removing people from the process entirely. Personally, I don’t think that’s what most organisations want. There are certainly activities that can be automated. Administrative tasks, repetitive actions and routine processes are all obvious candidates. But many business decisions still require accountability, judgement and context. Approving a significant payment. Making a hiring decision. Authorising a contract change. Managing a supplier dispute. These are decisions people are expected to own.

Oracle’s Human Approval capability reflects that reality by allowing approval stages to be introduced directly into agentic workflows. Approvals can be routed through established business processes, delivered through multiple notification channels and paused until a decision has been made. Once approval is received, the workflow can continue without losing context or progress.

I see this less as a restriction and more as a confidence-building mechanism. The goal isn’t to remove people. The goal is to ensure people focus on the decisions that genuinely require human judgement whilst allowing automation to handle everything else. That’s a much more realistic vision of enterprise AI.

One of the challenges with generative AI is that it isn’t designed to be deterministic. Ask a large language model to summarise a document and you may receive slightly different wording each time. That’s perfectly acceptable in many situations. But not all business decisions fall into that category.

There are areas where organisations expect exactly the same answer every time. Benefits eligibility. Compensation calculations. Compliance rules. Financial policies. Contractual obligations. These are not decisions where approximation is acceptable.

This is where Oracle’s Policy Models become particularly interesting. Rather than relying solely on AI reasoning, organisations can define policies that execute as deterministic functions. These policies can be generated from business documents, validated through testing and reused across multiple workflows, helping ensure critical business rules are applied consistently.

I think this is one of the most important capabilities within AI Agent Studio. Not because it’s particularly exciting. But because it addresses one of the biggest concerns organisations have about AI. Consistency. Most business leaders are comfortable allowing AI to generate recommendations. They’re far less comfortable allowing AI to interpret policy differently from one situation to the next. Policy Models create a clear separation between reasoning and rules. The AI can help understand the situation. The policy ensures the organisation’s rules are applied correctly.

If there’s one theme that runs through almost every successful technology implementation I’ve experienced, it’s predictability. People trust systems when they understand how they behave. They trust systems when outcomes are consistent. And they trust systems when they know there are controls in place if something goes wrong. That’s why I find Oracle’s approach to approvals and policy enforcement so interesting.

Together, they acknowledge a simple reality: not every decision should be automated, and not every decision should rely entirely on AI. Some decisions benefit from human judgement. Some decisions require strict adherence to business rules. The most effective enterprise AI environments understand the difference.

Rather than forcing organisations to choose between complete automation and complete human control, Oracle appears to be creating a middle ground where AI can assist, recommend and accelerate, whilst governance mechanisms ensure oversight remains where it’s needed. For many organisations, I suspect this balance will prove critical to adoption.

When conversations about AI take place in boardrooms, they’re rarely centred around prompts, models or workflows. They’re centred around risk. Can we trust the recommendations? Can we explain the decisions? Can we maintain control? Can we govern the process? These questions are entirely reasonable. In fact, they’re probably more important than the technology itself. An incredibly intelligent system that nobody trusts will never deliver value.

A well-governed system that people are confident using can transform the way decisions are made. That’s why I think human oversight and deterministic controls deserve more attention than they’re often given. They’re not barriers to innovation. They’re enablers of adoption.

As organisations continue moving from AI experimentation to AI deployment, I believe we’ll see increasing focus on trust alongside intelligence. The organisations that gain the greatest value from AI won’t necessarily be those with the most advanced models. They’ll be the ones that strike the right balance between automation, governance and human judgement. Because ultimately, enterprise AI isn’t really about replacing decisions. It’s about helping people make better ones.

In the next article, I’ll look at another essential piece of the puzzle: how organisations can test, validate and secure AI solutions before they reach production, and why capabilities such as simulation, debugging, auditability and governance may prove just as important as the intelligence itself.

Please note that all screenshots are the property of Oracle and are used in accordance with Oracle’s Copyright Guidelines.