Skip to content

Resolve Join vs Create Public chat confusion #32

Description

@hesterbruikman

User Story

As a user I want buttons and links in the app to do exactly what they say they do so that I can take better informed actions and are not faced with surprises.

Description
Type: UI / IA

Summary: Propose alternatives ways to show people that when they enter a topic they are in a way 'starting' this topic.

Expected behavior
When I enter a topic in the Public channel screen form field I expect it to behave like a searchbar. If it's a form field I expect it to look and feel like this and for example do not have something below the input field that looks like a results list.
Next to this, I expect that when a topic does not exist yet, it is only started when I select a control to indicate I want to start it. Unless I do so, I only want to see any conversations that are ongoing.

Actual behavior
In finding a public chat; most participants seemed surprised at having ‘created’ a new chat, while seemingly under the impression that they were searching.

Cause
Copy: There is no sufficiently explanatory hint text or label for the textfield.
UI design: The [#] field on it’s own and, especially in combination with a list, appears to users as a search bar rather than a form field.
People’s experience is to create channels and therefore expect a distinction between Start and Join channel, the UI does not fulfill nor

Consequence
Insecurity, potential frustration

Suggestion for improvement

  • Adjust copy to accurately and fully label and explain field. E.g. [Topic], [Enter topic to join or create chat]
  • Explore layout alternatives to communicate Explore or Find instead of Search.
  • Explore previews or other means of allowing users control over whether they Join or Start a channel.

RRR8 20180906T2I2.1
https://docs.google.com/presentation/d/10qb5jRXwRT9lYkxrn8Ui5Bov_JRuf1WBaPqSXd0ZAtY/edit#slide=id.g41d28d5cd7_16_23
th 2018

Google Docs
Hester Status 17 / 09 / 2018 UXR findings Chat & Command RRR8 Sept 6th 2018

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions