The Bridge design pattern provides a solution:
Define separate inheritance hierarchies for an abstraction and its implementation.
Abstraction delegates its implementation to an Implementor object
instead of committing to an implementation at compile-time. Describing the Bridge design in more detail is the theme of the following sections.
See Applicability section for all problems Bridge can solve.

• The key idea in this pattern is to separate (decouple) an abstraction from its implementation so that the two can be defined independently from each other.
  The pattern calls the relationship between an abstraction and its implementation a bridge "because it bridges the abstraction and its implementation, letting them vary independently." [GoF, p152]
• Define separate inheritance hierarchies for an abstraction (Abstraction)
  and its implementation (Implementor).
  • The Abstraction interface is implemented in terms of (by delegating to) an Implementor object (imp.operationImp()).
  • "Typically the Implementor interface provides only primitive operations, and Abstraction defines higher-level operations based on these primitives." [GoF, p154]
• This enables compile-time flexibility (via inheritance).
  Abstraction and implementation can be defined independently from each other.
• Abstraction delegates its implementation to an Implementor object
  (imp.operationImp()).
• This enables run-time flexibility (via object composition).
  Abstraction can be configured with an Implementor object, and even more, the Implementor object can be exchanged at run-time.