Skip to main content

Book: Helping People Win at Work

This book provides a useful framework for performance review. The main premise is that you give the individual the "test" at the start of the review process - meaning that you work out between you and them what their goals are for the quater in advance.

The book is divided into four sections.

The first section looks at the review structure - it's a little bit boring, but useful nonetheless. Reviews are quaterly and the review at the end of the quater is filled out by the team member (or "tribe member") only; the team leader ("tribe leader") looks at the review and may enter into a discussion where there is a difference in opinion as to how a member has progressed with a stated goal.

The second section talks about building a culture; assumptions, beliefs, vision and values. How to develop a learning culture and how to cultivate a strong vision and set of shared values. Some really useful learning in this section.

The third discusses/reviews the leadership style of Garry Ridge, president of the WD-40 Company. This is and interesting one, as Garry goes into his background and how he's ended up being the influential and thoughtful leader he clearly is. Garry promotes the idea of looking to your background to help you define yourself as a leader and your leadership style.

Finally, Ken Blanchard finishes off with the fourth section by providing a series of "simple truths" about how to help people win at work. For example; "servant leadership is the only way to go", "celebrate success", etc. Again all invaluable insights. I like the concept of Servant Leadership.

There's a section at the end of the book that gives a set of tables which can be used to build up a performance review framework as is described in section one.

Overall, really useful book. Would certainly recommend it. A very quick read in-fact, probably a fast reader could knock it off in a day or a couple of hours even.

Title: Helping People Win at Work "Don't Mark My Paper, Help Me Get An A"
Author: Ken Blanchard and Garry Ridge
Tags: Business, Leadership

Comments

Popular posts from this blog

HOW-TO: Add/edit a field in Team Foundation Server 2012 using Visual Studio 2012

It's been a while since I made a purely technical post...

So, today I wanted to make a change to a Microsoft Team Foundation Server 2012 (TFS2012) instance that I am working with to reflect "Actual" time spent on a task - mainly for reporting purposes, and because I have found in the past that making this minor process adjustment yields a relatively useful metric over the long-term.

I am using the Microsoft Scrum 2.1 Process Template (http://msdn.microsoft.com/en-us/library/vstudio/ff731587.aspx) for a project that I am working with. So that I don't forget how to do this (again!) I will blog-post the procedure I've used to add this field to the template as a screen-shot-based tutorial, as follows...
Before Assuming you are familiar with the Scrum Process Template (2.1-ish) - open a task and take a look at the "Details" section, as follows:


 This is where I want my "Actual" field to show up.
Get the Power Tools Download and install the latest v…

HOW-TO: Apply a “baseless merge” in Team Foundation Server 2010 (and 2012)

Another purely technical post on TFS...
The scenario We wish to migrate code between branches that do not have a branch/merge relationship, in order to expedite urgent changes being made by a project team, without disrupting on-going BAU development work. Sample branch hierachy/strategy Imagine the following branching strategy in TFS (visible by connecting to TFS via Visual Studio 2010 or 2012):

Essentially you have a "DEV" branch, which has a "QA" branch, which in turn has a "PROD" branch. DEV is the branch that you would be using for BAU development. As a piece of development matures, you move it into QA, where it is tested by your internal QA team. There may be further changes made in DEV that are moved into the QA branch as the QA team pick up issues. Once the QA team are happy with a packaged of changes, they will move them into PROD, which is essentially the hand-over to the customer. The PROD branch represents the software that the customer has.

Mo…

Eclipse/Android error: "Multiple dex files define [...]"

Wow, I am really going nuts blogging this-evening - 2nd post in less than an hour. 


Anyway this is a particularly nasty error that I keep running into with Eclipse/Android when starting the emulator after I have not run it for a little while. Since I run the risk of permanently forgetting the solution to the problem every time I walk away from my Android project (and thus having to spend a painful hour-or-so digging up the procedure again), I will blog it here, for my benefit, and for the benefit of anyone who may also suffer the same problem.


The gist is that when you start the emulator in debug mode (that is, you hit the button in the following image), you get the following error message come out on the console and a nasty popup telling you nothing more than there is an error with your program and you need to fix it:








[2012-04-06 23:20:57 - Dex Loader] Unable to execute dex: Multiple dex files define Lcom/google/gson/ExclusionStrategy;
[2012-04-06 23:20:57 - SimpleList] Conversion to Dal…