Are these terms 'Database', 'Record', 'Table', 'Field', 'Row', and 'Column' too technical (or even relevant) for a normal online banking application user, especially when talking to a customer service executive over phone?
I understand that it could vary from context to context, but I am not sure how to see this objectively and find out where to draw the line. A banking website would anyways have many technical terms which a normal person is not likely to understand without putting extra effort.
If not, then what would be appropriate alternative terms for 'Database', 'Record', 'Table', 'Field', 'Row', and 'Column'?
Answer
Following on Benny's answer, I would recommend trying to find the term that relates to the goal of the user (in some circles know as "business terms"). Perhaps by "Record" you mean "transaction", and by "Database" you mean "Transaction History" (just for example).
Of course these terms are also technical, but they relate to the technicality of the realm of the application and the user who is trying to use it. It's way better to educate for these terms, as it might benefit the users in many more ways than teaching them about computer-related technical terms. To achieve this, I really recommend context-sensitive-help.
No comments:
Post a Comment