<?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 Noah Iliinsky</title>
    <link>http://www.boxesandarrows.com/person/8738</link>
    <pubDate>Wed, 06 Jun 2007 00:18:33 GMT</pubDate>
    <description>Comments by Noah Iliinsky</description>
    <item>
      <description>&lt;p&gt;My TC graduate program at the University of Washington ( &lt;a href="http://uwtc.washington.edu/" rel="nofollow"&gt;http://uwtc.washington.edu/&lt;/a&gt; ) had a lot of focus on documentation and technical journalism. We are also strong in the areas of user research and usability testing (due in no small part to our department chair, Judy Ramey, a respected usability expert). My personal focus, information, interface, and interaction design, was addressed, but not to the same extent as the research and documentation branches.&lt;/p&gt;

	&lt;p&gt;However, I think it all fits together well. When people ask what TC is, or what our department does, I have a standard response: it&amp;#8217;s about understanding an audiences need for information, and then satisfying that need, whether by documentation, journalism, a web page, software product, or device interface. By that definition, we all fit under the larger TC umbrella. Anyone with good TC skills probably has a good foundation upon which to build a UX skill set.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/using-technical#content_8631</link>
      <guid>http://www.boxesandarrows.com/view/using-technical#content_8631</guid>
      <pubDate>Wed, 06 Jun 2007 00:18:33 GMT</pubDate>
      <author>Noah Iliinsky</author>
    </item>
    <item>
      <description>&lt;p&gt;Joe, this is a great lesson.&lt;/p&gt;

	&lt;p&gt;I&amp;#8217;ve worked for several startups. One was an unqualified success: we were bought out for many millions of dollars and the founders are now rich. Two others languished or underperformed, despite brilliant ideas and dedicated, capable staff. They key difference was the willingness of the successful founders to change course and adapt to circumstances and feedback (changing our product focus while leveraging our underlying technology), rather than staying the unproven or unlikely but hoped-for course. ( I expand on this just a bit more here: &lt;a href="http://blogs.exbiblio.com/2006/08/15/departure-noah-iliinsky/" rel="nofollow"&gt;http://blogs.exbiblio.com/2006/08/15/departure-noah-iliin&amp;hellip;&lt;/a&gt; )&lt;/p&gt;

	&lt;p&gt;I&amp;#8217;ll toss one more metaphor into play. Apply it to business, politics, or wherever you find it fits: they say it&amp;#8217;s a bad idea to change horses in mid stream, but when the horse is in over its head&amp;#8230;&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/it-seemed-like-the#content_10478</link>
      <guid>http://www.boxesandarrows.com/view/it-seemed-like-the#content_10478</guid>
      <pubDate>Tue, 24 Jul 2007 00:46:48 GMT</pubDate>
      <author>Noah Iliinsky</author>
    </item>
    <item>
      <description>&lt;p&gt;Joe, I didn&amp;#8217;t get stuck in the companies that weren&amp;#8217;t doing as well. I had excellent, educational experiences, and got out when it was clear that there were better opportunities out there. Both companies are still around, but not (yet?) changing the world.&lt;/p&gt;

	&lt;p&gt;If I was to give one piece of advice I&amp;#8217;d say make sure the leadership team is really more than one individual. The successful company had two excellent founders who very actively sought input from a board of investors and board of advisers. The other companies were each run by the individual founder, and in both cases had no real obligation to any investors or board, so they were allowed to drift, rather than proving themselves. Accountability is good incentive, it turns out.&lt;/p&gt;

	&lt;p&gt;Hope that&amp;#8217;s helpful to someone. Good luck to all!&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/it-seemed-like-the#content_10686</link>
      <guid>http://www.boxesandarrows.com/view/it-seemed-like-the#content_10686</guid>
      <pubDate>Thu, 26 Jul 2007 22:25:42 GMT</pubDate>
      <author>Noah Iliinsky</author>
    </item>
    <item>
      <description>&lt;p&gt;Hi Patrick,&lt;/p&gt;

	&lt;p&gt;This is an interesting approach. I really like the accessibility of the final map product.&lt;/p&gt;

	&lt;p&gt;I don&amp;#8217;t know if you used consistent axes for each map and sub-map, but I&amp;#8217;d be curious to hear how you chose directions for the various lines. My mental model says other intranet pages should be &amp;#8220;sibling&amp;#8221; pages, to the side (on a horizontal line), child pages should be below (on a vertical line), and external pages are &amp;#8220;out there&amp;#8221; (maybe at an upward diagonal). Of course number of nodes to manage will affect your layout approach. I do like the choice of colors for each line.&lt;/p&gt;

	&lt;p&gt;For deeper thoughts on diagram layout, please check out my master&amp;#8217;s thesis, which is exactly about how to straighten up spaghetti diagrams: &lt;a href="http://www.complexdiagrams.com/" rel="nofollow"&gt;http://www.complexdiagrams.com/&lt;/a&gt;&lt;/p&gt;

	&lt;p&gt;Cheers, Noah&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/a-map-based-approach#content_12376</link>
      <guid>http://www.boxesandarrows.com/view/a-map-based-approach#content_12376</guid>
      <pubDate>Thu, 13 Sep 2007 23:42:41 GMT</pubDate>
      <author>Noah Iliinsky</author>
    </item>
    <item>
      <description>&lt;p&gt;For such an application-oriented audience, I hope an article will be written more concisely than this summary. It sounds like you have good things to say, but as someone with limited time to extract value from a resource, it was hard for me to even locate the point of the proposal, as it didn&amp;#8217;t show up until over halfway through the post.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/idea/view/8845#content_13138</link>
      <guid>http://www.boxesandarrows.com/idea/view/8845#content_13138</guid>
      <pubDate>Tue, 23 Oct 2007 23:02:43 GMT</pubDate>
      <author>Noah Iliinsky</author>
    </item>
    <item>
      <description>&lt;p&gt;Perhaps as another article, I&amp;#8217;d also love a good comparative review of Tinderbox vs other popular outliner tools, Word, OmniOutliner, etc.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/idea/view/12348#content_13510</link>
      <guid>http://www.boxesandarrows.com/idea/view/12348#content_13510</guid>
      <pubDate>Tue, 13 Nov 2007 19:53:52 GMT</pubDate>
      <author>Noah Iliinsky</author>
    </item>
    <item>
      <description>&lt;p&gt;Hi Dan, and everyone.&lt;/p&gt;

	&lt;p&gt;Just chiming in here on the pixels in Visio issue. I&amp;#8217;ve managed to coerce Visio into displaying pixel-equivalent measurements. For times when Visio is unavoidable, here is a simple fix: &lt;br /&gt;&lt;a href="http://complexdiagrams.com/2008/06/01/pixel-rulers-in-visio/" rel="nofollow"&gt;http://complexdiagrams.com/2008/06/01/pixel-rulers-in-vis&amp;hellip;&lt;/a&gt;&lt;/p&gt;

	&lt;p&gt;Cheers, Noah&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/three_visio_tips_special_deliverables_4#content_21757</link>
      <guid>http://www.boxesandarrows.com/view/three_visio_tips_special_deliverables_4#content_21757</guid>
      <pubDate>Mon, 02 Jun 2008 06:10:47 GMT</pubDate>
      <author>Noah Iliinsky</author>
    </item>
    <item>
      <description>&lt;p&gt;Here&amp;#8217;s the simple solution I mentioned above: &lt;br /&gt;&lt;a href="http://complexdiagrams.com/2008/06/01/pixel-rulers-in-visio/" rel="nofollow"&gt;http://complexdiagrams.com/2008/06/01/pixel-rulers-in-vis&amp;hellip;&lt;/a&gt;&lt;/p&gt;

	&lt;p&gt;Cheers, Noah&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/idea/view/13137#content_21758</link>
      <guid>http://www.boxesandarrows.com/idea/view/13137#content_21758</guid>
      <pubDate>Mon, 02 Jun 2008 06:12:17 GMT</pubDate>
      <author>Noah Iliinsky</author>
    </item>
  </channel>
</rss>
