Ideas and implementation get confused when planning a new feature. "We should allow our users to do this" turns into "We should allow them to do it this way"

Sometime this way is bad. Of course it is: the impmementation is a first draft. It needs some attention still

But the idea is good

It's natural to focus on the how (implementation) as soon as we have the what (idea). A bad implementation can ruin the idea

When planning features, separate the how from the what. Is it a good idea? Okay, commit to it. Figure out implementation in a separate discussion