Skip to main content

Book: The One Thing You Need to Know...About Great Managing, Great Leading, and Sustained Individual Success

As the title suggests, this book is partitioned into three sections - in the opinion of the author:

How to be a great manager
How to be a great leader
How to achieve sustained individual success

I found this book useful as it clearly defines what the core competencies of a "leader" and a "manager" are; which is something that I have not found elsewhere as yet. Have to admit that some of what I read was news to me - I've realised that my role involves both. To spell it out, effectively managing is looking after your individuals and your team; helping them find success in their work and supporting them. Leading is about providing a vision for your constituents (team) which they can aspire to; painting a picture of what things will be like when the goal is achieved and being clear about what it'll take to get there.

The author introduces the concept of a "controlling insight". This is a succinct description of the one thing that stands out clearly as being the key to success in any distinct pursuit (for example, being a great manager). Each section starts by developing a hypothesis, then revealing the controlling insight that the hypothesis supports. From there each section goes onto explain how to use the controlling insight to your advantage in order to achieve success in that area.

I found the section on sustained individual success most intriguing. The author encourages the reader to cleave away the parts of their existence that they find dull or annoying and reclaim that space for pursuits that inspire them. He offers some clever techniques to do this mostly without disruption. Many useful concepts and approaches are covered.

The content is persuasive and inspiring. My one comment would be that there are a statements made that indicate the author believes that the phenomenon of religion is currently in the process of being phased out and replaced by the world of business and technology - I'll simply say that I disagree. Overall a very good book.

Title: The One Thing You Need to Know...About Great Managing, Great Leading, and Sustained Individual Success
Author: Marcus Buckingham
Tags: Leadership, Management, Sustained Individual Success

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…