So I have a requirement to design a "Create, Update, Delete" interface all-in-one (without a table). Here's the basic functionality, or flow, as I understand it:

You enter an ID into an input box and push "search" or "go" or whatever... if the ID doesn't exist, you take the user to a "wizard" that allows them to add that ID to the "database." If the ID does exist, a pop-up will open saying "Do you want to delete or edit this record?"... delete will delete the record and edit will take the user to the same "wizard" for adding a record, just that all input fields in the wizard will be pre-populated.

Speaking from a generic-user point-of-view, I know that this whole "Create/Update/Delete" is confusing. That's why I'm wondering if there's any way possible to keep the same flow (one place to do all CUD operations), but still maintain GOOD user experience. If anyone has done something like this, I'd love to know how you actually designed it!


1 Answer 1


You may try the following suggestion :

  • The user etners the ID (screen 1)
  • If the ID does not exist, the ID field is disbled, the status is set to NEW and the user can enter the details of the new entry (screen 2)
  • If the ID exists, the ID field is disbled, the status is set to UPDATE and the user can make any changes needed or delete the record (screen 3)
  • When the user is done with one ID and wants to enter another one, he clicks on clear which clears all fields and enables the ID field.


download bmml source – Wireframes created with Balsamiq Mockups

  • 1
    This definitely gives me a good starting point, thank you!
    – exk0730
    Jan 17, 2018 at 13:14

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.