<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/rss2full.xsl" type="text/xsl" media="screen"?><?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/itemcontent.css" type="text/css" media="screen"?><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">

<channel>
	<title>Jameson Watts</title>
	
	<link>http://www.jamesonwatts.com</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Wed, 16 Jul 2008 14:07:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
	<language>en</language>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/JamesonWatts" type="application/rss+xml" /><item>
		<title>Book Review: Managing in a Time of Great Change</title>
		<link>http://www.jamesonwatts.com/2008/07/16/book-review-managing-in-a-time-of-great-change-peter-f-drucker/</link>
		<comments>http://www.jamesonwatts.com/2008/07/16/book-review-managing-in-a-time-of-great-change-peter-f-drucker/#comments</comments>
		<pubDate>Wed, 16 Jul 2008 13:36:04 +0000</pubDate>
		<dc:creator>jameson</dc:creator>
		
		<category><![CDATA[books]]></category>

		<category><![CDATA[business]]></category>

		<category><![CDATA[interactive]]></category>

		<category><![CDATA[drucker]]></category>

		<category><![CDATA[management]]></category>

		<category><![CDATA[managing]]></category>

		<category><![CDATA[peter]]></category>

		<category><![CDATA[vermilion]]></category>

		<guid isPermaLink="false">http://www.jamesonwatts.com/?p=8</guid>
		<description><![CDATA[For those of you that know Peter F. Drucker&#8217;s history, you know he&#8217;s had an opinion or a prediction about nearly every aspect of doing business.  His collection of essays&#8211;compiled meaningfully in Managing in a Time of Great Change&#8211;is no exception.  For myself, I took most heed to his notes on management in [...]]]></description>
			<content:encoded><![CDATA[<p>For those of you that know Peter F. Drucker&#8217;s history, you know he&#8217;s had an opinion or a prediction about nearly every aspect of doing business.  His collection of essays&#8211;compiled meaningfully in <span style="text-decoration: underline;">Managing in a Time of Great Change</span>&#8211;is no exception.  For myself, I took most heed to his notes on management in a knowledge society, his advice about personal brand, and his insight on emergent business structures.</p>
<h3>The Financial Understanding of an Agency</h3>
<p>I manage at an agency where every ounce of business we get is entirely dependent on the individuals doing the work. Creative agencies are the epitomy of the knowledge industry; we have nothing to distribute or stockpile and our entire product is in the transfer of expertise from our employees to our clients.<span id="more-8"></span> In many ways, our product is similar to a financial instrument; it has the same intangibility, measurable history, susceptibility to perception, and risk.</p>
<p>So for each type of &#8220;investor&#8221; you have a different style agency.  Those interested in a stable return on their investment usually seek out agencies that can both predict (in the form of market research) and then measure return.  These activities take additional resources and so your return is diminished by the overhead of the agency.  On the flip side, you have agencies that cater to market speculators.  They exercise great latitude in their interpretation of client need, but engender substantial risk in the process.</p>
<p>So I kinda left Drucker&#8217;s book to start rambling on my own, but I think the point of the previous two paragraphs is that it may take a different type of mind and a different approach to capture the essence of the new knowledge society and that, is something Drucker was quite clear about.</p>
<h3>Networks and the Outhouse</h3>
<p>Drucker spends a good deal of time talking about flat organizations, teamwork and organizational networks.  What he&#8217;s seen is the emergence of knowledge professionals along career paths that have nothing to do with imposed authority and everything to do with one&#8217;s depth of knowledge and talent.  In many ways, we&#8217;ve all become the new trade worker&#8230; in the same way that a doctor or a blacksmith becomes ever more valuable with practice and specialization, so to does the worker in today&#8217;s knowledge economy.  So much so in fact, that it is no longer possible to &#8220;promote&#8221; them to management.  In other words, the skills they&#8217;ve developed are too valuable to waste time having them manage others.  Instead, knowledge workers continue to hone their skills and their career has more to do with the nature and complexity of the problem, then it does an artificial hierarchy.</p>
<p>So then, who are the new managers (and are they even necessary)?  Drucker suggests that like anything else, management is a knowledge skill practiced and honed by those with the talent and desire to learn how to do it; however, this has some interesting implications.  One, is that many new managers will be &#8220;managing&#8221; individuals much older than they are.  I&#8217;ve had to do this and it&#8217;s a tricky proposition in the best of circumstances.  I think we are all still living the transition more than a decade after these concepts first entered the collective business consciousness.</p>
<p>Another implication of this flattening is the emergence of small networked clusters of in-kind business.  In my industry (loosely interpreted) we&#8217;ve got copywriting, graphic design, media buying, internet marketing, programming, public relations, etc&#8230; and the history has been to consolidate much of this under one roof.  Even now I&#8217;m witnessing one of my main competitors (<a href="http://xylemcci.com/">Xylem CCI</a>) attempt to create an in-house SEO department&#8230; this, right after a large merger.  <a href="http://texturemedia.com" target="_blank">Texture Media</a> tried something similar and&#8211;to the best of my knowledge&#8211;had quite a bit of trouble getting anything to work.  In my opinion it is risky to diversify one&#8217;s offering so thoroughly with the understanding that you&#8217;ll never be as good as the new breed of specialist&#8230; <a href="http://thebooyahagency.com">The Booyah Agency</a> is one of the nation&#8217;s best SEO firms; they&#8217;ve got the best local talent and can help my clients achieve returns on marketing dollars faster than we ever could&#8230; which, ultimately means more business for our core competencies in design and interactive.</p>
<p>So I think managing in the knowledge economy means three things: disciplined focus on core competency, the development of resource networks outside one&#8217;s core competencies and the recruitment and retention of knowledge workers.  It is this last, which I believe to be the hardest of all.</p>
<h3>My employees are your employees</h3>
<p>Employees no longer spend an entire career at one company&#8230; and in the interactive world, turnover seems to be even more prevalent.  Retention can come at a significant financial cost&#8211;I&#8217;ve seen companies like <a href="http://wallst.com">Walls Street on Demand</a> slap on the golden handcuffs pretty successfully&#8211;but I don&#8217;t think this is sustainable in the slightly less fortified interactive / advertising industry.  Drucker suggests that managers of the knowledge worker will need to focus on &#8220;meaning&#8221; in addition to compensation.  Now, meaning can stand for different things at different companies, but the underlying theme (in my interpretation) is that life, work and purpose are becoming ever more intertwined as we all become more digitally connected; my computer travels with me, my online social and business networks are the same, my code is both open source and making money&#8230;  I&#8217;m not sure what meaning is for every company and indeed it may vary by employee; however, I suspect that this concern will be one of the defining characteristics of the new manager.</p>
<h3>Jameson is more memorable than Jamie</h3>
<p>Drucker touched briefly on the idea of personal brand, but enough that it stood out to me as an important factor for success in the new economy.  One of the problems we knowledge workers have, is the variety of jobs currently, or likely to show up on our resume.  This dispersion of focus makes it difficult for potential employers to evaluate one&#8217;s ability to succeed at a new post.  What Drucker suggests (and I agree strongly with), is that the responsibilty has shifted to the individual to shepard the cohesion of one&#8217;s past.  In other words, everyone needs to become a marketer.</p>
<p>To do this, we need a personal value proposition (or more likely a set of arguments stored in our head) such that the jump from Medical IT Manager to Creative agency Interactive Director is not just accepted, but seen as a logical and natural transition.  I think the perception may be changing naturally as hiring managers see ever more colorful applications, however, it is my belief that those who actively focus on their personal brand will excel faster than those who don&#8217;t.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jamesonwatts.com/2008/07/16/book-review-managing-in-a-time-of-great-change-peter-f-drucker/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Leftovers: Eighty / Twenty and the problem with contractors</title>
		<link>http://www.jamesonwatts.com/2008/03/15/leftovers-eighty-twenty-and-the-problem-with-contractors/</link>
		<comments>http://www.jamesonwatts.com/2008/03/15/leftovers-eighty-twenty-and-the-problem-with-contractors/#comments</comments>
		<pubDate>Sat, 15 Mar 2008 17:18:23 +0000</pubDate>
		<dc:creator>jameson</dc:creator>
		
		<category><![CDATA[business]]></category>

		<category><![CDATA[interactive]]></category>

		<category><![CDATA[accountability]]></category>

		<category><![CDATA[contracting]]></category>

		<category><![CDATA[contractors]]></category>

		<category><![CDATA[development]]></category>

		<category><![CDATA[proposals]]></category>

		<guid isPermaLink="false">http://www.jamesonwatts.com/2008/03/15/leftovers-eighty-twenty-and-the-problem-with-contractors/</guid>
		<description><![CDATA[Several great programmers I know have recently made the switch from full-time employee to full-time contractor&#8230; and I understand why.  Clients and corporate structure can be a real drag.  You have to deal with politics and personalities all while trying to actually get some work done.  What I don&#8217;t know is whether [...]]]></description>
			<content:encoded><![CDATA[<p>Several great programmers I know have recently made the switch from full-time employee to full-time contractor&#8230; and I understand why.  Clients and corporate structure can be a real drag.  You have to deal with politics and personalities all while trying to actually get some work done.  What I don&#8217;t know is whether this is going to be an industry-wide trend or a phase in what is now a very favorable economic cycle for interactive developers<span id="more-7"></span>.  Needless to say, I can understand (and have experienced) the appeal of hourly work and the freedom to be choosy about one&#8217;s projects, but it may not be good for the industry over the long term. This shift has forced the business model towards an agency of interactive project managers who contract out work to a sea of growing independents; however, scope changes, waning accountability, and the fragility of an ongoing support relationship can all disrupt the success of your project.</p>
<h3>The proposal problem</h3>
<p>Proposals aren&#8217;t meant to assume the responsibility of a complete requirements specification, but they are meant to illustrate a broad definition of scope.  They often list deliverables, dates and process; however, if you&#8217;re planning to use a contractor for the development portion of your interactive project then most proposals aren&#8217;t specific enough.  Contractors often need to schedule chunks of their own time and put together a proposal of their own (based on yours).  This all needs to be done while courting the client to ensure resources are in place if the project is a go.  Unfortunately, if you write your proposals with hard deadlines and strict penalties, no one will bite, and if you write a complete functional specification, your potential client might just shop it around to other firms; your competition will always have a lower bid because they didn&#8217;t need to spend hours fine-tuning a proposal and researching the time required to complete a given task.</p>
<p>The other option is to pull from a pool of developers that charge by the hour and pass that rate through with a margin.  In my opinion, this is never fair to the client even if you manage to land one who&#8217;s extremely rich, used to slow government contracts and enjoys spending vast sums of cash on prolonged phone calls and meetings with three team members ($150/hr * 3 attendees  * 2hr meeting = $$$).  In addition, most clients have very little understanding of a project&#8217;s scope or the consequences of making seemingly small changes in the middle of development.  This always leads to a frustrating client relationship and can compromise a potential referral.</p>
<h3>The accountability problem</h3>
<p>Most contract software developers have shunned the corporate world for a reason&#8230; the amount of non-development energy required to finish a project and make a client happy can be equivalent to the time spent writing code (if one accounts for the time costs of communication, research, training and deployment).  It is much simpler to carve out the programming portion and leave the rest to an agency; however, this disengagement will inevitably lead to ambiguities of responsibility, and a higher risk of failure.</p>
<p>Finger pointing (responsibility) can generally be avoided by robust contracts, but this really just takes us back to the proposal problem.   The process can also work if you happen to use contractors serious about their long-term reputation.  In other words, contractors who treat the agency with the same level of customer service with which the agency treats the client.  I&#8217;ve seen this work&#8211;it&#8217;s the epitome of capitalism&#8211;but it doesn&#8217;t take long for these developers to understand their real value and raise rates accordingly, thus making it ever more difficult to justify their use on &#8220;every day&#8221; projects.</p>
<p>When working with a development contractor, there is always the risk they will fire you&#8230; if the project starts getting difficult, relationships go sour, the time-line changes (when doesn&#8217;t it?) or they take a full time position with another company.  For all these reasons and more, a project&#8217;s risk profile expands as outsourced development is integrated into the process.  I&#8217;ve seen this successfully managed by extremely talented project managers.  Unfortunately, they also tend to realize their true value after a period of success.</p>
<h3>The training and support problem</h3>
<p>Another consideration is the time it takes for internal development staff to fully understand the code written by a contractor.  This can be necessary  in order to provide ongoing support at the conclusion of a contract; however, there is little consideration for the additional hours this process takes, not to mention the sour attitude any internal programmer will develop when tasked with leafing through someone else&#8217;s code.</p>
<p>One solution is to write perfect software such that your client has nothing to complain about.  Believe it or not, I&#8217;ve had reasonably good luck with this mostly as a result of working with rock star developers.  But, in all likelihood this is the exception not the rule.</p>
<p>Another alternative is to hire a full service development agency (more middle men), and rely on them to handle ongoing support.  This can work if your goal is to completely isolate the creative from any of the software development, but I tend to dislike any arrangement that releases ultimate responsibility for client relationships.  In addition, these agencies are always at least as expensive as you are, and thus rarely a money-making proposition.</p>
<h3>What now?</h3>
<p>We&#8217;re probably heading for a recession, but it may be that as companies cut budgets from traditional advertising, alternative means of accessing their customer base become more attractive&#8230; thus the case for continued growth in Interactive business.  It&#8217;s usually better to run your agency a little lean, but with the growing demand for interactive work it may be time to stick you neck out there and start to hire.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jamesonwatts.com/2008/03/15/leftovers-eighty-twenty-and-the-problem-with-contractors/feed/</wfw:commentRss>
		</item>
		<item>
		<title>The Seed Conference 2008</title>
		<link>http://www.jamesonwatts.com/2008/02/10/the-seed-conference-2008/</link>
		<comments>http://www.jamesonwatts.com/2008/02/10/the-seed-conference-2008/#comments</comments>
		<pubDate>Mon, 11 Feb 2008 04:42:05 +0000</pubDate>
		<dc:creator>jameson</dc:creator>
		
		<category><![CDATA[business]]></category>

		<category><![CDATA[interactive]]></category>

		<category><![CDATA[rails]]></category>

		<guid isPermaLink="false">http://www.jamesonwatts.com/2008/02/10/the-seed-conference-2008/</guid>
		<description><![CDATA[The Seed Conference was on the beautiful  IIT campus on the south side of Chicago in a relatively new building designed by  Rem Koolhaas (a student of Mies van der Rohe), but I&#8217;ll get into that in a  bit&#8230;
Main topics &#8212; Stop meeting. Stay small. Say no.
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;
The first presenter was Carlos Segura. [...]]]></description>
			<content:encoded><![CDATA[<p>The <a title="blocked::http://www.seedconference.com/" href="http://www.seedconference.com/">Seed Conference</a> was on the beautiful  IIT campus on the south side of Chicago in a relatively new building designed by  Rem Koolhaas (a student of Mies van der Rohe), but I&#8217;ll get into that in a  bit&#8230;</p>
<p><strong>Main topics</strong> &#8212; Stop meeting. Stay small. Say no.<span id="more-4"></span></p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p>The first presenter was <a title="blocked::http://www.segura-inc.com/index.php" href="http://www.segura-inc.com/index.php"><strong title="blocked::http://www.segura-inc.com/index.php">Carlos Segura</strong>.</a> He&#8217;s  apparently a huge name in print; maybe some of you design-minded individuals  know him better than I. Some questions he did a really good job of  answering: How do you manage design(ers)? How do you manage a client? What is  brand? How do you market yourself?</p>
<p>Best Quote: &#8220;We lose more clients than we get&#8221;</p>
<p>2nd Best Quote: &#8220;If a client says &#8216;money is not an object&#8217;, quote them one  million dollars&#8230; they&#8217;ll give you a budget&#8221;</p>
<p><strong>How do you manage design(ers)?</strong></p>
<p>I thought his process was simple, but appropriate. First, he&#8217;s (almost) never met a  client in person, thinks meetings are generally a waste of time and is much more  likely to turn down a project then to take it. Part of the reason his team can  do this is because they remain small and focused&#8211;they needn&#8217;t take on work  &#8220;just to feed the beast&#8221; &#8211;so to say. He also claimed that creativity exists at  the fringe, and thus&#8230; designers will do their best work when they have too  much to do combined with inspiring projects. On a practical note, when a new  project first comes in, Carlos has many designers go off and work on their own. After a period, they gather again and he helps determine which ideas the client  will see.</p>
<p><strong>How do you manage a client?</strong></p>
<p>From what I gathered, it was the combination of three vital practices that  cumulated in a successful client relationship. First, record everything (notes)  that a client says they want and then briefly remind them of it shortly before  presenting. Second, only show what you&#8217;d eventually be happy with as a designer  and third, get the budget up front. Carlos also said several times that it is  imperative to communicate a clear definition of target audience (i.e. &#8220;the  design is for your customer not for you&#8230;&#8221;). Thus, there must be a sense of  trust that we (the expert) can&#8211;and will&#8211;do a better job of understanding the  ultimate consumer of the creative product. In addition to these guiding  principles, Carlos said he always fought for his ideas and in many cases fired  clients that wanted too much control over the design. His justification was  that the Segura brand was evident in every piece of work he did&#8230; in other  words, don&#8217;t compromise your design integrity if you are trying to build a  long-term reputation.</p>
<p><strong>What is brand?</strong></p>
<p>It can be difficult to explain what branding means, and quoting something  aloof like &#8220;brand is the visual representation of the benefits your  product/company provide,&#8221; may well be lost on your client. Carlos instead uses  the example of several car companies: What is BMW? &#8212; excellence in  engineering. What is Volvo? &#8212; safety. What is Cadillac? &#8212; American luxury. What is Ford? &#8212; ???  Ford is trying to be all things to all people.</p>
<p><span class="Apple-style-span" style="font-weight: bold">How do you market  yourself?</span></p>
<p>I asked Carlos to what extent his personal brand was a conscious effort and  how much was a byproduct of his work. He said that his personal brand&#8211;and by  extension, that of his company&#8211;were a conscious effort every minute of every  day. This response surprised me somewhat as I guessed it would have been some  combination, but it goes to show how much of himself has been dedicated to the  craft that no distinguishable line can be drawn between the man and his work. Finally, when you&#8217;re pounding the pavement Carlos claims that great and unique  marketing/presentation material will always win the deal.</p>
<p><strong>He did case studies on:</strong></p>
<p>Re-branding Corbis<br />
Rock Shox<br />
Labels for Express Jeans</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p>The second presenter was <strong>Jason Fried</strong> founder of 37signals. He and  his business partner David Heinemeier Hansson (creator of the Rails application  development framework) have created some of the most influential web apps that  exists&#8230; think Basecamp. He did a wonderful job framing his business  philosophy, which can be summed up with a few basic concepts: planning hurts  your business, size matters, open works, and interruption kills  productivity.</p>
<p>Best Quote: &#8220;I&#8217;d rather have a client grow out of our products then make  them so feature laden that we raise the barrier to entry for new  customers.&#8221;</p>
<p>2nd Best Quote: &#8220;There&#8217;s no such thing as a one hour meeting. If it&#8217;s a  ten person meeting that takes an hour, it&#8217;s a ten hour meeting.&#8221;</p>
<p><strong>Planning hurts your business</strong></p>
<p>A lot of businesses spend time and meetings trying to figure out where they  want to be one, five and even ten years from the present. Jason&#8217;s argument is  simply that by planning for an uncertain future, one is donning a set of  blinders. In other words, the plan itself can limit your ability to grasp  opportunity at the fringe. Jason expanded on this topic by making the  suggestion that rather than focus on large decisions that require company-wide  consensus and considerable commitment of resources, focus instead on small  decisions that can be made frequently. This allows the company to fail and fail  often without compromising it&#8217;s overall health. The idea is that these small  failures provide a sustainable platform for learning from one&#8217;s mistakes by  minimizing the risk associated with each decision. It also empowers employees  to take personal responsibility since the risk of failure doesn&#8217;t endanger their  employment status.</p>
<p><strong>Size matters</strong></p>
<p>Staying small was a theme that permeated each presenter&#8217;s talk. Like  Carlos, Jason consciously keeps his team small in order to prevent the need to  take on work just to pay salaries, but also because he thinks it leads to better  products. He argued that businesses will most often scale up their workforce to  match the perceived scope of a project. He instead suggests you scale the  project scope to your companies head count. This forces the team to focus on  only those features which really make an impact for the end user. All 37signals  products adhere to this philosophy (they are a company of ~10).</p>
<p><strong>Open works</strong></p>
<p>Rails&#8211;the platform upon which Bascamp is built&#8211;is completely open  sourced, all of 37signals&#8217;s business processes are transparent to the public,  and the company regularly publishes successes, failures and ideas to its blog  (<a title="blocked::http://www.37signals.com/svn/" href="http://www.37signals.com/svn/">Signals vs. Noise</a>). The idea is that  &#8220;open&#8221; works and the analogy given was that of the Cookbook. Every well known  and successful chef gives away their secrets in the form of recipes. This  giving-away of intellectual capital actually enhances an organization&#8217;s ability  to garner success (contrary to what many in the industry think). I believe this  to be an extension of the popular theory that work in the interactive space is  no longer about the idea, but rather the execution of that idea (could this trend may  be a result of the rising knowledge-based economy predicted by Drucker in the  90&#8217;s?)</p>
<p><strong>Interruption kills productivity</strong></p>
<p>If you accept the fact that it takes a certain amount of time to focus and  un-focus (think about writing an elaborate email, starting a new design or  writing code), then it follows that the more times you are required to break  concentration, the less productive you become. Think then about how many times  during the day someone comes and interrupts your train of thought? As an  exercise, Jason suggested we mark on a piece of paper the number of times this  happens in a typical work day, then calculate the approximate time sacrificed. As an alternative, he suggests email or if it&#8217;s urgent, IM since it at least  provides the 15-30 seconds required to finish a thought before responding. Implicit in this method is a social contract that relies on responses within a  reasonable timeframe. Jason terms the two types of interruption, active and  passive, with passive being the preferred method.</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p>The third presenter was Jim Coudal who&#8211;along with a small team&#8211;manages <a title="blocked::http://www.coudal.com/" href="http://www.coudal.com/">coudal.com</a> and a few other successful  businesses. He runs his shop much like the first two presenters but had a few  good insights regarding client work, short attention spans, and truth.</p>
<p>Quote: &#8220;Hire us because of the way we think not because of what we&#8217;ve  done&#8221;</p>
<p><strong>Client work</strong></p>
<p>As an agency one of the least talked about competencies is the ability to  very quickly understand a client&#8217;s target market. His point for bringing this  up was to make the case for engaging in entrepreneurial activities in  conjunction with client work. In other words, if you have developed the craft  on behalf of a client (to understand and analyze a market), why not use this for  your organization&#8217;s own benefit; create something and sell it.</p>
<p><strong>Short attention spans</strong></p>
<p>As illustrated by the short film hosted <a title="blocked::http://www.coudal.com/regrets.php" href="http://www.coudal.com/regrets.php">here</a>, many of us have  an entrepreneurial spirit paired with a short attention span. The film casts  this behavior in a bad light, but Jim took the opposite view and instead  suggested that we embrace our short attention spans as a source of energy and  enlightenment. If you&#8217;ve ever been part of a team coalescing around the latest  &#8220;great&#8221; idea, then you know the kind of energy and excitement of which Jim  speaks; however, the vast majority of these adventures fail either because of  lost interest or because the market proves it&#8217;s a bad idea. Jim challenges that  this cycle of energy and failure is actually a very positive part of his  business because it keeps people energized and because you generally learn a lot  in the process of failing (credit to the previous speaker).</p>
<p><strong>Truth</strong></p>
<p>During the Q&amp;A session one member of the audience mentioned that while  coudal.com was really cool, it didn&#8217;t feel elitist, patronizing or otherwise  unapproachable&#8211;I think the phrase he used was, &#8220;too cool for school.&#8221; When  asked about this balance, Jim simply stated that which appeared obvious (after a  brief visual scrutiny) &#8230;&#8221;I&#8217;m not cool.&#8221; In three words Jim was expressing his  view that customers in the digital age can sense authenticity, even through  something as superficial as a web page.</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p><strong>Some thoughts of my own&#8230;</strong></p>
<p>During the lunch break an architecture expert&#8211;and fellow at the Harvard  school of design&#8211;came and gave a presentation on the building we were in  (designed by Rem Koolhaas) and the rest of the campus (designed by Mies van der  Rohe). Much of the talk was focused on <a title="blocked::http://mies.iit.edu/" href="http://mies.iit.edu/">Crown Hall</a> and how it becomes even more grand  because of its transparency and bold openness. This didn&#8217;t appear to be a  conscious reflection on the speakers personal business philosophies, but it did  act&#8211;even if just below the surface&#8211;as a unifying theme of the conference. In  an age where Google knows us better than we know ourselves, I think our clients  and certainly our client&#8217;s clients are demanding a brutal version of the truth  in everything they consume. Honesty and doing business in public&#8211;especially  with regard to our failures&#8211;is the new credential. Think about our new  politicians; in the past, Obama&#8217;s admission of organizational shortcomings might  have emboldened skeptics and critics, but instead we saw attacks on his  opponent&#8217;s veneer of modesty. I believe we may be witnessing the natural, but  unexpected consequence of the information age&#8230; simply, that we can&#8217;t hide  anymore. And those who take the first steps to embrace this fact in business,  or elsewhere will be rewarded by a population willing to supply capital for  something with which they feel a personal connection.</p>
<p>This concept of doing business &#8220;in the open&#8221; leads me to conclude what I  think many in business already know, that the product is no longer separate from  the company and the company is no longer separate from it&#8217;s employees. Consumers have started to demand that an organization embody the ideals of its  product, but I think the next step is to demand that management also be held  accountable for that very same ideal. As mentioned previously, I asked Carlos  about managing his personal brand, but I think the conclusion is the same for  all of the presenters. Product is the company is the person.</p>
<p><a title="Direct link to file" onclick="return false;" href="http://www.jamesonwatts.com/wp-content/uploads/2008/02/seed.png"><img src="http://www.jamesonwatts.com/wp-content/uploads/2008/02/seed.png" alt="Seed Conference 2008 Panel" /></a></p>
<p>From left to right: Carlos Segura, Jason Fried, Jim  Coudal</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jamesonwatts.com/2008/02/10/the-seed-conference-2008/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Hello world!</title>
		<link>http://www.jamesonwatts.com/2008/02/10/hello-world/</link>
		<comments>http://www.jamesonwatts.com/2008/02/10/hello-world/#comments</comments>
		<pubDate>Mon, 11 Feb 2008 03:21:53 +0000</pubDate>
		<dc:creator>jameson</dc:creator>
		
		<category><![CDATA[interactive]]></category>

		<category><![CDATA[conference]]></category>

		<category><![CDATA[hello]]></category>

		<category><![CDATA[seed]]></category>

		<category><![CDATA[vermilion]]></category>

		<category><![CDATA[world]]></category>

		<guid isPermaLink="false">http://www.jamesonwatts.com/?p=1</guid>
		<description><![CDATA[I thought for too long about whether to keep the default Wordpress title for my first post.  I then spent too long trying to think about how many &#8220;Hello world!&#8221; applications I&#8217;ve written over the years.  As a matter of introduction, I&#8217;ve been writing software (mostly in the interactive world) for over a [...]]]></description>
			<content:encoded><![CDATA[<p>I thought for too long about whether to keep the default Wordpress title for my first post.  I then spent too long trying to think about how many &#8220;Hello world!&#8221; applications I&#8217;ve written over the years.  As a matter of introduction, I&#8217;ve been writing software (mostly in the interactive world) for over a decade using the web language du jour (I&#8217;m now high on Rails), but I&#8217;ve remained somewhat silent even while intently observing my piers blog away.  I was trained to write code in college then learned how after college, then got an MBA and now I&#8217;m running the technology circus at <a href="http://www.vermilion.com" title="Vermilion" target="_blank">Vermilion</a>.  Anyway, I attended the <a href="http://seedconference.com/" title="SEED">Seed</a> conference in Chicago recently and there was much talk about doing business in public so it kind of inspired me to start organizing my projects in a more open way.  Stay tuned for a post on that conference.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jamesonwatts.com/2008/02/10/hello-world/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
