Asking for Outcome, Not the App

Objective

After completing this lesson, you will be able to explain how Joule Work lets people start with what they want to accomplish and how it brings together business context, assistants, agents, and connected systems to help move work forward.

Asking for the Outcome, Not the App

What if work started with the outcome?

Think about the beginning of a typical workday, you need to prepare for an important customer meeting. The latest conversation is somewhere in your inbox, your calendar has the meeting details, a presentation contains the project status, another file holds the open issues. Perhaps something important about the customer has changed since you last checked. Before you have even started preparing, you are already thinking about tools: Where was that email? Which folder has the presentation? Did someone update the project file? Is there anything new I should know?

Now imagine beginning somewhere completely different. You simply ask:" Prepare me for my customer meeting this afternoon. Bring together the meeting details, the latest emails, the relevant project information, and anything important I should know."

You are no longer telling the system where to go, you are telling it what you want to accomplish. That is the shift behind Joule Work.

Start with intent, not navigation

Joule Work is the new UI for AI. It gives people a single place to direct their work while AI handles execution across their systems. Instead of starting every task by finding the right application, report, file, or menu, the user can begin with the business need.

Joule Work UI

That need might sound like:

  • "Show me what needs my attention today."
  • "Help me understand what is causing this supply shortage."
  • "Summarize the open issues in this project."
  • "Build me a view of the things I need to track every morning."

The applications and business systems underneath still matter. What changes is the way the person approaches them, the outcome becomes the starting point.

One request can bring the context together

The value becomes especially clear when a business question depends on information stored in different places. Imagine a project manager trying to understand why an important customer issue is still unresolved. Part of the answer may sit in an email thread, another part may be buried in project files. Recent meeting notes may contain an important decision, current external information may add another piece of the picture.

In the Joule Work desktop app, a single conversation can work across email, calendar, local files, and the web. Connected systems can extend that context even further, instead of searching each source separately and trying to reconstruct the story yourself, you can describe what you need to understand.

For example: "Explain why this customer issue is still open. Focus on the decisions already made, anything that is blocking progress, and what needs attention next."

Joule Work can work across the relevant context and bring the pieces together into one coherent response, with the important difference being that the value is not simply in getting the answer faster, but that the user can spend less time finding, switching, copying, and reassembling information before they can even start thinking about the problem.

More than a chatbot response

Some work is too complex for a single lookup or generated answer. Joule Work is built for multi-step work, following a Reason-Act-Reflect-Iterate loop.

  • Reason: Joule Work interprets your intent and plans the steps needed to complete the task.
  • Act: It works with the relevant sources, such as files, email, connected systems, or other available context.
  • Reflect: It evaluates whether the result actually matches what you asked for.
  • Iterate: If something is incomplete or off-target, it can continue before responding.

Suppose you ask: "Review this week’s project information and tell me which risks have become more urgent, what changed, and what I should raise in tomorrow’s steering meeting." That is not one simple retrieval, Joule Work may need to find the relevant information, compare it, identify what changed, organize the result, and decide whether the answer actually addresses your question. The user does not have to design that sequence first, they start with the outcome.

You direct. Assistants coordinate. Agents execute.

Some outcomes involve more than understanding information, they require action across business processes. This is where Joule Assistants and Joule Agents become important.

Joule Assistants are role-aligned and process-aware.

For example, a Financial Closing Assistant understands finance workflows, a Core HR Assistant understands employee lifecycle processes, and a Sourcing Assistant understands procurement.

Assistants coordinate specialized Agents, which execute specific multi-step tasks across SAP systems. The relationship is simple: You direct. Assistants coordinate. Agents execute.

Consider a sourcing manager who needs to move a supplier-related process forward: the person does not necessarily want to think about which system holds which piece of information or which process step needs to be triggered first, they want the business outcome.

The Assistant can help coordinate the relevant process context, while specialized Agents can execute the defined tasks required within that process. The user remains the one setting the direction, the technology helps organize and execute what happens around it.

Sometimes you need more than an answer

Now imagine a sales manager who checks the same information every morning: How many open deals are there? Which customer conversations need attention? What meetings are coming up? Which approvals are still pending? How is the pipeline changing? A conversation can answer those questions once, but tomorrow, the answers may already be out of date.

That is where Spaces change the experience. The manager can simply say: "Build me a dashboard for my daily sales briefing." And Joule Work can create an intent-driven Space around that goal.

The user does not start from a fixed template or a predefined application page. The Space is assembled around the intent and the available data and it can then be refreshed as the underlying information changes.

This is generative UI: the interface itself can be constructed around what the user is trying to accomplish. Instead of always asking people to adapt to software, the software can begin adapting to the person’s goal.

Sometimes the work finds you

There is another possibility: sometimes you know exactly what to ask, but sometimes you do not yet know that something needs your attention.

In the Joule Work web experience, Discover can proactively surface tasks and content that are relevant to the user’s role and context. A deadline may be approaching, an approval may require attention, something important may have changed. Instead of waiting for the user to navigate somewhere and discover the issue manually, relevant work can be brought forward.

That gives the experience different ways to begin:

  • With Conversations, you ask.
  • With Discover, relevant work can surface proactively.
  • With Spaces, you create an ongoing view around a recurring need.
  • With Develop, power users and developers can move from using Joule Work to extending it through Joule Studio.

The interaction changes depending on what the person is trying to achieve.

Diagram showing Conversations, Discover, Spaces, and Develop modes.

What happens when the need evolves?

The Joule Work experience becomes particularly interesting when those modes connect.

Imagine a supply chain manager who asks in Conversations about an emerging shortage. The issue is identified, and procurement needs a broader view of supply and demand. A procurement director can then work with a Space that brings together the relevant information, supports further analysis, and helps move the process toward a sourcing decision.

Later, the organization decides that supplier performance should be monitored continuously instead of waiting for someone to ask. That is when the need can move into Develop, the entry point into Joule Studio, where a production-grade agent can be built for ongoing execution.

One business problem. Different ways of working with it as the need evolves.

The user is not jumping between unrelated AI features, the experience can move from asking, to understanding, to working with an ongoing view, to building something that operates at a broader scale.

Work can follow you

The same principle also applies to where work happens.

Joule Work is available across desktop, web, and mobile, with each format designed for a different context.

Image showing Joule on Desktop, Web, and Mobile.

The desktop experience is suited to knowledge work involving local files, email, calendar, and connected systems, while the web experience brings Joule Work into SAP cloud processes and supports experiences such as Assistants, Spaces, and Develop.

And on mobile, the interaction can continue when you are away from your desk. Picture a sourcing manager on a site visit when an urgent supplier approval arrives. They do not need to wait until they return to their laptop, they can use the mobile app, ask Joule Work for context, and even interact through voice when typing is impractical.

The point is not simply that the same technology appears on another screen, it is that the experience can follow the work instead of requiring the work to wait for the right application, device, or moment.

From "Where do I click?" to "What do I want to accomplish?"

For decades, enterprise software has often asked people to learn how the system is organized: Which application? Which menu? Which report? Which transaction?

Joule Work introduces a different starting point.

Describe the goal. Let the relevant context, systems, Assistants, and Agents come together around that intent. Sometimes that means a conversation, sometimes it becomes a Space, sometimes the right information appears proactively. And sometimes the requirement grows into something that needs to be built through Develop and Joule Studio.

The question shifts from "Where do I go to do this?" to "What do I want to accomplish?".

That is what makes Joule Work more than another AI chat interface. It points to a different way of working with enterprise technology: one where people begin with what they want to achieve, the system can bring the right context and capabilities together around that goal, and more of the complexity stays behind the experience rather than in front of the user.

The result is not simply a faster way to use software, it is a more natural way for people and AI to work together around the outcomes that matter.

Want to explore Joule Work in more detail? Continue with the Using Joule Work course to learn more about Conversations, Discover, Spaces, Develop, and how Joule Work supports work across desktop, web, and mobile.

Lesson Summary

  • Joule Work is the new UI for AI, giving users a single place to direct their work while AI handles execution across their systems.
  • Users can begin with the outcome they want rather than navigating first to a particular application.
  • Depending on the format and setup, Joule Work can work with context from SAP systems, files, email, calendar, the web, and connected external systems.
  • Joule Work follows a Reason-Act-Reflect-Iterate loop to support multi-step work.
  • Joule Assistants are role-aligned and process-aware, while specialized Joule Agents execute multi-step tasks: You direct. Assistants coordinate. Agents execute.
  • Conversations, Discover, Spaces, and Develop provide different ways to work around the user’s intent.
  • Across desktop, web, and mobile, Joule Work is designed to support different work contexts while keeping the focus on what the person wants to accomplish.
  • The broader shift is from organizing work around applications to organizing the experience around business intent and outcomes.