Our summary
Ask about a paycheck and Sana shows a card, with the amount revealed by a click. Ask for time off and a date picker appears. Lardinois reports these examples from Workday's press demonstration of its assistant for HR, finance and IT, which selects screen parts for an employee's request.
Workday says Jev chooses among components the company has already designed, rather than having a language model write the interface. Preparing data ahead of time helps, too. Choices stay within those components. Other projects in the article describe fallbacks for unfamiliar requests, but those are not Workday's disclosed behavior.
Workday has not said how many components there are or what happens if none fits. The article names TypeSafe as an outside data processor. According to the briefing, using Sana through Claude loses the Jev-driven interface and some context, so that route offers a different screen experience.
Key takeaways
- The components are predesigned by Workday. Jev selects them rather than drawing an entire interface from scratch.
- Ahead-of-time data preparation contributes to the response. Model speed does not explain the whole experience.
- Before borrowing the approach, check outside data processors and what happens when no component fits. Workday's fallback is undisclosed.