This is somewhat of a nit of a question, but a fellow designer and I
tossed it around and we decided we needed a little outside advice.
We are designing a revision of an internal development tool that
constructs applications that of course interact with people. The
question we have is about the terminology of a piece of the tool that
allows the developer to specify instructions that will be given to a
person and accepts responses back from that person. We think we'd
like to use the terms "input" and "output" as labels, but we're
wondering in which direction they should be used. I.e., is an
instruction to the person "output"? And is their response
"input"? Or is a person's response "output" based in the
instruction? Or should we abandon these two words and use others
such as "request" and "receive"?
Thoughts? Other helpful ideas?
Those using this tool are generally well-educated about the purpose
of it, so poor usability is not too much of an issue. We'd just
like the labels to be clear and make sense.