<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Garra Gao on Medium]]></title>
        <description><![CDATA[Stories by Garra Gao on Medium]]></description>
        <link>https://medium.com/@garragao?source=rss-65f09bfdcf2b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*YgVFcH859Kt-VbRJ.</url>
            <title>Stories by Garra Gao on Medium</title>
            <link>https://medium.com/@garragao?source=rss-65f09bfdcf2b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:52:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@garragao/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[2 Learnings from book: High Output Management]]></title>
            <link>https://medium.com/@garragao/2-learnings-from-book-high-output-management-aa35c5db1ec5?source=rss-65f09bfdcf2b------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa35c5db1ec5</guid>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[manager]]></category>
            <category><![CDATA[performance-reviews]]></category>
            <dc:creator><![CDATA[Garra Gao]]></dc:creator>
            <pubDate>Fri, 05 Jun 2020 22:58:48 GMT</pubDate>
            <atom:updated>2020-06-11T02:00:25.490Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to Lead and Review Performance Effectively?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/795/0*R7ga8tp0uWjl20Os.png" /></figure><p>This is the first article of my “two sparked thoughts series”! :) Great books always sparked further thinking and starting this series is to capture these thinkings as well as cultivate the articulation of thinking and learning.</p><p>First book up — <strong>High Output Management</strong>. Despite the book was first published in 1983, it still has the timeless wisdom and perspectives for managers at all levels.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/398/0*tB7dBq6SL_iwHH1Y" /></figure><p><strong>1.Task-Relevance Maturity: </strong>Measures the maturity level based on the sum of the individual’s experience, training, education and background for a particular task.</p><p>Grove highlighted the need for separation on one’s competency and maturity vs one’s task relevance maturity (TRM). This theory can shine lights on both a parent and a manager. Leadership style should adapt not only to the audience but also to the certain task that they need to perform. It’s such a no brainer statement but yet in reality it’s hard to remember especially if you have already formed certain understanding and impressions about the talents in your team, and when assign them with brand new task or additional responsibility, it’s a tendency for both of you to continue with the same ways of working.</p><p>Grove outlined the correspondent managerial style based on the Task-relevance Maturity below.</p><p><strong>Low:</strong> The most effective approach is one that offers very precise and detailed instructions. The key characteristics of this approach are: <strong>Structured; task-oriented; tell “when, what, how”.</strong></p><p><strong>Medium:</strong> When TRM of the junior grows, the more effective style moves from the structured to one more given to communication, emotional support and encouragement. The key characteristics of this approach are: <strong>Individual-oriented; emphasis on two-way communication, support, mutual reasoning.</strong></p><p><strong>High: </strong>As the TRM becomes even greater, the effective management style change again. Here the manager’s involvement should be kept to a minimum, and should primarily consist of making sure that the objectives toward which the junior is working are mutually agreed upon. The key characteristics of this approach are: <strong>involvement by manager minimal; establishing objectives and monitoring.</strong></p><p>Notice that throughout the growth of TRM, the structure moves from being <em>externally imposed</em> to being <em>internally given</em>.</p><p>The framework is however, should always paired with open communication and mutual understanding with your team to put into proper and most effective use.</p><p>Let me give you an example, in the book Grove has shared an example of promoting an extremely productive sales manager from field to the plant, where he was placed in charge of a factory unit. The sales manager’s performance was very low at the beginning and gradually increased to his peak level in the previous role in time. But the process was a surprise to his management team which Grove pointed out that it was due to the lack of understanding of TRM, where the management confused the manager’s general competence and maturity with his task-relevance maturity.</p><p>I agreed with that point, but at the same time, I would argue that even with the management’s understanding of separating the personal maturity vs task maturity, they will still possibly make the wrong assumption on his TRM, what if they still believe that he has high TRM, or what if in another case, the individual actually has transferrable experience that leads to high TRM but the management is not aware of. The gap of management’s impression on his TRM vs his actual TRM, will be most effectively bridged through open communication and setting expectation for trials and errors, with an mutual agreement of the management style to begin with and the upcoming iterative versions to find the most optimal one.</p><p>The framework is useful but only if the communication is there to properly assess the right level of TRM.</p><p><strong>2. Performance review:</strong> How to provide an effective feedback to juniors in your team.</p><p>Keep in mind that your goal is to improve their performance. This goal often get diluted when with no proper preparation, the conversation will end up including superficiality, clichés, and laundry lists of unrelated observations that pull your juniors towards multiple directions, a.k.a no where. I’ve summarized and revised three steps below that I found useful to remember and continue practicing in the future.</p><p><strong>Step 1:</strong> Before the conversation, take out a blank paper, you can refer to the past notes from 1:1, meeting observations, previous performance reviews, etc., start writing down everything that you think about when considering your junior’s performance.</p><p><strong>Step 2:</strong> When you’ve finished, scan through it and look for the relationship between the various items listed. You will probably begin to notice that certain items are different manifestations of the same phenomenon, and that there may be some indications <em>why</em> a certain strength or weakness exists. When you find such relationships, you can start calling them “messages” for the junior. Now you can draw some conclusions and examples to support the message.</p><p><strong>Step 3:</strong> Cross out, condense, summarize and prioritize to only<strong> two messages </strong>whether if it’s one good and one bad or all good or all bad, but just two. Your intent is to focus on giving the very feedback that can most effectively help to improve your junior at that given point in time.</p><p>Now let’s try practising these 2 renewed wisdoms and see how they go. :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa35c5db1ec5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>