There was mention in another comment about Peter Rawlinson not having a strong background/expertise on software. If the initial approach was ad-hoc, then they are already buried in technical debt. I am not sure how widespread that term is for other fields, but it more or less embodies the cost from inefficiency in design and implementation in regards to forward progress of development. The undertaking of solid engineering from a software perspective with long-term outlooks is equally culture, awareness, and experience driven from the top down. An equivalent person to Peter Rawlinson for the traditional engineering would have been necessary from the outset or strong internal motivation.
As a software engineer, I have seen many, many projects drowning in technical debt with development reduced to a snail's space. If this is in fact the case, the hope would be for the new head of software to focus efforts on making the software robust from a design and implementation standpoint. This may even be the case with the "major" update and hot patches leading up to it. A strong foundation to build upon, much like traditional engineering, will bring forth the features and capabilities we want faster in the long run. I think his background is Apple? They have solid software and best practices, regardless of being an Apple fan or not.
Someone mentioned a possible culling of the initial software engineers in a different thread. I would argue this signifies the first steps in revitalizing the core software, similar to dropping all those high executive people.