Half a century ago, Stern discussed this attribute of an artistic object and called it apparency. While art is not limited to this single end, he felt that one of its two basic functions was "to create images which by clarity and harmony of form fulfill the need for vividly comprehensible appearance." In his mind, this was an essential first step toward the expression of inner meaning.
The personal experience of most of us will testify to this persistence of an illusory image long after its inadequacy is conceptually realized. We stare into the jungle and see only the sunlight on the green leaves, but a warning noise tells us that an animal is hidden there. The observer then learns to interpret the scene by singling out "give-away" clues and by reweighting previous signals. The camouflaged animal may now be picked up by the reflection of its eyes. Finally by repeated experience the entire pattern of perception is changed, and the observer need no longer consciously search for give-aways, or add new data to an old framework. They have achieved an image which will operate successfully in the new situation, seeming natural and right. Quite suddenly the hidden animal appears among the leaves, "as plain as day."
Everything points to the conclusion that the phrase 'the language of art' is more than a loose metaphor, that even to describe the visible world in images we need a developed system of schemata.
Start all of the pieces of work a little bit earlier. The key to starting work early is not succumbing to the pressure of having to finish the work. Don’t worry about finishing. If you’re a developer, you can start doing things while your design or information architect are working because a lot of your work actually isn’t dependent on their work. Some of it is, so you probably won’t be able to finish, but that shouldn’t stop you from starting.
Share Work-in-Progress Early and Often
When you share work-in-progress, share it with the caveat that no feedback is needed at this point. You’re simply sharing it to let people know where you are. For example, if you have to make 12 wireframes, share it when you finish 2 or 3. Rather than spending a whole week to drop 12 wireframes, share 2 – 3 wireframes every 2 days. The more often you do this, you start to build rhythm, and rhythm builds momentum.