Yes, and it's called something oh so simple, "measure twice cut once." What you are attempting to do, when you want an interface to be right, or code to be right, is to try something, see if it leads to the right answer. If it does, continue. It's not a perfect analogy, but bear with me.

What I tend to do w/ code is to prototype something - especially if it's hard either 'cause it's large or it's complex. If it's not something I can fully churn out in a few hours, I do a bit of it, and walk away at a good stopping point. Why? 'cause that is a one time measurement. If I can come back, and see some sense to it, and not want to scrap it, that is my second measurement. More likely, though not completely 100% all the time true, I've done something right. It's like proof reading.

It's the same thing you do w/ client facing interfaces. You propose it then prototype it to make sure that things are really what they want. In your case, you are your client, so you need to do a little, and come back fresh to make sure you are making sense. Taking breaks helps! :)