The Factory Method design pattern solves problems like:
How can an object be created
so that subclasses can redefine which class to instantiate?
How can a class defer instantiation to subclasses?
See Applicability section for all problems Factory Method can solve. See Solution section for how Factory Method solves the problems.

• An inflexible way is to create an object (new Product1()) directly within the class (Creator|operation()) that requires (uses) the object.
• This commits (couples) the class to a particular object and makes it impossible to change the instantiation (which class to instantiate) independently from (without having to change) the class.
• That's the kind of approach to avoid if we want to create an object so that subclasses can redefine the way the object is created.
• For example, designing reusable classes that require (depend on) other objects.
  A reusable class should avoid creating the objects it requires directly (and often it doesn't know which class to instantiate) so that users of the class can write subclasses to specify the instantiation they need.