Big little is fundamentally the correct architecture. It's not Intel's fault that the software guys making the Linux Kernel haven't fully supported heterogeneous yet.
In the long term, it'll be the optimal call for so many workloads. Thousands of server and laptop workloads care only about performance per watt, not peak single thread.
With these architectures I think often what the management should really look at is: "We currently employ 100 hardware engineers, and 30 software engineers, with this architecture, we're going to need 50 hardware engineers and 500 software engineers. Do we still think this is the right call?"
Because this problem is incredibly well solved (I believe?).
Scheduling priorities in operating systems an enormously well explored topic.
Put simply: you must incorporate heterogenous cores into the OS thread scheduler.
There's three actors here:
Hardware developers.
OS developers.
End user software engineers.
The hardware developers are running into physical constraints.
The fix is to shift the prioritisation between the different core types, big little, to the operating system scheduler.