Is your application highly complex? Are your users highly technically skilled and constantly using this application? Highly complex UIs arise from highly complex situations - think plant-processing control rooms - lots of dials, switches and blinking status lights.
If the answer is: the user doesn't regularly use this piece of software, or this application is ancillary to their primary task, then you should fall back to simplicity, remembering that simplicity and directness is difficult because it involves paring back what is less used.
Here are some general guidelines:
Go back to first principles. Understand the key process, identify the critical path and make it simple to perform common tasks.
Make it easy to remember context. Recently accessed searches are more likely to be re-used. Do you store these?
Avoid modal interactions, because the user may have to jump out of their current activities midstream to perform another task, and then return to where they were.
A significant portion of support time for enterprise product is due to administrators misconfiguring the product. Nail those down so that it is difficult to get wrong.
