These 10 steps are more common sense than a plan; certainly, developers have some variation on this process they follow already. Why not apply the same principles to Power Users, too?
A governance policy is enforced that requires that all users with an interest in using SharePoint Designer be taught basic documentation techniques.
Power Users are either encouraged to create their own SharePoint Rudder libraries or are provided an organization-approved templated version by the SharePoint team.
Upon initiation of every SharePoint project, the designated OneNote template is used and the five Ws are captured.
Users are provided a test environment so that no production space is harmed in the expansion of SharePoint skill.
Power Users are granted access to SharePoint Designer, and creation of powerful business solutions commences only in the test environment.
The initiation meeting notes are combined with more documentation related to the solution being developed.
Once the working solution is complete, approval workflow is sent to the SharePoint team asking for review. This includes links to the test solution and the OneNote documentation.
Approval is granted, and the Power User builds the solution in the production environment to much acclaim of her fellow employees/stakeholders.
At the monthly SharePoint Power Userusers meeting, this solution is highlighted and demonstrated so the knowledge is shared and more people benefit from this example.
After 18 months, a workflow is triggered, asking the original creator of the solution for a review—this means making changes to ensure all development on the platform stays up to date.