<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Filters and Priorities</title><link>http://blogs.msdn.com/b/jmeier/archive/2011/07/11/filters-and-priorities.aspx</link><description>One of my mentors showed me a simple success pattern for achieving more at work, while gaining more credibility and freedom.&amp;#160;&amp;#160; It’s Filters and Priorities.&amp;#160; The method works by&amp;#160; connecting your work to business priorities.&amp;#160; He</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Filters and Priorities</title><link>http://blogs.msdn.com/b/jmeier/archive/2011/07/11/filters-and-priorities.aspx#10185859</link><pubDate>Wed, 13 Jul 2011 02:42:03 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10185859</guid><dc:creator>JD Meier</dc:creator><description>&lt;p&gt;@ sfuqua -- Speaking their language is helpful and it sounds like that&amp;#39;s what you&amp;#39;re doing with capacity, progress, user stories, and process improvement.&lt;/p&gt;
&lt;p&gt;However, I would uplevel the game, and find out what problems they want to solve. &amp;nbsp;At the end of the day, solving the problems they care about, makes you relevant and valued. &amp;nbsp;Speaking in their terms and filters simply helps you connect and avoid conflicts in communication and styles.&lt;/p&gt;
&lt;p&gt;If you know what problem they are trying to solve, you can race to the end in mind.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10185859" width="1" height="1"&gt;</description></item><item><title>re: Filters and Priorities</title><link>http://blogs.msdn.com/b/jmeier/archive/2011/07/11/filters-and-priorities.aspx#10185662</link><pubDate>Tue, 12 Jul 2011 17:18:59 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10185662</guid><dc:creator>sfuqua</dc:creator><description>&lt;p&gt;Sounds like an intuitive and reasonable approach to managing up. Putting a concrete example together is challenging, however. That said, perhaps this simple example helps illustrate (if this is not the direction you intended, then please provide a nudge that way): manager has a priority of Project X, and filters such as (capacity, progress, user stories, process improvement). In finding the intersection, I should be clearly communicating about the progress of Project X in terms of user stories; if there is a lack of capacity, or extra capacity, then I need to express this frequently – and again, linking to user stories can be helpful, and so forth. GANTT charts, while useful in some circumstances, are not part of his language or triggering, so communication using a GANTT chart is unlikely to “amplify [my] success”.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10185662" width="1" height="1"&gt;</description></item></channel></rss>