This piece argues that a bunch of familiar UI patterns are going to age badly as AI assistants take over more of the work, especially anything built around rigid forms, deep navigation, and lots of manual clicking.
this image from the piece nails the whole “old UI assumptions are getting shaky” vibe.
The UI is part of it, but i think the first thing people miss is the paper trail. once an assistant starts filling forms or moving stuff around, someone is going to ask “why did it do that? ” and “who signed off? ” a chat log feels flimsy for that. in something like expense approvals, hr changes, or even crm updates, i’d want a clean diff with approve/reject, not just a transcript and vibes. has anyone seen a product that does this well without turning into a giant compliance tax? honestly not sure on implementation.
That “clean diff with approve/reject” bit you mentioned is exactly what I wish more AI-first teams started with instead of treating a chat transcript like an audit log — have you seen anyone attach the approval to a specific before/after artifact (with policy/version metadata) without it turning into a miserable compliance UI?
Signing a stable patch ID is the bit that matters. Not the chat.
I’d keep the UI boring by default: show the diff, let people approve that, and tuck the policy/version junk behind a details drawer until something looks sketchy. We tried a version of this at work and the minute you surface all the metadata up front, people stop reviewing and just start hunting for the one field they’re scared of.
I’m not sure how many AI-first teams will want the extra bookkeeping on the backend, mind you. When you say policy/version metadata, do you mean the policy that was in force when the patch was proposed, or the one at approval time?
The “details drawer until something looks sketchy” idea matches how people actually review, but the part that gets me is time. You probably need to store both “policy at proposal” and “policy at approval, ” because a patch can sit for days and the rules can change under it. Then the UI can show “approved under policy X; current policy is Y” without making everyone stare at metadata all day. I’m not sure what your threshold was for “looks sketchy, ” though. Was it just diff size/type (permissions, money, PII), or something more semantic?
:: Copyright KIRUPA 2024 //--