A command that stays available, makes room for conversation, and leaves space for the work.
- The brief
- Unified Command is a shared starting point for expressing intent: one place to ask, search or command. It was not going to be a chatbot parked beside the product, so its shape and behavior had to come from the work on screen.
- What I did
- I worked through how much of it should be visible. It sits bottom center as a compact control, opens to a full input, and grows a conversation upward from that same input. Results open in the workspace, and the conversation can be put away without ending the session.
One component, one input
Opening chat should not leave the original command sitting below another text field, making someone decide where to continue. The conversation grows from the command, with the input staying at the bottom of the same component. You started here, the exchange opened here, and your next request belongs here.
Command and workspace
The command is for saying what you want and for short exchanges about it. The workspace is for the thing itself. A planner opens a purchase order, asks when it arrives, then attaches a revised supplier schedule and asks to compare. The comparison needs room to scan dates and select a row, so it opens in the workspace, with the command still there for a follow-up.
Put away, not ended
Closing chat changes what is visible without ending the session. Someone can put the conversation away to inspect the result and come back to it without reconstructing what they were doing. The architecture stays consistent while the interface adapts to the work.