What's your point, eeklipzz?
First, I'm going to say that I'm not a great writer. I'm a better ideater. Please bare with me.
The topic that I want to bring up is this. We are now looking at The Multi-channel Experience in a new way. We are embracing responsive web design techniques more and more as we march into this mobile lifestyle. How can we mentally process our design efforts in a way that streamlines communications with development, and offers the in-depth design capability that we so desperately want?
I submit to you the idea of designing with an object oriented approach. Developers have been building their programs in this way for many years. Programs written in an object oriented language are in essence functions within functions. One visual metaphor that may help you understand this idea is to look at the Matryoshka Doll.
In this metaphor, the program as you would see it would be the biggest doll. As you start breaking down the program into different functions, you basically be looking at the smaller objects within. Each smaller object can individually be broken down even further.
Can't we approach design in this same way? Ideally we'd determine the goals of the design and layout it's high level wire-frame. Within the wire-frame, we would find objects: page Title or main focal point, menus or secondary focal points, etc.
Objects in the Object Oriented Design Methodology should be designed with these attributes in order to best communicate to the developers what your intention is with the specific design object...
Object Oriented Design Object Attributes:
- Minimum and Maximum size specifications
- Object priority at this tier level
- Resolution Range
- ...anything else?
I did tell you up above that I'm not a writer, so I apologize if this seems disorganized. The idea that I'm presenting here is basically a call for a paradigm shift in the way we approach design. Yes, there are many publications that have different terminology that is used to describe a similar view on design ("microinteractions", etc...), but I believe this change in the way we think of design is necessary so that we can better speak the language of the development team.
I like to think of our communications with this metaphor. Image your in a boat. On one side of the boat is the development team. On the other side of the boat is the design team. Now image that one side says something to the other side. The other side doesn't immediately understand what the first side said... They must take time to comprehend the words that were spoken to them. As they think harder and harder, the boat starts veering to their side with the added weights. When they finally figure out what's been said, they reply with a message to the first side. The same thing happens to the first side, and now the boat is starting to veer towards the first side.
The boat is zig-zagging in the water. This zig-zagging is what slows the process of getting work done. Now, image if they spoke the same language. The zig-zaggs would be quite a bit less, which would result in a more efficient process.
The better we can communicate, the quick we can move forward. Objected Oriented Design answer.
Hope this inspires you to better flesh out this concept.