🔄 The secret to process

Process/workflows/tools should be good enough that they help the people doing the work. They are not just an administrative tool. Some examples:

• Git helps me manage my own work, so I use it even on personal projects where collaboration is not needed.
• Gitea issues are so fast and easy to use that when working on hard problems, I automatically create an issue to log progress. It is easier and faster than keeping notes anywhere else.
• Gitea releases are so quick and easy to use that I use them even for internal releases there rather than composing an email.
• Jitsi Meet is easier than a phone call, so we use it for most calls and have the benefit of screen sharing, video, multiple participants, etc.
• Code formatting tools help me as a developer, so I gladly integrate them into my editor.
• Part numbers are so easy to pull and use that they help me manage parts and assemblies for my prototype builds, so I pull them early in the design process and integrate them in CAD libraries.
• Tests are easy to create and run locally, so I create them as part of my development process.
• Documentation is integrated with the design files and easy to create, edit, and track. Thus, documentation is an integral part of the development process vs. an afterthought.
• End to end tests are easy to run by anyone, so when there are issues to debug, they are tool that is regularly used by developers.
• It is easy to purchase things needed to do my job and improve the company as everyone is issued a credit card, and expense reports are generated automatically. There is no motivation to bypass the process.

Tools/workflows/process should help the people doing the work go faster, not slow them down. If this is the case, you won't need to force them on people. If this is not the case, the process needs work.