What is the point in selling a horse saddle for one who does not own a horse?
The interface segregation principle (ISP) states that no client should be forced to depend on methods it does not use. ISP splits interfaces that are very large into smaller and more specific ones so that clients will only have to know about the methods that are of interest to them.
Clients should not be forced to depend upon methods that they don't use.
ISP is intended to keep a system decoupled and thus easier to refactor, change, and redeploy.
When we design an application we should take care how we are going to make abstract a module which contains several submodules. Considering the module implemented by a class, we can have an abstraction of the system done in an interface. But if we want to extend our application adding another module that contains only some of the sub-modules of the original system, we are forced to implement the full interface and to write some dummy methods. Such an interface is named fat interface or polluted interface. Having interface pollution is not a good solution and might induce inappropriate behavior in the system.
If the design is already done fat interfaces can be segregated using the Adapter pattern.