Tips for Successful Conversation in Tapped In

TAPPED IN is a conference facility set up to enable

you to use general "rules of conversation" that you

would use in real-world meetings. However, the

constraints of text-based communication make it

necessary to introduce a few additional hints on how

to express yourself. Below we provide some tips that

we have found helpful.

Be Aware of Your Surroundings

When you log in, type WHO to see who else is logged,

where they are, and whether they are active or idle.

When you enter a room, take a few seconds to look at

the room map (also called the floor plan), read the

room's description (above the map), and check who

and what objects are in the room with you (below the

map). Remember, not all objects in the room will

appear on the map.

The text interface will automatically tell you when

someone enters or leaves the room (or is

accidentally disconnected). Use the LOOK command to

remind you of where you are, who is with you, and

what objects are in the room. If you are using the

Web interface, click UPDATE VIEW (upper right of the

TAPPED IN Netscape window).

Use a Conversational Speaking Style

Spoken conversation is fraught with mistakes,

shortcuts, and ungrammatical utterances; text-based

conversation need be no different. Don't feel

compelled to spell every word correctly; use common

abbreviations if you like. Commands do need to be

spelled correctly, but TAPPED IN can recognize some

truncated command words like LOOK WHITE, for LOOK

WHITEBOARD.

Regulate the Pace of the Conversation

Conversation often involves relatively short

statements and tightly-coupled turn-taking among the

participants. If the conversation is going too fast

for you to follow, indicate that to the others using

the EMOTE command, e.g.,

:needs a minute to catch up

Try to type shorter, conversational statements

instead of long paragraphs, since the long pauses

while you type can be confusing to others, or the

conversation may have moved on before you hit the

enter key. If you do want to make a longer

statement, use the EMOTE command or ellipses, e.g.,

:has two things to say "We can sum this up as...

[the dot-dot-dot indicates you want to say more]

Show patience for such signs in others'

communication.

Give Nonverbal Feedback

In face-to-face communication, feedback is often

given with nonverbal actions, like nodding.

Text-based communication lacks the visual and

auditory cues that people commonly use to convey

meaning to others, but you can generate them using

the EMOTE command. You don't need to translate every

"body language" action from the real world into

TAPPED IN, but it is often useful to give the other

participants in the conversation feedback that you

are attending. Watch out for ambiguous situations

and unpleasant silence, and disclose your facial

expressions and gestures, e.g.,

:listens :shrugs :grins :nods :raises his hand

Avoid Overlapping Conversations in Meetings

Overlapping topics or overlapping conversations

between different people in the same meeting are

hard to follow. When in a meeting, if you want to

introduce a new topic, indicate that first to make

sure that you don't create overlapping

conversations. Wait until you have the attention of

others who are still talking about the old topic. If

you want to have a side conversation, use the

WHISPER command or go to another room.

--------------------------------------------------

©1997 SRI International, Center for Technology in

Learning. Menlo Park, CA 94025

For more information, contact Mark

(schlager@sri.com) or Patti (schank@sri.com)

Website maintained by schank@sri.com