Creating a good system for advanced users is not magic.
In practice, what tends to happen (when things go well, that is) is that people follow the same course as Douglas Engelbart’s development of the NLS system, which he called “bootstrapping”, and which we today might call “agile” or possibly “devops”. I.e. the initial users are using the system from day 1, and developers are constantly giving users more options and features to aid the users, and since the developers are either in close cooperation with the users, or the groups simply overlap, the finished system (that is, when it starts to change more slowly) is one in which the system is quite complex, but all users are also advanced users who can use it at high speed to tremendous advantage.
This is the point at which you should go back and add intermediate levels, tutorials, easy modes, child proofing, etc.
In practice, what tends to happen (when things go well, that is) is that people follow the same course as Douglas Engelbart’s development of the NLS system, which he called “bootstrapping”, and which we today might call “agile” or possibly “devops”. I.e. the initial users are using the system from day 1, and developers are constantly giving users more options and features to aid the users, and since the developers are either in close cooperation with the users, or the groups simply overlap, the finished system (that is, when it starts to change more slowly) is one in which the system is quite complex, but all users are also advanced users who can use it at high speed to tremendous advantage.
This is the point at which you should go back and add intermediate levels, tutorials, easy modes, child proofing, etc.