I think you don't need a pattern in this case, but a principle. In this case, the Liskov Substitution Principle. Your small Views should implement the same Interface, so that the large View can manage them (to the extent that is needed based on the language you are using). The data Classes should also use this principle, so that the small View can be passed in data and return it to your wiring code without special consideration for what, specifically, is going on.
I find that I haven't been able to make an application of any complexity where Liskov Substitution is perfect, and that is possibly due to limitations in me vs. the principle. But I tend to think of it like a soda machine in a restaurant. You care about the specific type in the back room where you hook up the tubes to the boxes of syrup, and you care again when it's in your cup, but in between it all goes through the tube the same.
So I usually will have my endpoint Views type-check the IDataObject to make sure it's congruent with the View. The other end (the back room) for me is typically a Builder and/or an Abstract Factory that has references to many specific factories and calls on the correct ones based on some condition inherent in the data (I typically have a tag in the XML data source that says "pull the factory registered under this name" and a hash that contains the Factories).
I am fortunate to develop in Flash, and I allow Flash itself to be the Factory for my Views and simply pick up references to them once they've been instantiated, but if you have to manually construct Views, you can probably use something similar to what I've described for data construction.
I applaud that you're thinking through the design on the front in, because in real life few bosses will allow you to go back and rip out your initial experiments in favor of a more robust/maintainable design. Note that it is enough in the short-term to develop your Views and Model to Interfaces--you should find it much easier to add some kind of Factory later than it is to redo the logic that your management can physically see.