Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove the Welcome Checklist for all users #28948

Open
daniellekirkwood opened this issue Jan 8, 2025 · 5 comments
Open

Remove the Welcome Checklist for all users #28948

daniellekirkwood opened this issue Jan 8, 2025 · 5 comments
Labels
A-Onboarding The users first experience of Element, whether that be first impressions or first tasks. T-Enhancement T-Task Tasks for the team like planning X-Needs-Product More input needed from the Product team

Comments

@daniellekirkwood
Copy link
Contributor

Your use case

What would you like to do?

Remove 'the use case question' and the 'welcome checklist'

The future plans of OIDC and SSO make this screen nearly redundant as very few users will see it. The use case question does not currently show the correct Welcome checklist anyways so we may as well remove that too while we're there.

In the future we would like to re-introduce this page and maybe have it configurable by the HS Admin.

Screenshot 2025-01-08 at 17 56 47 Screenshot 2025-01-08 at 17 57 21

Epics relating to introducing it:

Why would you like to do it?

It was valuable at the time and gave us learnings. Now it is not super functional and brings no added value to the product team or user's experience with element web. We will reintroduce it in the future. For now we should remove it.

How would you like to achieve it?

🤷 CTRL+A DEL ? 😉

Note

This screen still exists and can be replaced and will endure:
Screenshot 2025-01-08 at 17 57 48

Have you considered any alternatives?

No response

Additional context

No response

@daniellekirkwood daniellekirkwood added T-Enhancement X-Needs-Product More input needed from the Product team labels Jan 8, 2025
@dosubot dosubot bot added A-Onboarding The users first experience of Element, whether that be first impressions or first tasks. T-Task Tasks for the team like planning labels Jan 8, 2025
@daniellekirkwood
Copy link
Contributor Author

daniellekirkwood commented Jan 8, 2025

@pmaier1 i found a complication...

Screenshot 2025-01-08 at 18 03 34 quite a few people click the buttons... Screenshot 2025-01-08 at 18 07 59 Shows that 9,000 people clicked to go to the welcome screen in one month...

So the options are:

  • Remove it and reintroduce it, having this data as a reason to do that sooner rather than later
  • Make the page permanent for all users regardless of when and where they signed up

Keep in mind that data is tracked for users who explicitly turn it on and we estimate that to be about 10% of the base

@daniellekirkwood
Copy link
Contributor Author

Suggestion... These screens were intended to improve D1. We could remove it and:

  • if D1 drops a little bit prioritise the new onboarding flow sooner
  • if D1 drops a lot reinstate the checklist
  • if D1 doesn't move at all, delete the code and come back to it when we get to the onboarding flow

WDYT @pmaier1 & @t3chguy

@t3chguy
Copy link
Member

t3chguy commented Jan 8, 2025

delete the code and come back to it when we get to the onboarding flow

What's the difference between remove it and delete the code? If this PR was merged the code would be deleted but perpetually available right here and in git blame for if we wanted to bring it back. Disabling it via a flag would add yet more tech debt and potentially never be removed due to time constraints. There's about 5 touchpoints which would gain complexity in where this code hooks in.

@daniellekirkwood
Copy link
Contributor Author

Great, no difference needed. Thanks

@t3chguy
Copy link
Member

t3chguy commented Jan 10, 2025

@daniellekirkwood can we land #28943 then? It'd ship in 2.5 weeks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Onboarding The users first experience of Element, whether that be first impressions or first tasks. T-Enhancement T-Task Tasks for the team like planning X-Needs-Product More input needed from the Product team
Projects
None yet
Development

No branches or pull requests

2 participants