<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Boxes and Arrows: Comments by Manish Pillewar</title>
    <link>http://www.boxesandarrows.com/person/3359</link>
    <pubDate>Thu, 15 Mar 2007 13:10:25 GMT</pubDate>
    <description>Comments by Manish Pillewar</description>
    <item>
      <description>&lt;p&gt;Bubbles and the wireframes:&lt;br /&gt;I reckon this level of detailing for the wirefrmes is required when the designer is not present while presenting the concept. Have been working in a constantly changing client scenario, I find it easier to just blurr out the concept details: what section would load, whats on focus and how does it appear etc. The rest is self evident. Normally even for a &lt;span class="caps"&gt;RIA&lt;/span&gt;, the wireframe would be used only to show placeholders and the IA and Navigation concept. Maybe, content at times. A clients development team would definitely catch up on the nature of the UI elements within minutes of the presentation. A Powerpoint low/medium fidelity prototype should be enough to get across the ideas. Else, get it simulated on Visio/asp/etc. I find this level of detail unnecessary when the designer is there to explain it.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/the_guided_wire#content_5428</link>
      <guid>http://www.boxesandarrows.com/view/the_guided_wire#content_5428</guid>
      <pubDate>Thu, 15 Mar 2007 13:10:25 GMT</pubDate>
      <author>Manish Pillewar</author>
    </item>
    <item>
      <description>&lt;p&gt;The should be some way to undo a vote. I clicked on the offensive option by mistake. Ignore that Afshan. Looking forward to read your article.&lt;br /&gt;Cheers!&lt;br /&gt;Manish&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/idea/view/5734#content_5739</link>
      <guid>http://www.boxesandarrows.com/idea/view/5734#content_5739</guid>
      <pubDate>Mon, 02 Apr 2007 11:03:37 GMT</pubDate>
      <author>Manish Pillewar</author>
    </item>
    <item>
      <description>&lt;p&gt;Communication: &lt;br /&gt;This has to be polished to a professional extent. Newbies need to practice clear communication in order to articulate their ideas to the clients at times. Clear and professional communication also helps in defining the exact goal of the UI exercise and helps to eliminate ambiguity. Junior designers need to practice writing professional emails and polish their talk as well.&lt;br /&gt;Subset : Vocabulary: &lt;br /&gt;Again from a professional perspective, designers need to learn the talk. Know and practice using UI jargons, read a lot for the same. Designers need to be armed with examples for every UI design they suggest as well. Clients, often from the business side, need to be given examples they know &amp;#38; UI&amp;#8217;s they have seen, to understand things better.&lt;br /&gt;My two cents.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/talent-isn-t#content_5948</link>
      <guid>http://www.boxesandarrows.com/view/talent-isn-t#content_5948</guid>
      <pubDate>Wed, 11 Apr 2007 04:19:06 GMT</pubDate>
      <author>Manish Pillewar</author>
    </item>
  </channel>
</rss>
