~ Design lab ~

A space for structured experimentation 🧪

Here I document lightweight design studies inspired by my ongoing research in interaction design, AI tools, prompt engineering, and user psychology. These are fast explorations created to test ideas, interaction patterns, and emerging product workflows without the pressure of building a full case study.

Kanban Payments: exploring a visual way to manage multiple bills

While working on payment workflows for SMBs and larger companies, I kept noticing how complex bill management can become.

Finance teams often deal with dozens (sometimes hundreds) of invoices simultaneously, each in a different state: pending, scheduled, under validation, processing, failed, or completed.

Most systems represent this through dense tables or fragmented filters.

I wondered if a simpler interaction model could make this easier to understand.

While working on payment workflows for SMBs and larger companies, I kept noticing how complex bill management can become.

Finance teams often deal with dozens (sometimes hundreds) of invoices simultaneously, each in a different state: pending, scheduled, under validation, processing, failed, or completed.

Most systems represent this through dense tables or fragmented filters.

I wondered if a simpler interaction model could make this easier to understand.

Trello demonstrates a powerful design principle: start simple, and reveal complexity only when the user needs it.

A board can begin with just three columns: To Do, Doing, Done, and still support extremely complex workflows as users add detail. This experiment explores what would happen if that interaction model were applied to payment management.

Trello demonstrates a powerful design principle: start simple, and reveal complexity only when the user needs it.

The concept was to represent bills as movable cards in a kanban-style board:

→ Pending (To Do): bills that require action, such as new invoices or failed payment attempts

→ Processing (Doing): payments currently in progress, scheduled transactions, validations, or bank processing

→ Completed (Done): bills already paid, cancelled, or expired

Interaction
Instead of navigating multiple forms, users interact with payments directly on the board.

Dragging a bill to Processing can trigger a modal to schedule or confirm the payment.

Moving a card to Completed prompts actions such as marking the bill as paid, ignoring it, or cancelling the transaction.

As the concept evolved, the board also explored batch interactions, allowing users to select multiple bills and move them together for bulk scheduling and payment operations.