If your users can describe a task simply, chances are the interface can be built to make that task at least that simple.
When designing a user interface, sometimes the less you know about the architecture, the better. The more time you spend working with the component objects, the more your mental model of the application uses these building blocks when conceiving of the application from all perspectives.
Address user goals
It's important to remember that your users are trying to accomplish something. The path from A to B will involve interaction with your component objects
on the backend. In all likelihood, the most usable solution will not involve letting (aka making) the user create and interact with the objects directly. Instead, the design should address goals and attempt to simplify the process and create an intuitive interaction. If your users can describe a task simply, chances are the interface can be built to make that task at least that simple.
Sure you created a super flexible architecture where all sorts of your objects could be hooked into each other in any number of ways—
The sky's the limit!
, you shout. Then you show the user the application and tell them that to do X, you create a type A object and a type B object, and hook them together like so, but to do Y, you create a type A object, a type B object, and a type C object, then hook the B to the C first, then the C to the A—be sure not to hook the A to the B!—and flip this switch. And voila! An unusable, unintuitive interface.
Speak plainly
Users are not application architects. They may be able to understand complex constructs in varying contexts, but why should they have to in your application? You should learn what the user's goals are and use
your knowledge of the architecture to obviate the magic that goes on behind the scenes. Speak in plain language on the interface; don't refer to the objects and their architectural relationships unless A) absolutely necessary, and B) you can do so in plain terms.
Do your best to make it so the user doesn't need to know what the man behind the curtain is doing. That's what the curtain is there for, after all.
