Posts Tagged ‘innovation’

Iterating through Little Bets

Posted in 03 - Product Development, Book Review, Innovation on November 10th, 2011 by Paul McArdle2 Comments

In more recent months, I’ve read a number of books on the topic (seems to be gaining prevalence, at least in terms of people willing to write – and buy – books).

Not that I mind, because it’s an approach that’s close to our heart.

The Book

What we thought

LittleBets
Little Bets – How Breakthrough Ideas Emerge From Small Discoveries

by Peter Sims
Thumbs up

Worth reading

I’ve posted separately about why we read, and review, so many books (and about the links above)…

.

read more »

Better design of our Business

Posted in Book Review on July 16th, 2011 by Paul McArdle3 Comments

Back around November 2009 read an article by Roger Martin promoting his new book, and posted about it here.

The book arrived and I read it some time ago, but some developments more recently prompted me to pick it up again.  Given the reliance our company has on product innovation, it was worth reading (even a 2nd time).

The Book

What we thought

The-Design-of-Business

The Design of Business – Why Design Thinking is the Next Competitive Advantage

by Roger Martin
Thumbs up

Not a large book,
but packs a punch

I’ve posted separately about why we read, and review, so many books (and about the links above)…

read more »

Becoming the Rabbit

Posted in Book Review, Problem solving, Value2 - Relentless Improvement on April 15th, 2011 by Paul McArdle1 Comment

Someone suggested I read this book a long time ago.  Apologies that I can’t remember who, or I would note your name here.

The Book

What we thought

ChasingTheRabbit

Chasing the Rabbit

by Steven J Spear
Thumbs up

An detailed, challenging read,
but well worthwhile

I’ve posted separately about why we read, and review, so many books (and about the links above)…

.

Because of the extensive and valuable discussion provided by the author, the following teaser does not do justice to the book – you have to read it to gain a real context.

PS - I’ve been told that there’s a newer version of the book available (now titled High Velocity Edge) that has a new preface and epilogue to reflect on Toyota’s recent issues.

read more »

Summary of Our Core Values

Posted in Values on March 1st, 2010 by Paul McArdle6 Comments

Beginning in early March, I have been progressively posting about each of our core values.

A.  Why focus on Values?

To provide context – i.e. to provide the reason why we do what we do.

Increasingly in future, we will be referring back to these core values to provide us a grounding as our business grows – they will define the basis for our culture (the way we do things around here).

It is through reference to these values that we will be able to rapidly grow our number of clients with only a relatively small growth in the size of our team.

read more »

What’s Required of our “Product Managers”

Posted in 03 - Product Development, Roles & Responsibilities on January 4th, 2010 by Paul McArdle4 Comments

The post below is an early draft (and is incomplete).

It has been superseded by a more recent update, which I posted here on the blog on Thursday 25th February 2010.  The post below remains here (for now) as a historical curiosity.


The role of the Product Manager follows a similar model as that we will apply to our Chief Software Engineer and, as such, the position might be equally termed:

Manager for Discerning, Developing and Delivering what the Customer Wants

Again, all three aspects of the role are important.

1)     Summary

As Product Manager, you will accept direct responsibility for one (or more) of our Mature Products.

With this responsibility, your focus will be on maximising the value we deliver to clients through this product – whilst at the same time maximising the value we generate for ourselves, over the longer-term.

You will also accept responsibility as a Project Manager in the software development process – utilising the Agile methods promoted by the Chief Software Engineer.

If necessary, you will also play a role in coding, though this will not be your primary focus.


read more »

What is innovation?

Posted in CEO's Philosophy, Innovation on December 31st, 2009 by Paul McArdle7 Comments

.

It is a loaded term – it means different things to different people (here’s the Wikipedia reference, for instance).

To me, it seems that there are two competing “innovation camps” which I sum up as follows: read more »

How can we be better product designers?

Posted in 02 - People & Culture, Book Review, Design, Event Review, Methodology, Requirements Gathering on December 28th, 2009 by Paul McArdle1 Comment

.

Here’s an interesting video (runs for an hour) promoting a new book “Glimmer:  How Design Can Transform Your Life, and Maybe Even the World” by Warren Berger (and Bruce Mau).

Seems like an interesting book, so have thrown it in our shopping cart, and will review it sometime in 2010.

read more »

Does it have to be Analysis -vs- Innovation?

Posted in Analysis, Article Review, Innovation on November 10th, 2009 by Paul McArdle4 Comments

I’ve recently posted about what some are calling the rise of the “Age of Analytics”, and also posted several times on innovation (such as this note about 5 “discovery skills”).

Not sure how I stumbled upon this article in Business Week – it’s titled “The Design of Business” and is written by Roger Martin (of Rotman School of Management) to coincide with the launch of his new book (which we have duly added to our Amazon cart and will review in due course). read more »

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

Posted in 03 - Product Development, Article Review, Innovation 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!