User Experience Stack Exchange is a question and answer site for user experience researchers and experts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a system in which Procedures can be defined. Each Procedure has a series of steps (each step having some attributes)

It is reasonable to assume that the user will add all of the steps while creating the procedure.

My current approach is using an excel-like grid to enable fast input of the steps.

Procedure Name
[Some Name...]

Name      | Expected Time | Is Invoiced?
Step 1    | 1 day         | [X]
Step 2    | 2 days        | []
add new...               


download bmml source – Wireframes created with Balsamiq Mockups

I would like to know if this sounds resonable or if there is a better way to solve this problem.

As far a I know, the average procedure has 10-20 steps, and each step can have more than 3 attributes... (although only the Step's name is required)

share|improve this question
@Charles: Thanks for showing me how to include the mockup!! – The Sauralph Dec 21 '12 at 19:30

From what I can see, assuming those columns have fixed meanings, it looks like a good solution. I've worked on something similar, a procedure specified in a table, and although it required some training (it was a complicated, domain heavy application) it was successful from a usability point of view. (Hitting the "Enter" key causes a new step to be added, right?)

share|improve this answer
A new step placeholder is available at all times. As soon as there is something on the name column, a new row becomes available. – The Sauralph Dec 21 '12 at 20:14

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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