<?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 colm nelson</title>
    <link>http://www.boxesandarrows.com/person/31087</link>
    <pubDate>Tue, 07 Jul 2009 04:24:27 GMT</pubDate>
    <description>Comments by colm nelson</description>
    <item>
      <description>&lt;p&gt;Hi Andrew &amp;#8211;  Bryce has it right.  In this case, Max volunteered the feedback as a wrap up to our conversation and it was definitely helpful.  What I took away was that there may or may not be another conversation so that&amp;#8217;s when I then took the initiative to follow up with the concept document, based on several topics of the conversation, Max&amp;#8217;s feedback and my own research.  I think Bryce has a good point about asking for feedback if the vibe is right.  What I would say as well is that it is always worth following up with a response immediately after a phone interview, if nothing else but to express thanks for the courtesy of the conversation and consideration.  This is also potentially an opportunity to include some additional thoughts about how you feel that you may contribute to the organization based on the conversation and solicit feedback for next steps.  I&amp;#8217;ve been on the other side of the interview loop with phone screens and it always makes a good impression when a candidate follows up with a thoughtful response.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/flowmaps-and-frag#content_39330</link>
      <guid>http://www.boxesandarrows.com/view/flowmaps-and-frag#content_39330</guid>
      <pubDate>Tue, 07 Jul 2009 04:24:27 GMT</pubDate>
      <author>colm nelson</author>
    </item>
  </channel>
</rss>

