<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Comments on  Flowmaps and Frag-Grenades, Part 1</title>
    <link>http://www.boxesandarrows.com/view/flowmaps-and-frag</link>
    <pubDate>Tue, 07 Jul 2009 04:24:27 GMT</pubDate>
    <description>Five years ago, Colm Nelson captured a dream job as the Interaction Designer for the blockbuster Halo 3. In the midst of his busy schedule, he sits down with Bryce Glass for part one of a two-part series.</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>
    <item>
      <description>&lt;p&gt;Hi Andrew&amp;#8212;great question! I feel compelled to clarify that it was Colm&amp;#8217;s response to my question, so I will forward this on to him for clarification. But it&amp;#8217;s my understanding that the interviewer, Max, freely offered up the direct feedback as a wrapup to the phone call.&lt;/p&gt;

	&lt;p&gt;So&#8212;you&amp;#8217;re right&#8212;honest and unsolicited feedback during a phone interview is all-too-rare, and wonderful when its given (and, as you can see, gave Colm the chance to &amp;#8216;set things right&amp;#8217; and impress with his ambition and drive.) Perhaps, as interviewees, we should all get into the practice of -asking- for feedback as the last point of a first phone-interview. Perhaps something like&#8230; &amp;#8220;May I ask&#8230; how do you feel today&amp;#8217;s interview has gone? Do you have any concerns or questions that I can answer right now, or perhaps work to deliver an answer within [timeframe of our choosing]?&amp;#8221;&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/flowmaps-and-frag#content_39328</link>
      <guid>http://www.boxesandarrows.com/view/flowmaps-and-frag#content_39328</guid>
      <pubDate>Mon, 06 Jul 2009 20:46:31 GMT</pubDate>
      <author>Bryce Glass</author>
    </item>
    <item>
      <description>&lt;p&gt;Bryce,&lt;br /&gt;I&amp;#8217;m curious about your answer to &amp;#8220;And how did you get the job?&amp;#8221;...&lt;br /&gt;Did you ask for direct feedback in the phone interview or did they offer it to you and open the door for a 2nd chance to prove yourself? Getting honest feedback from a phone interview and getting a chance to redeem yourself is unique. I&amp;#8217;m usually left guessing what went wrong when a phone interview doesn&amp;#8217;t pan out&amp;#8230;&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/flowmaps-and-frag#content_39313</link>
      <guid>http://www.boxesandarrows.com/view/flowmaps-and-frag#content_39313</guid>
      <pubDate>Mon, 06 Jul 2009 13:26:29 GMT</pubDate>
      <author>Andrew R</author>
    </item>
    <item>
      <description>&lt;p&gt;And now, by&#8230; er&#8230; &amp;#8216;popular&amp;#8217; demand, &lt;a href="http://boxesandarrows.com/view/flowmaps-and-frag8" rel="nofollow" rel="nofollow"&gt;Part 2 of this interview&lt;/a&gt; is now up and available for comment.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/flowmaps-and-frag#content_31399</link>
      <guid>http://www.boxesandarrows.com/view/flowmaps-and-frag#content_31399</guid>
      <pubDate>Fri, 07 Jan 2011 19:40:14 GMT</pubDate>
      <author>Bryce Glass</author>
    </item>
    <item>
      <description>&lt;p&gt;Interesting start to an article&amp;#8230; but ditto on splitting into 2 parts being annoying.   There is no mention of when the next part will be posted.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/flowmaps-and-frag#content_31349</link>
      <guid>http://www.boxesandarrows.com/view/flowmaps-and-frag#content_31349</guid>
      <pubDate>Fri, 12 Dec 2008 18:39:43 GMT</pubDate>
      <author>Jackie Curry</author>
    </item>
    <item>
      <description>&lt;p&gt;Then I pass my crass disapproval on to them.&lt;/p&gt;

	&lt;p&gt;Why knowingly crass?  Because I was treated as an ad impression instead of a reader.  Give me a low marginal value and I will return the favor.&lt;/p&gt;

	&lt;p&gt;I don&amp;#8217;t buy the reasonable size argument because this whole page is under 100k with the comments.  The text is only 9k compressed.  None of the constraints in other mediums apply: there&amp;#8217;s no paper costs to cover and you don&amp;#8217;t have to fit into a 30 minute time slot.&lt;/p&gt;

	&lt;p&gt;Here are just a few ways to present an extra long article and leave the choice in the readers&amp;#8217; hands: &lt;br /&gt;- Link to full article at the end of intro.  The reader will know what they are getting into.&lt;br /&gt;- Pagination would allow limitless content in manageable sizes.&lt;br /&gt;- Editorial titles to delineate conversation topics.&lt;br /&gt;- Make content more stimulating with relevant images and figures (I&amp;#8217;m guessing these are in the next part???  This is about a richly designed video game and not even a screen cap.)&lt;/p&gt;

	&lt;p&gt;I never blamed anyone for my mistake.  This was feedback. Interesting to see if any real conversation will occur over my feelings however.  So far only smug deflection.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/flowmaps-and-frag#content_31222</link>
      <guid>http://www.boxesandarrows.com/view/flowmaps-and-frag#content_31222</guid>
      <pubDate>Tue, 02 Dec 2008 02:23:54 GMT</pubDate>
      <author>L long</author>
    </item>
    <item>
      <description>&lt;p&gt;L long &#8212;&#160;I just wrote the thing, I don&amp;#8217;t decide how it&amp;#8217;s apportioned and doled out to you. Take it up with the fine folks at Boxes and Arrows. (Tho&amp;#8217; I suspect that their reasons are less manipulative and Machiavellian than you seem to think&amp;#8212;the reason I was given is that they try to keep articles to a reasonable length and this one goes longer than that average.)&lt;/p&gt;

	&lt;p&gt;And I, too, regret your decision to submit to Digg if your brand of &amp;#8216;crap&amp;#8217; is typical of the quality of insight and analysis that appearing over there will bring over here. Don&amp;#8217;t blame me for your hair-trigger Digg finger. (Since when is &amp;#8216;reading the damn article&amp;#8217; considered &amp;#8216;due diligence&amp;#8217; anyway?)&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/flowmaps-and-frag#content_31218</link>
      <guid>http://www.boxesandarrows.com/view/flowmaps-and-frag#content_31218</guid>
      <pubDate>Mon, 01 Dec 2008 18:34:35 GMT</pubDate>
      <author>Bryce Glass</author>
    </item>
    <item>
      <description>&lt;p&gt;Bryce.  I submitted this to Digg because it is something that audience would find interesting.  I&amp;#8217;m regretting it now however.  It is my fault I didn&amp;#8217;t do the due diligence and read the entire article carefully.&lt;/p&gt;

	&lt;p&gt;The two part thing is crap.  Your business module (of gaining subscribers) is in direct conflict with your users&amp;#8217; needs. On a usability site none-the-less.  The only user-centric valid reason a for time delayed 2 part article online is you don&amp;#8217;t have the information yet.  If you were running a batch of tests and want to report the first half &amp;#8211; that makes sense.  All you are doing here is transcribing an interview and the first part barely introduces the subject.  If you wanted a couple pages, fine.  But this is manipulative and excessive.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/flowmaps-and-frag#content_31216</link>
      <guid>http://www.boxesandarrows.com/view/flowmaps-and-frag#content_31216</guid>
      <pubDate>Sun, 30 Nov 2008 22:03:39 GMT</pubDate>
      <author>L long</author>
    </item>
    <item>
      <description>&lt;p&gt;Thanks Bernie! Part 2 of the interview does indeed get into specifics a little more deeply and touches on some of the methods and deliverables that Colm employed during the H3 development process. So, tune in again&#8230;&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/flowmaps-and-frag#content_31215</link>
      <guid>http://www.boxesandarrows.com/view/flowmaps-and-frag#content_31215</guid>
      <pubDate>Sun, 30 Nov 2008 18:54:26 GMT</pubDate>
      <author>Bryce Glass</author>
    </item>
    <item>
      <description>&lt;p&gt;Bryce, thanks for the story&amp;#8230;it&amp;#8217;s very inspiring to hear stories like Colm&amp;#8217;s&amp;#8212;of interaction designers being taken more seriously.&lt;br /&gt;If you&amp;#8217;re planning to talk with Colm again, would you mind asking which specific methodologies transferred most easily from the consumer app industry to the gaming industry? Or about the differences between consumer application methodologies and game methodologies? It&amp;#8217;d be interesting to know which methodologies apply to more industries.&lt;br /&gt;Thanks again!&lt;br /&gt;Bernie&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/flowmaps-and-frag#content_31209</link>
      <guid>http://www.boxesandarrows.com/view/flowmaps-and-frag#content_31209</guid>
      <pubDate>Sun, 30 Nov 2008 06:04:46 GMT</pubDate>
      <author>Bernie Telles</author>
    </item>
    <item>
      <description>&lt;p&gt;@ Bryce &amp;#8211; Clear and brief talk &amp;#8211; It was just a trifle too short and too brief for my liking. I am eager to read the next part&lt;br /&gt;@ Olivier &amp;#8211; Why didn&amp;#8217;t you post your opinion under the topic forums? &lt;a href="http://boxesandarrows.com/topics" rel="nofollow"&gt;http://boxesandarrows.com/topics&lt;/a&gt; &amp;#8211; Your comment has nothing to do with this story. Sad!&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/flowmaps-and-frag#content_31191</link>
      <guid>http://www.boxesandarrows.com/view/flowmaps-and-frag#content_31191</guid>
      <pubDate>Mon, 15 Dec 2008 19:33:49 GMT</pubDate>
      <author>Holger Maassen</author>
    </item>
    <item>
      <description>&lt;p&gt;The following bothered me enough to register. I cannot understand why a site that writes about usability uses such a small line-height for the text. It&amp;#8217;s currently at 1.3em which many find too low for easy reading. Just increasing it to 1.4 makes the text much more readable. Sorry for the rant but it is a pet peeve of mine.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/flowmaps-and-frag#content_31150</link>
      <guid>http://www.boxesandarrows.com/view/flowmaps-and-frag#content_31150</guid>
      <pubDate>Mon, 15 Dec 2008 19:32:44 GMT</pubDate>
      <author>Olivier Olivier</author>
    </item>
  </channel>
</rss>

