Context
- Prism Central: AWS for your own infrastructure, built on 2014-era patterns
- Generative UI collapsed the gap between intent and execution
- Chat renders charts; a transcript scrolls them away
- Diagnosis needs things side by side, not in sequence
Prism Central is Nutanix's flagship control plane for commanding and controlling data centers. Think AWS, but for your own infrastructure.
It has been built on traditional enterprise patterns since 2014, and it carries a decade of accumulated conventions. Meanwhile, generative UI was changing what people expect from software. The loop from intent to execution was collapsing across the consumer tools our users go home to, while in products like ours getting something done still meant discovery, navigation, and learning steps.
The obvious move was to dock a chat panel beside the page. Modern chat surfaces render charts and tables perfectly well, so the constraint was never what a single response can contain. It is what a transcript can hold onto:
"As an IT admin, I want to analyze why my VM is running slow so I can take the right steps to resolve it."
That admin does not ask one question. They pull a latency chart, check the host, compare against last week, then look at what else is running on that node. A transcript answers each of those and scrolls the previous one out of reach. Nothing sits beside anything else, so the comparison the diagnosis actually turns on has to happen in the admin's head. We had to rethink what kind of intervention fit.