Here's the scenario: A Person has a bunch of Accounts. Accounts may (or may not) have Services attached to it depending on the type of Account. Currently there are two types of Service (indicated by Columns 1 & 2 in the pic below) but the types of Services will grow in the future (maybe up to 4-6 sort of range)

Some Account types qualify for some Services but not others, etc.

The big system constraint is that all of the Services and Accounts for the Person must be submitted together.

Here is the design proposed by the client:

enter image description here

To me, the suggested designs weakness seems to be the problem of growing Services.

I'm interested in alternatives.

This question provided some interesting ideas but didn't quite fit my use case:

Best UI pattern for letting a user assign items to groups

  • So reversing the original design so that there is a list of Accounts and letting them select from a list of services will not work? – Michael Lai May 16 '13 at 2:28

What your client proposes works, I would change the order though: Accounts first then services.

It is understandable, there is no confusion, you can add as many services as you want.


download bmml source – Wireframes created with Balsamiq Mockups

Maybe what is confusing is the fact that the services names are numbers so I imagine there is some logic between those services.

If the administrator knows the name of the services she wants to add. And only then, you can use that type of interface :


download bmml source

If it is more like all the services are added except one, adapt the interface and add all the available services by default an let the user discard those that are not needed.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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