An interface for the archive of an AI assistant
The archive that feeds the assistant lived in a bucket, and every action on it depended on technical knowledge and on credentials for the tools. The Library brought that archive inside the product.
- My role
- Product Designer
- Duration
- 3 months
- Teams
- Design + Engineering
- Platform
- Web
Context
iGUi’s assistant on WhatsApp answers by consulting an archive of documents, and that archive decides how good the answer is.
The Library is where you work on that archive. It lives inside SiG, iGUi’s back office, where each area of the franchisor has its own working tools.
My role
I defined what the screen would do and built the prototypes, first in mid fidelity, then in high.
- I did
- Information architecture · flows · prototypes · design system · handoff
The problem
There was no product. The archive was a bucket, a cloud folder with no screen at all, and working on it meant knowing the file path. The only interface was an engineering test utility: a field to type a name into and a button that deleted.
It served the people building the tool. The people who know the content, the ones who actually need to feed an assistant, were left out.
What use revealed
-
An archive with no screen
Before the listing, every action on the archive, uploading or deleting a file, required technical knowledge and credentials for the tools.
-
Deleting with no way back
Deleting was permanent, in an archive still being put together. The bin came from watching the team work.
-
One document at a time
People updating the archive work on several documents at once, and the screen made them repeat the same action on every file. Multiple selection and bulk actions came in later.
-
Pausing to test
The archive changes all the time, and the team pauses a document to check how it affects the quality of the answer. If the impact is negative they delete it; if not, they reactivate it. Without a pause state, that test was run by deleting the file and restoring it afterwards.
Decisions
-
Permission column
Who receives the file in replies reads straight off the list, without opening anything.
-
Status chip
Paused is not deleted. One sweep down the column tells you what is answering.
-
Permission column
Who receives the file in replies reads straight off the list, without opening anything.
-
Status chip
Paused is not deleted. One sweep down the column tells you what is answering.
-
The permission field
It asks about reach in the conversation, not about access to the Library.
-
The permission field
It asks about reach in the conversation, not about access to the Library.
-
AI description
The largest field in the dialogue, because it is what replaces opening the file.
-
AI description
The largest field in the dialogue, because it is what replaces opening the file.
Results
Running the archive stopped requiring engineering, and it stopped being file‑by‑file work. The same actions serve one document or a whole batch.
- Drop the file in a bucket, outside the product
- Upload on screen, with its reach in replies set in the same step
- Type the exact name from memory to delete
- Pick the item off the list, with a bin to undo it
- A flat prefix, with nothing to say what exists
- Folders by type of material, with breadcrumb and search
- One document at a time
- Multiple selection, with pause, move and discard in bulk
- No record of who did what
- History per item, with author and date
What I took away
Improvisation is a specification. Nobody asked for a pause button: the team was testing the archive by deleting and restoring documents, and that test needed a function of its own.
Next project
Warranty registration in the after‑sales cycle