Posts Tagged ‘HBR’

The “big 8” deeply embedded life interests

Posted in Article Review, Human Resources Management on October 13th, 2009 by Paul McArdle1 Comment

.

In recent times we have been looking to the future, trying to be more thoughtful about how we structure the many things we need to get through each day in order that we can achieve our growth targets.

Hence, I pulled out an old copy of the article “Job Sculpting – the art of retaining your best people” (by Timothy Butler and James Waldroop) which I had been given a number of years ago.

read more »

The “5 Discovery Skills” for Innovation – and how it applies for Agile Software Development

Posted in Article Review, Innovation, Software Development on October 8th, 2009 by Paul McArdle4 Comments

.

Following my previous post (book review of “Tale of Two Systems” – but really a consideration of Agile & Lean Software Development) I have continued to read, and think (yeah, dangerous, I know).

The following two posts will be of interest:

1)  This post from the HBR Editor’s Blog titled “How do innovators think?” provides many good points (and some of the added comments at the bottom are great as well) but I want to cut to the chase and highlight the “5 Discovery Skills” included in the article:

Skill 1 = Associating – a cognitive skill that “allows creative people to make connections across seemingly unrelated questions, problems, or ideas”.  Like being able to find your way without needing a map.

Skill 2 = Questioning – like asking the “5 why’s”

Skill 3 = Observation, and (particularly) doing it really well – well enough to pick up nuances in behaviour, etc….

Skill 4 = Experimentation – try a lot of things and keep what works, as noted by Collins and Porras.

Skill 5 = Networking – the post notes that the key is that the networking is done with smart people who have little in common with them, but from whom they can learn.

2)  I read in the comments that someone has already made the link with Agile Software Development.  Here’s commentary by Bob MacNeal on his blog.

In particular with respect to Bob’s post, he has omitted the 3rd skill. I am not sure why he has done this, or if it is deliberate.

However one of the comments underneath sums it up when they note “To write great software you need to observe the detail that’s not included in the written version of the requirements.”  (my emphasis added, as I totally agree)

Given the challenges, opportunities and uncertainties our business faces, we need all 5 in spades!