<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>Comments on: looking back</title>
	<atom:link href="http://gluue.com/2007/08/looking-back/feed/" rel="self" type="application/rss+xml" />
	<link>http://gluue.com/2007/08/looking-back/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Tue, 17 Mar 2026 18:34:31 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=3.8.41</generator>
	<item>
		<title>By: Greg Paulhus</title>
		<link>http://gluue.com/2007/08/looking-back/comment-page-1/#comment-4</link>
		<dc:creator><![CDATA[Greg Paulhus]]></dc:creator>
		<pubDate>Fri, 10 Aug 2007 16:46:02 +0000</pubDate>
		<guid isPermaLink="false">http://pasteinteractive.com/2007/08/looking-back/#comment-4</guid>
		<description><![CDATA[-----
Everything you do should evolve into the real thing. If a document stops before it turns real, it’s dead.
-----

Just my two cents. A planning document&#039;s focus should be to communicate well with the client and project team, but especially the client. You&#039;ve got to create planning documents that the client can understand, so they can look at the document and &#039;get it&#039;. Then they can approve it, because they get it, and you don&#039;t get sucked into an iterative nightmare and infinite revisions.

A live wireframe is a fine idea, but if your client can&#039;t understand it easily, there&#039;s no point.]]></description>
		<content:encoded><![CDATA[<p>&#8212;&#8212;-<br />
Everything you do should evolve into the real thing. If a document stops before it turns real, it’s dead.<br />
&#8212;&#8212;-</p>
<p>Just my two cents. A planning document&#8217;s focus should be to communicate well with the client and project team, but especially the client. You&#8217;ve got to create planning documents that the client can understand, so they can look at the document and &#8216;get it&#8217;. Then they can approve it, because they get it, and you don&#8217;t get sucked into an iterative nightmare and infinite revisions.</p>
<p>A live wireframe is a fine idea, but if your client can&#8217;t understand it easily, there&#8217;s no point.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced
Object Caching 161/164 objects using disk

 Served from: gluue.com @ 2026-04-22 19:20:14 by W3 Total Cache -->