Our summary
A paycheck question brought up a card with the amount behind a click; a time-off request brought up a date picker. Lardinois describes those examples from a Workday press demonstration. Sana, the company's assistant for HR, finance and IT, selects the screen parts needed for the employee's request.
Workday says it gave Jev its designed components to choose from instead of asking a language model to write the whole interface. Preparing data ahead of time also mattered. The bounded choice keeps the screen within those parts, though other projects discussed in the article use a fallback for unfamiliar requests.
Workday has not disclosed how many components it offers or what happens when none fits. The article also identifies TypeSafe as an outside data processor. Accessing Sana through Claude loses the Jev-driven interface and some context, according to the briefing; that route is not the same screen experience.
Key takeaways
- Jev chooses among components Workday already designed; it is not drawing the whole interface from scratch.
- Preparing the data ahead of time helps the screen respond. Model speed alone does not explain the experience.
- Workday's no-fit fallback is not disclosed. Check that behavior and the outside data processors before applying the same approach.