Design Pair Session

Thanks for taking the time to dig into some problem-solving! We'll be taking a look at a specific layout, and we'll be looking to hear your thoughts about the UX. The page you're looking at is a simplified, static version of a page, so there are some obvious gaps missing like validation, application shell, mobile layout, and an actual form submission.

During the shared portion of the session, we'll have an open discussion about these things. Feel free to ask any clarifying questions! There's no wrong answers here.

Let's focus on the specific action of the user story, and whether the form used is an effective solve for this. Are there potential problems with the UX? What would you do differently? Will it scale to other use cases?

View the form →

User Story

As an internal user for Acme records, I need to be able to manage the members attached to a specific Artist.

Additional Context

• a member is a person who can be attached to an artist
• there are thousands of members stored in the system
• there may be members with duplicate names
• members can be attached to multiple artists
• there are anywhere between 1 and 10 members attached to an artist
• when adding a member to an artist, the user likely knows the name of the member they're searching for
• a user would land on this page after clicking 'Edit Members' from the artist detail page
• we'll want to ensure the pattern we use here scales well to other similar relationships in the system that may have more complex attributes and identifiers
  • ex) adding tracks to an album, or a sound recording to a track
  • there are thousands of tracks, thousands of albums, and many duplicated names

View the form →