<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Blog &#187; Alex Johnson</title>
	<atom:link href="http://blog.protoshare.com/author/alex/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.protoshare.com</link>
	<description>Wireframing Tool - ProtoShare</description>
	<lastBuildDate>Wed, 15 Feb 2012 23:02:55 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Making Meetings Productive</title>
		<link>http://blog.protoshare.com/2011/11/making-meetings-productive/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=making-meetings-productive</link>
		<comments>http://blog.protoshare.com/2011/11/making-meetings-productive/#comments</comments>
		<pubDate>Mon, 21 Nov 2011 17:45:20 +0000</pubDate>
		<dc:creator>Alex Johnson</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[Industry]]></category>
		<category><![CDATA[ProtoShare Workflows]]></category>

		<guid isPermaLink="false">http://blog.protoshare.com/?p=1126</guid>
		<description><![CDATA[I recently stumbled onto this article, Read This Before Your Next Meeting, (which is itself about the book, Read This Before Our Next Meeting) that really resonated with me. I&#8217;ll start out with my favorite quote (of a quote): Every &#8230; <a href="http://blog.protoshare.com/2011/11/making-meetings-productive/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I recently stumbled onto this article, <a title="Read This Before Your Next Meeting on OPENForum.com" href="http://www.openforum.com/articles/read-this-before-your-next-meeting" target="_blank">Read This Before Your Next Meeting</a>, (which is itself about the book, <a title="Read This Before Our Next Meeting on Amazon.com" href="http://www.amazon.com/Read-This-Before-Next-Meeting/dp/1936719169/" target="_blank">Read This Before Our Next Meeting</a>) that really resonated with me.</p>
<p>I&#8217;ll start out with my favorite quote (of a quote):</p>
<blockquote><p>Every meeting costs a fortune. Spend it wisely.</p></blockquote>
<p>And two excellent bits:</p>
<blockquote><p>Create an agenda and send material in advance for everyone to be prepared.</p></blockquote>
<blockquote><p>A meeting should only focus on two activities: Resolve conflict and to lead coordination of action.</p></blockquote>
<p>ProtoShare is integral to our development process. <a title="Cultivating Agility – Part II: Under the Hood" href="http://blog.protoshare.com/2011/07/cultivating-agility-part-2-for-agile-ux-teams/" target="_blank">We use it</a> in the design of every new feature. One thing I love about it is that everyone can review the prototypes on their own schedule, creating and replying to topics independently. It saves us a ton of time because many topics are resolved without ever needing to get together in a meeting.</p>
<p>Sometimes, however, a prototype generates significant confusion or disagreement. I suppose we could work through these issues offline as well, but at a certain point it becomes unproductive. It&#8217;s much easier to resolve contentious topics face-to-face, instead of keyboard-to-keyboard.</p>
<p>When we do get together, these topics have already defined the meeting agenda. Before coming to the meeting, each of us reads through the others&#8217; replies. That allows us to spend our time in the meeting resolving the conflicts and deciding on our next course of action (sounds familiar, right?).</p>
<p>When we design ProtoShare, we try to answer the question, &#8220;how can we help our customers move their projects forward?&#8221; As much fun as it can be, your <a title="How much should I prototype?" href="http://blog.protoshare.com/2011/03/how-much-should-i-prototype/" target="_blank">goal throughout this process</a> is probably not to make wireframes. More likely, your goal is to build something else entirely. Your wireframes are a way to raise questions, and your meetings are a way to answer them. The review process is purpose-built to help move your project forward.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.protoshare.com/2011/11/making-meetings-productive/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

