I have come across multiple instances of people thinking they're doing great architecture but it turns out their efforts turn out to be counterproductive. Interface Bloat is a common consequence of this.
Once, when I discussed the importance of Interfaces when doing polymorphism in PHP with a Scrum Master, he responded by telling me about an environment he once worked in where there was an engineer who spent months developing interfaces and thought he was doing brilliant architecture work. Unfortunately, it turns out he wasn't doing great infrastructure work, he was guilty of implementing Interface Bloat.
Interface Bloat is, as the name suggests, is where an Interface is excessively bloated. An interface can be so bloated that it becomes practically impossible for a class to be implemented any other way.
Interfaces should be used sparingly; do you actually need an interface if the class is only ever going to be implemented once and once alone (and realistically, no one is never...