If you hate the process, then it's probably easiest to find another job with process you can tolerate - especially if the current process is working for your company. If enough people are frustrated by it you may have some luck getting the company to introduce a new process, but I'd expect an uphill battle.
If it's really software engineering and architecture that bothers you, though, I'd strongly suggest giving it another try. "Making something that just works" now, is awesome when you're writing the code in the first place, but it's an absolute maintenance nightmare, and it won't be long before you're drowning in tech debt.
A whole team where everybody says "lets just do the first thing that works" may work for a treehouse or a shed, but you'll never build a skyscraper or big project that way.