Do you think the C suite will take action to remove the prediction managers who continue to ignore Nintendo? We saw it at Sega yet nothing has changed. Square just promoted the guys who presided over the IP’s decline.
I‘d argue they don’t have to. As I have to remind people, the C-suite are the ones who write management’s cheques, so if the C-suite is unhappy, they can force their hand at any given moment and all those managers can do about it is swallow their pride or take a walk. It likely won’t be as dramatic as Nagoshi, but that was a special case because he was part of the C-suite himself and the rest of them lanced him like a boil.
The thing that will most motivate those decisions by the C-suite will be the technology teams. While there is some overlap between devs and the technology teams, they are typically separate units.
Typically, these tech teams work with a hardware team at a platform holder (like Nintendo’s Platform Technology Development team, as one example, usually through a liaison in the business/developer relations team), starting as early as is feasible. Once a technical spec outline is available, the platform holder’s tech team sends that spec (under the strictest NDA, usually along with a hardware emulator, a rudimentary facsimile of the tech using physically modified off-the-shelf parts or both) for them to test their software development tech against it. This for sure happened with Capcom and Switch, as early as late 2014, they went to a Game Creators Conference panel together in 2017 and
said as much. Seriously, most news outlets only took the news about the RAM bump Capcom requested from this panel, but the insights into the beginning days of new hardware with 3rd-parties is too instructive to not read it in full. This is the start of what they referred to as the new hardware verification process.
Now obviously, in the case of hardware like PS5 or XBS, new hardware verification is more about how far they can push this new hardware beyond current limits to plan for new development tools, and programming to account for differences in the current development environment. With something like Switch, the latter is still a consideration, but the testing is first and foremost about full compatibility with existing tools. Additionally, RE Engine was just starting to take shape, which is what the origin of the RAM bump was about; Capcom felt that more RAM was required to meet the minimum spec for even standard compatibility with RE Engine (albeit not all of its technical features) and Nintendo obliged. In addition, when making final confirmations on final CPU/GPU clocks, Capcom provided Nintendo in-development game builds to optimize around; this is apparently now standard practice for Nintendo.
This info is provided in pursuit of the reason why this team is so instrumental in getting developers on board, because these new hardware verifications are how the C-suite and developers are informed about what the hardware is capable of, costs associated with straining past its limitations, etc. That means this process is how preliminary budgetary planning is outlined for projects, as well as what in their current pipeline can be released at all. While technical capability is info given to the devs and managers, the cost estimates are usually given to the C-suite to decide their R&D budgeting with management. So platform holders making a solid positive first impression with preliminary hardware spec has a lot of impact on the outcome of software released on a platform in the first few years and, if it was found to be lacking for certain projects in the pipeline, will potentially diminish future support because of estimated exorbitant costs of down-porting that may not be as accurate due to changes in final hardware performance.
But there’s also a piece of responsibility that 3rd-parties have to own. At that panel, Capcom talked about asking to include native support for HLSL shaders and the Nintendo rep said Capcom was one of the only devs to ask for that, then asked for a show of hands from developers in the crowd who wanted that to then basically chastise them. To paraphrase, he said "don't be polite and take the hardware as-is, if a simple need like that isn't met, just tell us plainly and we will try to make it happen within an acceptable hardware cost." That outlines that developers were so used to just not asking for more and leads me to believe that Nintendo realized that with devs saying how insufficient their hardware was in public after the fact, they weren't getting good feedback in this new hardware verification process. Perhaps, with the upcoming hardware cycle, devs will get more of what they need to make their games happen on new hardware a lot more smoothly.
(this is the TL; DR part) All of this is to say that, if Nintendo presents hardware that impresses the technology teams at publishers well enough and they take and implement feedback swiftly, that will have a lot more to do with a change in attitude at publishers compared to the last time around, as it will likely deflate expected down-port cost estimations and generally leave a more favourable impression right off the hop that motivates more projects hitting the platform overall. Combine that with an expectation of a repeat in hardware sales success and it will highly motivate the C-suite to over-ride some of the objections to producing marquee software on the platform.