Your experience of what to align teams around

Team topology is a tricky topic and there's no right or finished way of doing it. We're currently working with a mix of platform/enabling teams and a set of rather stable cross-functional value stream aligned teams that ship for a type of high level use case and own an important high level job to be done / product area in this use case.

However, now having 8-10 teams we realize that this also has it's downsides, e.g.
- Teams are so stable that it's difficult to shift, fund, defund
- New products are harder to set up when teams are stable
- When trying to drive something that doesn't fit this paradigm, you'll need to talk to a lot of folks

I'm curious: what other ways of organizing product teams have you explored and maybe has worked for you? E.g. we're currently thinking if we should make more teams that own shared parts of our software "enabling" teams and then on top of this have very small "mission driven" teams that own 3-12 months missions. I'm afraid this is more of a project by project setup and lowers long term ownership ... however, it _feels_ a little more agile than the by the book Spotify model we're aiming for right now ...