[Figma] Improve onboarding for complex tools

Basically, every time I work on a feature, I have to dispel the myth that the solution needs to be intuitive to the point that every internal stakeholder like engineer or product manager understands how to use it intrinsically. Not only is that a fool’s errand (they are not the user) but it also sets us up to chase our tails trying to achieve something that’s impossible. I generally push back on the perception of the feature from internal stakeholders until we complete some preliminary testing, and eventually formative testing, which will give us a better idea of what makes sense to the different user personas and what doesn’t. Doctors especially are a finicky bunch, and they tend to prefer (counter-intuitively based on other user types) more complexity, information, and visible actions. They count their clicks, every second is precious, and they’d generally rather learn a complicated tool than try to navigate through a series of progressive disclosures in a very surface-level simple version of the tool. I’m also tired of hearing that myth repeated by UX designers when they mentor juniors. It’s a fine general rule of thumb, but when you start working on these types of tools, it’s just not a realistic nor responsible expectation that someone can just pick it up without the need for any sort of training or help tools built in. Especially with medical safety under consideration. And yes. I agree that the tool should use common patterns where possible to reduce the difficulty of learning the tool, but I think it’s entirely unrealistic to expect someone to just pick up a tool designed for processing neurological signals without any sort of guidance. I can’t show or say much more about the tool because of NDAs, but I can say that if you want a similar experience in terms of overall complexity, look to data processing SaaS tools like Monarch Money or Smartsheet. What are some good practices to address this issue?