Consensus and common goals aren't groupthink.
Groupthink is specifically about when people stop thinking individually, and take the group's position to be correct-by-default. Consensus and common goals can be achieved without that assumption.
Groupthink, in software architecture, happens when we can no longer question the basis for a design or assumption. Perhaps the design made perfect sense once, but now we're trying to scale to 1000+ servers, not just 5-10. Communication overhead is killing us, groupthink promotes (for too long, ultimately to the detriment of the business and its customers) the idea that the architecture is beyond question. Consensus and common goals are different. If the architecture is limiting the business, then that can be an agreed upon idea, but not actionable yet. Maybe we realize that other things need to be addressed first (our build system, CI/CD pipelines, testing systems) in order to make architecture updates even feasible.
Groupthink would deny even addressing those concerns because they still won't accept that the architecture is limiting the business.