Hello Friends, This is an interesting discussion. I would like to share my experience.
The business area for our product is audit. Having a know-how of audit domain has proven advantageous especially during the user councils and data gathering sessions. Domain knowledge in our case has made it one step easier to understand our users, relate to them and their processes. Especially when they have a typical query which can be addressed with existing work around in the product can be resolved further provides insight to fine tune on the usability of the product. Experience goes like this: Background: We had a feature for a functionality around benchmarking objects for comparing with the current objects. Here the user selects the parent object, then children for benchmarking. The user feedback was: There are cases when they are not aware of the parent but have defined the children for selection for benchmarking. Feature: Required selection of parent and then its children objects. Advantage: We know how the auditors work on this particular feature. Solution proposed for the current timeline. Provide an additional search option for underlying child objects to filter out the parent object and display enabled in the child object bucket on the UI. The user could then easily search/select child objects. Please share your experiences as well. My 2 cents, Bhakti ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://gamma.ixda.org/unsubscribe List Guidelines ............ http://gamma.ixda.org/guidelines List Help .................. http://gamma.ixda.org/help
