<?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>I’m deeply committed</title><link>http://blogs.msdn.com/b/eric_brechner/archive/2010/03/01/i-m-deeply-committed.aspx</link><description>It’s mid-year career discussion time at Microsoft®. I could rant about the HR tools we use, but that’s like complaining about prostate exams—too inflated a target. Instead, what gushes out at me at this time of year are BOGUS commitments. 
 You’ve heard</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: I’m deeply committed</title><link>http://blogs.msdn.com/b/eric_brechner/archive/2010/03/01/i-m-deeply-committed.aspx#10275043</link><pubDate>Wed, 29 Feb 2012 23:47:39 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10275043</guid><dc:creator>animageofmine</dc:creator><description>&lt;p&gt;First of all, the idea of commitments is hardly useful, especially when you work in agile work environment. You don&amp;#39;t know what you would be working on in next 6 months because there is a monthly release cycle. So, obviously you have to enter something generic or you have to update every month, which is even worse. &lt;/p&gt;
&lt;p&gt;I have worked with more than 10 leads and almost all of them have their own way of defining commitments. Which one is the truth table ? A plain simple answer is that as long as your manager knows what you are doing and how is your performance, commitments is just a formality because it is a part of HR. Following book rules by first setting up commitments and reviewing them by putting a check point on each at the end of the year is a foolish decision. &lt;/p&gt;
&lt;p&gt;Atleast that&amp;#39;s what my opinion is. I find it hard to understand why does it matter so much. &lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10275043" width="1" height="1"&gt;</description></item><item><title>re: I’m deeply committed</title><link>http://blogs.msdn.com/b/eric_brechner/archive/2010/03/01/i-m-deeply-committed.aspx#10027430</link><pubDate>Sat, 19 Jun 2010 06:17:05 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10027430</guid><dc:creator>Mohamed Elsherif</dc:creator><description>&lt;p&gt;I don&amp;#39;t think the yearly commitments thing suits all businesses, for example I work in OSD, where we release every 6 month, and now working on 3 month release cycles, which means commitments are very hard to tie with release goals because I can&amp;#39;t foresee and neither do my manager the goals for the next releases and how different the situation now from the next 6 months.&lt;/p&gt;
&lt;p&gt;I think commitments system should be a living document that can be changed by both the employee and approved by his manager throughout the year, otherwise it becomes something we have to do and waste some time.&lt;/p&gt;
&lt;p&gt;That&amp;#39;s my opinion, and I expect to see some changes for this process in the future&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10027430" width="1" height="1"&gt;</description></item><item><title>re: I’m deeply committed</title><link>http://blogs.msdn.com/b/eric_brechner/archive/2010/03/01/i-m-deeply-committed.aspx#10026559</link><pubDate>Thu, 17 Jun 2010 16:23:35 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10026559</guid><dc:creator>JPitts</dc:creator><description>&lt;p&gt;Hey Eric, after reading this post, I was thinking it might help if you posted a number of sample commitments and did a bit of a disection on them (what specfically are BOGUS about them? what accountabilities are a good balance between being measurable and unique but not too self centric? what makes you say &amp;#39;awesome&amp;#39;?) Thanks!&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10026559" width="1" height="1"&gt;</description></item><item><title>re: I’m deeply committed</title><link>http://blogs.msdn.com/b/eric_brechner/archive/2010/03/01/i-m-deeply-committed.aspx#9978782</link><pubDate>Mon, 15 Mar 2010 16:10:12 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9978782</guid><dc:creator>publicus</dc:creator><description>&lt;p&gt;To add, the whole commitment system at Microsoft produces politics and some of the nastiest people I've ever seen in a corporate environment, people actually undermine each other on the same team due to the curve and commitments!&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9978782" width="1" height="1"&gt;</description></item><item><title>re: I’m deeply committed</title><link>http://blogs.msdn.com/b/eric_brechner/archive/2010/03/01/i-m-deeply-committed.aspx#9978779</link><pubDate>Mon, 15 Mar 2010 16:06:39 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9978779</guid><dc:creator>publicus</dc:creator><description>&lt;p&gt;The whole idea behind commitment is flawed. They should be eradicated and focus on profitability and rewards instead.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9978779" width="1" height="1"&gt;</description></item><item><title>re: I’m deeply committed</title><link>http://blogs.msdn.com/b/eric_brechner/archive/2010/03/01/i-m-deeply-committed.aspx#9972888</link><pubDate>Thu, 04 Mar 2010 15:34:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9972888</guid><dc:creator>Code Monkey</dc:creator><description>&lt;p&gt;Tools don't kill people busines processes kill people...&lt;/p&gt;
&lt;p&gt;I agree that we can simplify the entire process and focus on working more and being inside the review process less, don't forget that the tools we use are based on enabling the business process. &amp;nbsp;IT doesn't write requirements we simply try to enable them based on the current &amp;quot;best&amp;quot; technology choice. &amp;nbsp;(and then we don't get funding to keep investing... that could be another article)&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9972888" width="1" height="1"&gt;</description></item><item><title>re: I’m deeply committed</title><link>http://blogs.msdn.com/b/eric_brechner/archive/2010/03/01/i-m-deeply-committed.aspx#9972449</link><pubDate>Wed, 03 Mar 2010 22:08:42 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9972449</guid><dc:creator>Disillusioned engineer</dc:creator><description>&lt;p&gt;&amp;quot;Are you working on a critical, difficult, high-risk, impactful, and influential project that aligns with the team’s business direction and customer focus?&amp;quot;&lt;/p&gt;
&lt;p&gt;Some people have to work on unsexy, uncritical, unimpactful and uninfluential stuff, because without 90% of unsexy stuff the rest 10% don't make up for a shipped product. And what should you write for those?&lt;/p&gt;
&lt;p&gt;Perf review process at MSFT is BOGUS, why do you wonder that it results in BOGUS committments?&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9972449" width="1" height="1"&gt;</description></item><item><title>re: I’m deeply committed</title><link>http://blogs.msdn.com/b/eric_brechner/archive/2010/03/01/i-m-deeply-committed.aspx#9971004</link><pubDate>Mon, 01 Mar 2010 18:50:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9971004</guid><dc:creator>FutureTurnip</dc:creator><description>&lt;p&gt;So sorry to hear that you're a victim of &amp;quot;performance reviews&amp;quot; and the worst flavor of reviews, &amp;quot;calibrated performance reviews&amp;quot;.&lt;/p&gt;
&lt;p&gt;Deming listed this as one of the deadly sins. Your article points out many reasons for why (e.g., &amp;quot;The goal is to get real work done, not to spend weeks writing and editing commitments.&amp;quot;) &lt;/p&gt;
&lt;p&gt;Save your HR department and Microsoft millions upon millions in wasted effort. Improve morale, productivity, and qualit by just saying &amp;quot;NO&amp;quot;.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9971004" width="1" height="1"&gt;</description></item></channel></rss>