A process I like to use and that might be helpful to you is what I call "Technical Initiatives". The idea is to allow everyone to suggest and implement technic

A process I like to use and that might be helpful to you is what I call "Technical Initiatives". The idea is to allow everyone to suggest and implement technical improvement by providing a process to do so. For each idea, the owner fills a spec to describe it. The main ideas are: - Be transparent on what we want to do and our issues, the doc should be public and comments-friendly - Follow an advice process by proactively asking people to improve or challenge the idea - Always have by a trial with time boundaries and goal A template could look like this: - Owner: Name - Title: to easily speak about it - Reviewers: people who should definitely have a look - Summary - Why: Describe what are the issues with the current process, the bugs or similar. - What is the change - How to implement the change - Duration of the trial - What should we've achieved at the end of the trial In your situation, it might be something like: - WAthrowaway - Staging env - Reviewers: Founder, Senior Eng #1... - Setup a staging environment - We encountered critical issue #1 on October 1st, issue #2 on October 2nd - A staging environment would allow to catch this bugs before it is on production - 1. Create a staging env 2. Create a staging branch 3. block push on master 4. PR staging / master - 1 month - Critical issues happen on staging and not on master PS: It's inspired by http://www.reinventingorganizationswiki.com/Decision_Making http://www.reinventingorganizationswiki.com/Decision_Making