<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Thinking and Making: Comments by Austin Govella</title>
    <link>http://www.thinkingandmaking.com/person/4840</link>
    <pubDate>Sat, 05 Apr 2008 23:10:39 GMT</pubDate>
    <description>Comments by Austin Govella</description>
    <item>
      <description>&lt;p&gt;Shawn,&lt;/p&gt;

	&lt;p&gt;I&amp;#8217;m totally with you here. In fact, the next post explains behavior-based metrics a bit more, and I think they have two key qualities:&lt;/p&gt;

	&lt;p&gt;1. They measure the desired user behavior.&lt;br /&gt;2. It&amp;#8217;s comparative, so you have the kind of ratio you&amp;#8217;re talking about.&lt;/p&gt;</description>
      <link>http://www.thinkingandmaking.com/view/unique-visitors-is-a#content_18108</link>
      <guid>http://www.thinkingandmaking.com/view/unique-visitors-is-a#content_18108</guid>
      <pubDate>Sat, 05 Apr 2008 23:10:39 GMT</pubDate>
      <author>Austin Govella</author>
    </item>
    <item>
      <description>&lt;p&gt;Paul,&lt;/p&gt;

	&lt;p&gt;That&amp;#8217;s refreshing to hear. And I think you&amp;#8217;re right about it being the obvious. I&amp;#8217;m still not sure why the metrics people use are so skewed some places.&lt;/p&gt;

	&lt;p&gt;I think I&amp;#8217;ll be doing a side thing at the Summit on the &amp;#8216;UX health check&amp;#8217;. It&amp;#8217;s a qualitative way to derive a longitudinal, quantitative measurement of your product&amp;#8217;s experience. That&amp;#8217;s lots of big words, but it makes total sense when you see it.&lt;/p&gt;

	&lt;p&gt;Catch me at the Summit, and I&amp;#8217;ll fill you in. I&amp;#8217;m interested in getting people&amp;#8217;s responses.&lt;/p&gt;</description>
      <link>http://www.thinkingandmaking.com/view/unique-visitors-is-a#content_18216</link>
      <guid>http://www.thinkingandmaking.com/view/unique-visitors-is-a#content_18216</guid>
      <pubDate>Tue, 08 Apr 2008 05:36:52 GMT</pubDate>
      <author>Austin Govella</author>
    </item>
    <item>
      <description>&lt;p&gt;Hey Jon!&lt;/p&gt;

	&lt;p&gt;I found this great article from Jeff Patton on what he calls the &amp;#8220;slow software movement&amp;#8217;:
* &lt;a href="http://agileproductdesign.com/blog/slow_software.html" rel="nofollow"&gt;http://agileproductdesign.com/blog/slow_software.html&lt;/a&gt;&lt;/p&gt;

	&lt;p&gt;I think your focus on feature scope vs. code quality is really interesting. I prefer to prioritize experience or product quality. I&amp;#8217;m more interested in the gestalt of the engineering + the features + the experience.&lt;/p&gt;

	&lt;p&gt;I feel like a lot of time, the project focuses on engineering or features, which makes sense, since they&amp;#8217;re more concrete.&lt;/p&gt;

	&lt;p&gt;Frankly, the backlog is a ghetto. Things go in and rarely make it back out. There&amp;#8217;s a lot of political pressure and shifting priorities that cause this to happen, so it&amp;#8217;s not the backlogs fault, but that definitely means the backlog, by itself, isn&amp;#8217;t a good answer.&lt;/p&gt;

	&lt;p&gt;We used to have the &amp;#8220;IA bucket&amp;#8221;. That seemed to work well. Maybe re-instituting the bucket would be a good thing? We used to use it for bug fixes, features, and design scrubs: all the &amp;#8220;experience&amp;#8221; things. And maybe there should also be an &amp;#8220;engineering bucket&amp;#8221;?&lt;/p&gt;

	&lt;p&gt;Definitely, we should write a ticket as soon as the gap appears. That&amp;#8217;s an awesome idea.&lt;/p&gt;</description>
      <link>http://www.thinkingandmaking.com/view/agile-ux-idealized#content_18625</link>
      <guid>http://www.thinkingandmaking.com/view/agile-ux-idealized#content_18625</guid>
      <pubDate>Tue, 15 Apr 2008 17:01:53 GMT</pubDate>
      <author>Austin Govella</author>
    </item>
    <item>
      <description>&lt;p&gt;One of my goals has always been to increase the team&amp;#8217;s design literacy. That&amp;#8217;s just good practice in any organization with any process. Design literacy enables faster, better, more advanced collaboration, and that&amp;#8217;s exactly what an agile process needs.&lt;/p&gt;

	&lt;p&gt;We&amp;#8217;ve divided user tasks on the site into four major groups, and we have a set of &amp;#8216;generic&amp;#8217; requirements for each. (More like best practices for that kind of task.)&lt;/p&gt;

	&lt;p&gt;I&amp;#8217;ve been struggling with the best way to communicate these requirements to both engineering and design. Any suggestions?&lt;/p&gt;</description>
      <link>http://www.thinkingandmaking.com/view/agile-user#content_18626</link>
      <guid>http://www.thinkingandmaking.com/view/agile-user#content_18626</guid>
      <pubDate>Tue, 15 Apr 2008 17:11:52 GMT</pubDate>
      <author>Austin Govella</author>
    </item>
    <item>
      <description>&lt;p&gt;Dude. Awesome insight. I think that begs the question: when we communicate in person, how much does our audience *really* affect what we say.&lt;/p&gt;

	&lt;p&gt;We assume it affects a lot, but maybe it doesn&amp;#8217;t?&lt;/p&gt;</description>
      <link>http://www.thinkingandmaking.com/view/some-thoughts-about#content_18698</link>
      <guid>http://www.thinkingandmaking.com/view/some-thoughts-about#content_18698</guid>
      <pubDate>Wed, 16 Apr 2008 18:43:52 GMT</pubDate>
      <author>Austin Govella</author>
    </item>
    <item>
      <description>&lt;p&gt;Tanya, I didn&amp;#8217;t even know the Second Life island was going to be active.&lt;/p&gt;

	&lt;p&gt;I think part of Twitter&amp;#8217;s brilliance is how it easy it is to use it to create a virtual world around any other event.&lt;/p&gt;</description>
      <link>http://www.thinkingandmaking.com/view/some-thoughts-about#content_19033</link>
      <guid>http://www.thinkingandmaking.com/view/some-thoughts-about#content_19033</guid>
      <pubDate>Wed, 23 Apr 2008 14:38:41 GMT</pubDate>
      <author>Austin Govella</author>
    </item>
    <item>
      <description>&lt;p&gt;&amp;#8221;... my perception of social intimacy is entirely relative. I may feel (and truly believe) I am close to you and you may feel (and truly believe) that we are not close at all&#8212;Twitter seems to allow us both to live that reality.&amp;#8221;&lt;/p&gt;

	&lt;p&gt;Wow. That&amp;#8217;s totally true. And although tat occurs occasionally in real life, I think Twitter exacerbates that disconnect because it lacks a lot of the physical social contexts that we have in the physical world.&lt;/p&gt;</description>
      <link>http://www.thinkingandmaking.com/view/some-thoughts-about#content_20892</link>
      <guid>http://www.thinkingandmaking.com/view/some-thoughts-about#content_20892</guid>
      <pubDate>Sun, 18 May 2008 15:27:44 GMT</pubDate>
      <author>Austin Govella</author>
    </item>
    <item>
      <description>&lt;p&gt;Brian,&lt;/p&gt;

	&lt;p&gt;I totally agree on our primary goal as UX practitioners. If I seemed casual, that&amp;#8217;s only because I don&amp;#8217;t think the UX is the most important part of working on a team. I think the most important part is working well together.&lt;/p&gt;

	&lt;p&gt;Every one on the team makes compromises. Working well means everyone understands the best compromises to make. That&amp;#8217;s why the team&amp;#8217;s design literacy is so important.&lt;/p&gt;</description>
      <link>http://www.thinkingandmaking.com/view/agile-ux-six#content_21722</link>
      <guid>http://www.thinkingandmaking.com/view/agile-ux-six#content_21722</guid>
      <pubDate>Sun, 01 Jun 2008 01:51:19 GMT</pubDate>
      <author>Austin Govella</author>
    </item>
    <item>
      <description>&lt;p&gt;Thanks! I appreciate the kind words.&lt;/p&gt;

	&lt;p&gt;I actually came across your blog recently. Wish you wrote more.&lt;/p&gt;</description>
      <link>http://www.thinkingandmaking.com/view/a-new-design#content_22939</link>
      <guid>http://www.thinkingandmaking.com/view/a-new-design#content_22939</guid>
      <pubDate>Mon, 16 Jun 2008 20:26:36 GMT</pubDate>
      <author>Austin Govella</author>
    </item>
    <item>
      <description>&lt;p&gt;One thing I liked about when we did the exercise for our team is the way we couldn&amp;#8217;t necessarily agree on an &amp;#8220;Only&amp;#8221;. That can be a useful insight, too.&lt;/p&gt;</description>
      <link>http://www.thinkingandmaking.com/view/a-sample-only#content_22940</link>
      <guid>http://www.thinkingandmaking.com/view/a-sample-only#content_22940</guid>
      <pubDate>Mon, 16 Jun 2008 20:27:49 GMT</pubDate>
      <author>Austin Govella</author>
    </item>
  </channel>
</rss>
