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

So, I'm working on this little project that has a task flow that includes a Summary page.

Here's the scenario:

User searches for something. Application displays results. User clicks on result. Application displays summary of result.

Option A User clicks field to edit. Application enables editable field. User clicks saves. Application saves. User clicks "back to results" Application displays results.


Option B User clicks field to edit. Application displays editable page of result. User clicks saves. Application saves. Application displays results.

So, I'm wondering what everyone's thoughts are on having the summary page multi-task as a summary page AND a place to edit data VS taking the user to an editable page?

My gut says it's easier for the user to do it all on summary page but it seems to break the mental model.

Any thoughts?

share|improve this question
Thanks. And yes, I guess it's a detail page. I spoke with the team and we agreed to make the detail editable. – Shane Fontane May 17 '10 at 20:56

How many fields are involved? Will your users want to edit more than field at a time? How many edits are they likely to want to do? Will they be editing something that's not shown in the results page? All these sorts of questions should guide you to an approach --- which you then should test with some actual users if possible.

It doesn't actually sound like a 'summary' page, the pattern sounds more like 'detail on demand'. The search result is your summary, the user then asks for more detail when they click the result.

The detail page could be completely editable by default? Removes one step from the entire process.

share|improve this answer

Option B seems the most intuitive BUT if the fields are editable you need to make sure that the action to make the field editable is blindingly obvious.


share|improve this answer

If you are trying to give people a simple way to edit a subset of the details, I would give people a choice from the search results rather than just give them only the smaller set and then make them click to edit the full record.

For example, Wordpress has the idea of "Quick Edit" which is an inline editing of certain details about a post (like title, enable contents), vs clicking on the post to edit the actual content.

share|improve this answer

If your summary page is able to provide the supporting information (to make an appropriate informed decision for change) and facilities to make a change why introduce an additional step between the user and the action they wish to carry out?

Option A (with appropriate caveats).

share|improve this answer

Your Answer


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