Design character and personality guidelines for Echo

[jeffreywescott]

@jeffreywescott commented on Tue Aug 09 2016

@tannerwelsh commented on Tue Jun 14 2016

@echo, our beloved ?? , is going to be a pervasive figure in our systems. We want our learners to develop an emotional connection to the character, because emotional connections == more engagement with learning and the game.

In other words, we need to do character development for Echo.

This covers things like defining a backstory and narrative, as well as style guide to create a "personality" through their verbal exchanges with learners (since learners will interface with Echo via text):

• What is the tone of their language?
• How do they react to errors or invalid commands?
• Do they have any common phrases?

To resolve this, write a document in the design guide for styling and adding character to Echo.

[shereefb]

➤ Jared Grippe commented: Are we doubling down on the echo chat interface?

[tannerwelsh]

@deadlyicon on the contrary, we're planning to move away from the Rocket.Chat interface (eventually). This is just about the personality of our mascot, Echo the 🐘

[shereefb]

➤ Jared Grippe commented: Doesn't echo die with RocketShat?

[tannerwelsh]

@deadlyicon yes Echo the chat service, but not necessarily Echo the host for our LOS. Maybe the character of Echo is aren't expressed as chat messages, but in the copy and content of our LOS app. And if Rocket.Chat does go away, we will probably use Slack for comms in which case Echo could become the Slack integration to our LOS.

[jeffreywescott]

It seems likely that we will (longer-term) (a) move to Slack, and (b) have a Hubot-powered "echo" character that we can program to do a bunch of stuff for us.

[shereefb]

➤ Jared Grippe commented: Awesome. Thanks! :smile:

[tannerwelsh]

Moved to Clubhouse.