Pattern Recognition
Recognising that a novel-looking problem is an instance of one you have seen before, and knowing which parts of the previous solution transfer.
This is most of what experience actually is. "The reporting team wants live data from the transactional database" is CQRS or a read replica. "Two systems disagree after a network blip" is a dual-write. "It works fine until Monday morning" is a cold cache or a scheduled job collision.
The value is speed and the risk is over-fitting. The same recognition that lets you skip to the solution also lets you apply the previous solution to a problem that only looks similar — which is how organisations end up with a message broker because the last place had one.
The corrective habit is to state the pattern explicitly and then check the forces: this looks like X, X applies when A, B and C hold, do they hold here? Naming it makes it falsifiable, which intuition on its own is not.