Patterns in the Solution Design Process

[Frankie]

Where and how in the design process do you bring patterns (as formalized by
the GoF) into play? In particular, after identifying specific feature
requirements, do you...

ONE: go hunting (quick as that effort may be) for a pattern that addresses
the design problem? And then design a specific solution by using the
relevant pattern(s) as a guide?

Or

TWO: do you tend to design a solution and object model (without explicitly
attempting to frame the solution in terms of patterns - or without
attempting to use a pattern as a sort of blueprint), then communicate about
your solution later in terms of patterns that are more-or-less relevant -
and that you may or may not have closely approximated in your design?

I ask because I'm curious about the role that patterns do (or possibly
should) play early in the design process.

I do understand other valuable roles of patterns - like the fact that they
help us to communicate more succintly ad hoc - but I'm particularly
interested in knowing how you bring them into play in the design process -
before the solution is designed.

Thanks!