ThoughtWorks
  • 联系我们
  • Español
  • Português
  • Deutsch
  • English
概况
  • 工匠精神和科技思维

    采用现代的软件开发方法,更快地交付价值

    智能驱动的决策机制

    利用数据资产解锁新价值来源

  • 低摩擦的运营模式

    提升组织的变革响应力

    企业级平台战略

    创建与经营战略发展同步的灵活的技术平台

  • 客户洞察和数字化产品能力

    快速设计、交付及演进优质产品和卓越体验

    合作伙伴

    利用我们可靠的合作商网络来扩大我们为客户提供的成果

概况
  • 汽车企业
  • 清洁技术,能源与公用事业
  • 金融和保险企业
  • 医疗企业
  • 媒体和出版业
  • 非盈利性组织
  • 公共服务机构
  • 零售业和电商
  • 旅游业和运输业
概况

特色

  • 技术

    深入探索企业技术与卓越工程管理

  • 商业

    及时了解数字领导者的最新业务和行业见解

  • 文化

    分享职业发展心得,以及我们对社会公正和包容性的见解

数字出版物和工具

  • 技术雷达

    对前沿技术提供意见和指引

  • 视野

    服务数字读者的出版物

  • 数字化流畅度模型

    可以将应对不确定性所需的数字能力进行优先级划分的模型

  • 解码器

    业务主管的A-Z技术指南

所有洞见

  • 文章

    助力商业的专业洞见

  • 博客

    ThoughtWorks 全球员工的洞见及观点

  • 书籍

    浏览更多我们的书籍

  • 播客

    分析商业和技术最新趋势的精彩对话

概况
  • 申请流程

    面试准备

  • 毕业生和变换职业者

    正确开启技术生涯

  • 搜索工作

    在您所在的区域寻找正在招聘的岗位

  • 保持联系

    订阅我们的月度新闻简报

概况
  • 会议与活动
  • 多元与包容
  • 新闻
  • 开源
  • 领导层
  • 社会影响力
  • Español
  • Português
  • Deutsch
  • English
ThoughtWorks菜单
  • 关闭   ✕
  • 产品及服务
  • 合作伙伴
  • 洞见
  • 加入我们
  • 关于我们
  • 联系我们
  • 返回
  • 关闭   ✕
  • 概况
  • 工匠精神和科技思维

    采用现代的软件开发方法,更快地交付价值

  • 客户洞察和数字化产品能力

    快速设计、交付及演进优质产品和卓越体验

  • 低摩擦的运营模式

    提升组织的变革响应力

  • 智能驱动的决策机制

    利用数据资产解锁新价值来源

  • 合作伙伴

    利用我们可靠的合作商网络来扩大我们为客户提供的成果

  • 企业级平台战略

    创建与经营战略发展同步的灵活的技术平台

  • 返回
  • 关闭   ✕
  • 概况
  • 汽车企业
  • 清洁技术,能源与公用事业
  • 金融和保险企业
  • 医疗企业
  • 媒体和出版业
  • 非盈利性组织
  • 公共服务机构
  • 零售业和电商
  • 旅游业和运输业
  • 返回
  • 关闭   ✕
  • 概况
  • 特色

  • 技术

    深入探索企业技术与卓越工程管理

  • 商业

    及时了解数字领导者的最新业务和行业见解

  • 文化

    分享职业发展心得,以及我们对社会公正和包容性的见解

  • 数字出版物和工具

  • 技术雷达

    对前沿技术提供意见和指引

  • 视野

    服务数字读者的出版物

  • 数字化流畅度模型

    可以将应对不确定性所需的数字能力进行优先级划分的模型

  • 解码器

    业务主管的A-Z技术指南

  • 所有洞见

  • 文章

    助力商业的专业洞见

  • 博客

    ThoughtWorks 全球员工的洞见及观点

  • 书籍

    浏览更多我们的书籍

  • 播客

    分析商业和技术最新趋势的精彩对话

  • 返回
  • 关闭   ✕
  • 概况
  • 申请流程

    面试准备

  • 毕业生和变换职业者

    正确开启技术生涯

  • 搜索工作

    在您所在的区域寻找正在招聘的岗位

  • 保持联系

    订阅我们的月度新闻简报

  • 返回
  • 关闭   ✕
  • 概况
  • 会议与活动
  • 多元与包容
  • 新闻
  • 开源
  • 领导层
  • 社会影响力
博客
选择主题
查看所有话题关闭
技术 
敏捷项目管理 云 持续交付 数据科学与工程 捍卫网络自由 演进式架构 体验设计 物联网 语言、工具与框架 遗留资产现代化 Machine Learning & Artificial Intelligence 微服务 平台 安全 软件测试 技术策略 
商业 
金融服务 全球医疗 创新 零售行业 转型 
招聘 
职业心得 多元与融合 社会改变 
博客

话题

选择主题
  • 技术
    技术
  • 技术 概观
  • 敏捷项目管理
  • 云
  • 持续交付
  • 数据科学与工程
  • 捍卫网络自由
  • 演进式架构
  • 体验设计
  • 物联网
  • 语言、工具与框架
  • 遗留资产现代化
  • Machine Learning & Artificial Intelligence
  • 微服务
  • 平台
  • 安全
  • 软件测试
  • 技术策略
  • 商业
    商业
  • 商业 概观
  • 金融服务
  • 全球医疗
  • 创新
  • 零售行业
  • 转型
  • 招聘
    招聘
  • 招聘 概观
  • 职业心得
  • 多元与融合
  • 社会改变
创新技术商业

Lessons learned pretending to be a chatbot: Part Two

Kylie Castellaw Kylie Castellaw

Published: Feb 5, 2018

In Part One, we shared what we learned about chatbots in general and our users, based on our experience of asking users to interact with a chatbot that was still part (or largely) human. Now, we’re excited to pass on a few specific tips and tricks for others who are designing (or thinking about designing) bots themselves.

Let’s get right into it: these lessons will hopefully aid others on the journey toward creating successful chat products via pretending to be a bot:
 
  1. Be upfront about who is behind the bot and nail the intro… eventually: By listening to the questions our users asked as they interacted with our fake bot, we learned exactly what content we’d need to provide in the bot’s introduction. For instance, who made the bot, what it does, and privacy information.

    Different bots will likely produce slightly different questions in users’ minds as they are just starting out, so while pretending to be a bot, feel free to leave the intro out. That way while your testers are being observed, you can hear them ask questions aloud — that way you know which questions are truly important to answer right up front.

    Then after you understand your users’ questions, take the time to make your bot’s introduction thoughtful and helpful — while still being concise. If we’d pretended to be a bot that included intro content, it’s doubtful that users would have told us which parts they didn’t need. So this really helped us keep it shorter and sweeter than if we’d included every piece of information we’d assumed might be helpful in the introduction.


     
  2. 'More is more' when it comes to directing users towards what to do next: In our ‘fake bot’ test period, users told us that they were unsure how to respond and what they were supposed to be doing. By age 15 (our target group), people know how to talk to a human. They know the rules of how to break the ice, how to ask questions, how to interpret what the other person is saying. Not so yet with bots! And that’s part of the delight of a chatbot done well at this early stage; people don’t know what to expect, and so we have the potential to delight them — or disappoint in a big way.

    We found that quick answer buttons can help users know how they should respond, especially early in an experience; they set the tone for how the user should engage, so they don’t have to think about what to type. We learned the hard way about how important it is to be even more explicit about what is expected of them than you’d be in any human conversation with a person, or in a traditional digital experience.
     
  3. Take advantage of this opportunity to try all the features you want and see what sticks! We found that the chatbot reaching out — say with a reminder or notification — was an exciting feature for our 15–25y/o audience!

    As designers and product strategists with full-time jobs, we often feel inundated by too many reminders for things as it is, so we were surprised to hear how excited this audience was to know that we’d be able to reach out with reminders for things they care about. While it will take us a little while to develop that into the app, it was easy to be able to offer the feature as humans, letting us see how users responded to that capability. Now it’s on our roadmap; if we’d gone on gut feel alone, we might not have prioritized it so highly.
     
  4. Set expectations for your fake bot’s response time: We did our best to respond to users’ questions and conversations as soon as we could, and even made ourselves available after office hours to meet the needs of our first users. But occasionally, we took too long to respond and broke our users’ trust; when you text a human, you expect the conversation to be asynchronous. But when you text a bot, something seems wrong if it doesn’t reply right away. So set expectations up front about what hours the bot will be available in this fake bot testing phase and then be sure to stick to it.
     
  5. Make it easy for users to provide ongoing feedback about the experience. After our initial 30-minute session with each test user, we asked them to interact with the bot for the following week. And the most enlightening part of that next week wasn’t how often they used it or how they answered the bot’s questions, but what they told our team directly through the bot. We told them they could preface any message to the bot with an asterisk if they wanted the message to be sure to be seen by us — and that it would be appreciated if they could provide feedback in this way. Here’s an example of something a user let us know through this mechanism:

    “*one thing the bot should/could be prepared to help/aid/assist with is anxiety concerning test results… what I like so much about the last response ("what is in your control") is that it gave me power. Anxiety (I think) is a fairly common thing among survivors and current patients. And the thing is we're pretty anxious bc all the things aren't in our control.”  

    This very rich piece of feedback was sent at the moment, with very little effort from the user, but it opened our eyes to a whole new potential content area to explore.
     
  6. And make it easy and straightforward for yourself to ask follow-up questions. Another thing that worked out very well was having a script item prepared, so we could paste it in whenever someone left feedback with an asterisk, letting them know that they were heard (“*Noted, thanks for the feedback!”). This set a precedent for asterisk-preempted messages to be outside the normal bot chat flow.

    This meant that we could even include personal messages or requests to participants, always starting with an asterisk and introducing ourselves by our real name to keep it clear who they were talking to. We used this method to ask clarifying questions about their asterisk comments, request that they pick a time for a follow-up session, and, in the case below, ask for permission to use a message in our blog post!
Designers and developers alike, take it from us: pretending to be a bot can be extremely enlightening, as well as a humbling and entertaining experience. Just make sure to set yourself up for success with the points above, keep an open mind about what you’ll learn, and be ready to shift course based on what you find. And let us know how it goes!
相关博客
创新

Lessons learned from life as a chatbot: Part 1

Kylie Castellaw
了解更多
Machine Learning & Artificial Intelligence

Why conversational UI? Why now?

Holden Bale
Neil Redding
了解更多
Machine Learning & Artificial Intelligence

Interact or Die Trying

Neil Redding
了解更多
  • 产品及服务
  • 合作伙伴
  • 洞见
  • 加入我们
  • 关于我们
  • 联系我们

WeChat

×
QR code to ThoughtWorks China WeChat subscription account

媒体与第三方机构垂询 | 政策声明 | Modern Slavery statement ThoughtWorks| 辅助功能 | © 2021 ThoughtWorks, Inc.