Workday Sana: From Software Menus to Finished Work
Workday Sana reorganizes enterprise software around finished work. Learn why process ownership, exception paths, and service metrics will determine its value.
Workday Sana matters because it changes what the enterprise interface is expected to do.
Instead of helping an employee find the correct application, menu, or department, Sana is designed to interpret the desired outcome and coordinate the tasks, information, agents, approvals, and people needed to complete it.
That could simplify employee services across HR, finance, and IT. It also raises the implementation standard. If the underlying process has unclear rules, conflicting owners, or no path for exceptions, a more natural interface will not fix the problem. It will simply reach that ambiguity faster.
Key takeaways
Sana is now the Workday Home experience, with administrators controlling enablement.
Sana Concierge remains with early adopters and is expected to become generally available in Q1 2027.
Agent Harness and several supporting development components are generally available.
The interface is shifting from locating software functions to coordinating outcomes.
Success should be measured by completed work, not merely fewer tickets or clicks.
What did Workday announce?
On October 13, 2026, Workday announced that Sana is becoming the new Workday Home.
The experience brings tasks, decisions, meetings, and agent activity into one persistent workspace. Employees can describe what they need in natural language, while Sana presents the appropriate form, calendar, approval card, visualization, or action.
Workday also introduced Sana Concierge for employee services such as onboarding, leave, payroll questions, password resets, and application access.
Availability
✓ Workday Home: Available now. Administrators decide when to enable it and whether it becomes the default.
◐ Sana Concierge: Currently available to early-adopter customers. General availability expected Q1 2027.
✓ Agent Harness, Agent-Ready Tools, Custom Agents, Developer Agent, Workday Data Cloud: Generally available.
◌ Additional context and grounded-reasoning capabilities: Planned for late 2026 or early 2027.
Separately, Workday says Agent Harness, Agent-Ready Tools, Custom Agents, Developer Agent, and Workday Data Cloud are generally available. Some additional context and grounded-reasoning capabilities remain planned for late 2026 or early 2027.
When menus disappear, the process becomes the interface
Traditional enterprise software expects employees to understand how the organization divided the work.
They need to know which application contains the information, where to submit a request, which department owns it, and what happens next.
Workday’s direction reverses that relationship. The employee describes the outcome, and the platform coordinates the systems behind it.
Applications and business rules do not disappear. They become less visible to the employee.
That can improve usability, but it also means the quality of the experience increasingly depends on what sits behind the interface:
Accurate employee and business data
The foundation for any agent-driven interaction. Incomplete or outdated records create incorrect outcomes.
Clear approval rules
Without explicit approval logic, agents cannot distinguish routine requests from exceptions.
Reliable system integrations
Coordinating outcomes across HR, finance, and IT requires stable, well-maintained connections.
Defined process ownership
Someone must own each process end-to-end, not just the technology, but the business rules.
Documented exception paths
Every process has edge cases. Without defined paths, agents stall and employees lose trust.
Effective human escalation
Agents need clear rules for when to stop and involve a person with the authority to decide.
An elegant front door cannot compensate for a process that no one fully owns.
Process debt becomes visible sooner
Consider employee onboarding.
An agent may be able to request equipment, create application access, assign training, and notify a manager. The organization must still define:
Decisions that remain necessary
- • What officially starts the process
- • Which access belongs to each role
- • Who approves unusual requests
- • What happens when equipment is delayed
- • Which tasks must finish before the starting date
- • Who takes ownership when automation fails
If those decisions vary by department or exist only in someone’s memory, Sana will encounter the inconsistency.
This is not an argument against agentic automation. It is a reason to treat process preparation as part of the implementation rather than expecting the new interface to perform that work automatically.
→
Ticket deflection is not the same as service improvement
Sana Concierge could resolve some employee needs before they become HR or IT tickets. That may reduce repetitive work, but ticket reduction alone is an incomplete measure.
Request disappeared correctly
The employee's need was fully met. The outcome was accurate, timely, and required no follow-up.
Request disappeared without resolution
The employee abandoned the interaction or found a workaround. The need was not actually met.
A request can disappear because it was resolved correctly. It can also disappear because the employee abandoned the interaction or found another way around it.
Organizations should measure:
| Metric | What it reveals |
|---|---|
| Time to complete the full employee outcome | Whether the end-to-end journey improved, not just the first response |
| First-contact resolution | Whether the request was handled completely on the first interaction |
| Reopened or repeated requests | Whether supposed resolutions actually stuck |
| Accuracy of approvals and system changes | Whether automated actions matched the correct business rules |
| Quality and speed of human escalation | Whether exceptions reached the right person quickly enough |
| Employee satisfaction | Whether employees felt their need was actually met |
| Frequency of exceptions | Whether processes are well-defined enough for automation to handle most cases |
These measures reveal whether the service improved, not merely whether the queue became smaller.
→
How should organizations evaluate Workday Sana?
Start with one recurring employee journey instead of enabling every possible workflow at once.
A useful pilot might focus on onboarding, parental leave, application access, or another process that crosses multiple teams.
For that journey:
Identify every system, owner, and approval involved
Document the normal path and common exceptions
Capture both the standard flow and the real-world variations that employees encounter.
Separate predictable rules from decisions requiring judgment
Determine which steps can follow fixed logic and which need human reasoning.
Define when Sana should stop and involve a person
Set explicit boundaries for agent authority versus human escalation.
Establish the current time, effort, and failure rate
Create a measurable baseline before implementation so improvement can be verified.
Compare the completed outcome after implementation
Measure whether the full journey improved in speed and accuracy.
The pilot should answer whether the process became faster, clearer, and more reliable—not simply whether employees liked using the interface.
→
The Infonaligy perspective
As enterprise interfaces become more conversational, process documentation becomes operating infrastructure.
The quality of the experience will depend less on how naturally an agent speaks and more on whether the organization has defined its rules, responsibilities, integrations, and escalation paths.
This also changes application ownership. Application teams will not only maintain configurations and availability. They will increasingly steward the business journeys that agents coordinate across systems.
Infonaligy’s AI Consulting and IT Application Services help organizations evaluate workflows, dependencies, ownership, and measurable outcomes before automation expands.
Conclusion
Workday Sana represents a meaningful shift from software that helps employees find work to software that attempts to coordinate and finish it.
That direction could reduce friction across HR, finance, and IT. Its value, however, will depend on the clarity of the processes underneath it.
The most useful adoption question is not simply whether employees can ask Sana for help. It is whether the organization has defined the work clearly enough for Sana—and the people around it—to finish the job well.
Frequently asked questions
Sana is Workday's agentic home experience for coordinating tasks, decisions, information, agents, approvals, and business processes through natural-language requests.
Not yet. Workday says it is available to early-adopter customers and is expected to become generally available in the first quarter of 2027.
Yes. Workday says Agent Harness and several related development and data components are generally available.
No. It may resolve routine requests, but organizations still need human support for exceptions, judgment, complex incidents, process failures, and sensitive decisions. Learn about IT help desk services →
Begin with one recurring employee journey. Document its rules, systems, owners, exceptions, and existing performance before testing whether Sana improves the complete outcome.
Primary sources
Related reading
- What Is IT Automation? An SMB Guide to Patching, Onboarding, and Monitoring
- The AI Agent Governance Gap: An SMB Guide
Whether you're evaluating Workday Sana readiness or strengthening the process infrastructure behind your enterprise applications, Infonaligy can help assess workflows, dependencies, ownership, and measurable outcomes.
Serving Businesses Across Texas & Oklahoma