<?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 Peter Gremett</title>
    <link>http://www.boxesandarrows.com/person/688</link>
    <pubDate>Fri, 26 Jan 2007 14:52:40 GMT</pubDate>
    <description>Comments by Peter Gremett</description>
    <item>
      <description>&lt;p&gt;I am proposing an article that describes some of the pitfalls when companies choose to use outside resources to create innovation for a product. Particularly as it relates to an in house design team. The material would come from direct experience and observation working as principal designer / ui lead and seeing some great opportunities being hired out and left to deal with the fallout.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/idea/view/2775#content_2790</link>
      <guid>http://www.boxesandarrows.com/idea/view/2775#content_2790</guid>
      <pubDate>Fri, 26 Jan 2007 14:52:40 GMT</pubDate>
      <author>Peter Gremett</author>
    </item>
    <item>
      <description>&lt;p&gt;Another point I had not thought of until recently is off-shoring UI design. This will certainly be something to watch as off-shoring becomes more and more prevalent.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/idea/view/2775#content_2828</link>
      <guid>http://www.boxesandarrows.com/idea/view/2775#content_2828</guid>
      <pubDate>Fri, 26 Jan 2007 14:52:42 GMT</pubDate>
      <author>Peter Gremett</author>
    </item>
    <item>
      <description>&lt;p&gt;Its great to get the message out that you don&amp;#8217;t have to be a manager to progress and grow in your career. So many people think that you have to be a manager to get paid more, recognized by an organization, etc.&lt;/p&gt;

	&lt;p&gt;Another point people should also know is that the path of a manager or an ic (individual contributor) for that matter, is not fixed. At different points in your career there is nothing stopping you from moving back and forth between the roles. This is especailly true for the dynamic places that we work in today.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/so-you-think-you#content_4730</link>
      <guid>http://www.boxesandarrows.com/view/so-you-think-you#content_4730</guid>
      <pubDate>Tue, 13 Feb 2007 16:22:12 GMT</pubDate>
      <author>Peter Gremett</author>
    </item>
    <item>
      <description>&lt;p&gt;i came across this, i know its quite old but am interested in progress you have made. i have been working with these for internal strategy / vision. i would like to talk to you more.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/idea/view/4101#content_5553</link>
      <guid>http://www.boxesandarrows.com/idea/view/4101#content_5553</guid>
      <pubDate>Fri, 23 Mar 2007 22:35:23 GMT</pubDate>
      <author>Peter Gremett</author>
    </item>
    <item>
      <description>&lt;p&gt;Terry covered most of the points and I agree with what he is saying. I do want to comment on @Jason #8.  The nature of the wiki is that you can create as many pages and sub pages as you like. You don&amp;#8217;t have to start off with the perfect organization, in fact this is a bit counter to what a wiki spec is about. They are flexible and should grow and change as the project does. This benefit is really leveraged when you are working with the agile process. The fluidity that is required for this type of project is a good match for the fluidity that you can have with the wiki.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/using-wikis-to#content_39714</link>
      <guid>http://www.boxesandarrows.com/view/using-wikis-to#content_39714</guid>
      <pubDate>Tue, 11 Aug 2009 23:48:56 GMT</pubDate>
      <author>Peter Gremett</author>
    </item>
  </channel>
</rss>

