Separating use from construction - After

gistfile1.java

public class BusinessObject {
  public void actionMethod() {
    // Other things

    //No Change!
    Servicec myServiceObject = Service.getInstance();
    myServiceObject.doService();
    // Other things
  }
}

abstract class Service {
  private Service(){ //any needed construction behavior }
  public static Service getInstance() {
    return ServiceFactory.getService()
  }
  abstract void doService();
}

class ServiceFactory{
  public static Service getService(){
    if (someCondition) {
      return new Service_Impl1();
    } else {
      return new Service_Impl2()
    }
  }
}

Service_Impl1 : Service {
  void doService() { // one implementation }
}
Service_Impl2 : Service
  void doService() { // different implementation
}

I don't see how ServiceFactory helps here. It seems to muddy the waters. I would inline ServiceFactory.getService() and put the conditional logic directly into Service.getInstance() with a REFACTOR comment that says "push this decision out to clients!"

Making Service abstract certainly sounds reasonable, but a REFACTOR comment that says "make me an interface, please".