Good Constraints for Onboarding and ScalingUp
/2025-06/session/3-d/
Topics:
Convener: David Rowley
Participants who chose to record their names here:
- Charles Iliya Krempeaux (@reiver@mastodon.social)
- Scott Jenson (@scottjenson@social.coop)
- JohannaB
- Kirsten Lembertsen
- Scott M. Stolz (@scott@loves.tech, @scott@codejournal.dev, @scott.codejournal.dev)
Notes
- what if had certification for Mastodon servers so that joinmastodon had confidence in sending new users there as part of a default choice
- mastodon team discussing starter packs
- first UXer of Mastodon, aware of challenges,seeks new fresh ideas.
- DR: What if when new users joined, they have a very, very limited experience
- they couldn’t, for example do a lot of the regular features
- DR: metaphor of “constraints” being similar to very young children at day-care holding a rope when walking outside
- CIK: What if when new people joined, we figure out why (ex: interest in some famous singer, talk about some specific politics, etc), and then give them that experience (maybe by auto-following certain people and hash-tas, auto-joining certain groups, maybe auto-muting certain things, etc).*
- Some known, published constraints can be good for minimizing tech support, techinfrastructure, etc. and they are not good for UX but they might e justified and known. E.g. 1,2,3,4,5,