Skip to content

[Hold #41442] [Guided Setup Stage 3][$500] Don't create default #announce rooms until a workspace has 3 or more members #34929

@JmillsExpensify

Description

@JmillsExpensify

Problem

While we originally envisioned default rooms to streamline the a whole host of team collaboration use cases – including announcements to your employees, or chatting with other admins - as we've gained experience onboarding users to NewDot we've realized that this has had the effect of making onboarding harder. More specifically, your LHN starts out with a host of rooms and messages, though it's not clear which you should start with first:

  • Expensify (planned)
  • Concierge
  • Workspace chat
  • #admins
  • #announce

Even further, plenty of sign-ups are first and foremost looking for an expense and financial management app, and they're just one person, so this ends up confusing them that they've downloaded the wrong app, costing us valuable bottom-up chances that we'd otherwise keep around as long as sign-ups can effectively find what they're looking for.

Solution

Part of this solution is more targeted onboarding, and that's already being worked on in #wave9-collect-signups. Though equally, let's not assume group collaboration is what sign-ups are after – especially if they're the only member of the workspace. A good example is the #announce room, which is only relevant when a workspace has several members.

Thus, in an effort to simplify what users are exposed to post-sign-up, and better target our functionality to their intended use case, let's:

  • Not create a default #announce room when the workspace is created
  • Instead, let's only create #announce rooms when the third member is added to the workspace (after all, otherwise two members could use a DM without issue).
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01d20cdc896fd34ad2
  • Upwork Job ID: 1755964549843316736
  • Last Price Increase: 2024-02-16
  • Automatic offers:
    • rojiphil | Contributor | 0

Metadata

Metadata

Labels

EngineeringExternalAdded to denote the issue can be worked on by a contributorNewFeatureSomething to build that is a new item.ReviewingHas a PR in reviewWeeklyKSv2

Type

No type
No fields configured for issues without a type.

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions