Posts Tagged ‘reading list’

“Get Rid of the Performance Review!” – more than a catchy title

Wednesday, July 14th, 2010

get rid of the performance reviewSamuel Culbert’s new book “Get Rid of the Performance Review!” has proved itself headline-worthy. A PR person’s email to me stated, in part, “Culbert’s book has been featured in The Wall Street Journal, AP, Gannett, Reuters, the New York Post and many other outlets.” And it’s easy to see why. Almost no one likes or values performance reviews – managers who give them, and, certainly, those who are subjected to the stilted process and its results. Another lousy raise, another year in the same job, another set of unclear expectations for the future.

Thankfully, though, Culbert’s book is more than a rant against the performance review as currently practiced – though, for the first 55 pages, it is that. Manager-only reviews, 360 degree reviews and, most of all, HR organizations come are subjected to withering critique. The rest of the book provides an analysis of why performance reviews are ill-suited to their objectives (justifying pay increases, setting out critical performance goals and outlining personal development plans).

To Culbert, the structure of the review is fatally flawed. A boss of limited insight and deep personal biases (this isn’t an attack on bosses, merely a description of human beings in general) dictates the content of a review and a powerless subordinate sits there and takes it (or dissents, at some risk to her own career). The boss checks off things the subordinate is good at, and decides on some things she is not good at, and there it is.

After shooting down such an easy target, Culbert takes the remaining 170 pages or so and lays out some very commonsense but profound lessons about managing people and leading organizations. Particularly striking is this advice on compensation:

For straight talk about pay, the corporate world requires a shift in which compensation is recognized as the marketplace-dependent variable it is. Don’t mix apples and oranges by bringing up pay during a performance review. Don’t send mixed messages to subordinates, telling them one minute their performance is top-notch and then in the next minute that their pay isn’t going up.

How might this new system work?

First, bosses need to decide what pay raise and other forms of compensation they are willing to offer. Figuring out the offer entails every bit as much self-assessment (by the boss) as assessment of the subordinate’s value. Bosses need to scrutinize the bases of their beliefs about the subordinate’s talent and skills, what they are willing to pay incrementally for them, and their faith in their own capacity to provide the support needed to increase the subordinate’s productivity.

Bosses also need to assess the subordinate’s expectations and make a judgment about how the subordinate values the current compensation package, which includes such intangibles as, say, happiness with a child’s school situation or proximity to a spouse’s office, or whether they are going through a divorce. Finally, bosses need to study the marketplace. They need to know what people in comparable roles receive and assess the availability of a replacement if the subordinate leaves.

Once the compensation package is determined, it should be communicated impersonally–perhaps written down and handed to the subordinate in a sealed envelope.

At this point it’s up to the subordinate either to agree or to negotiate. If the choice is to negotiate, the ensuing “conversation” should be exclusively about pay. It shouldn’t be about performance quality or perceived “faults.” If the boss doesn’t like the quality of the subordinate’s performance and can get someone more to his or her liking, the boss should do so.

There’s tons more great stuff in the book. HR won’t like it. Neither will many bosses, because Culbert insists that bosses need to be full partners in their employees’ performance. If performance suffers, the boss is also accountable. The boss and subordinate are a team delivering results to the organization. This implies, to me, a lot of work on the boss’s part. But it’s important and crucial work.

Something has to be done to improve the current situation, which with the economic crisis has only gotten more dysfunctional. I was reading the book on a recent airplane flight and my neighbor asked me about it. Then he related a story he had lived through some years earlier.

I got a new boss who was really well-respected in the company. He thought I had potential to be promoted. He was pretty hard on me in my first review. He laid out all the things I needed to do to be ready for the next step. It was a bit harsh, but I understood. A few months later the company merged. They needed to cut staff by 20%. HR didn’t really know any of the employees, so they took the performance reviews and simply cut the people with the lowest 20% rankings – including me. My boss was appalled but there was nothing he could do about it. So instead of getting promoted I got let go.

There are probably thousands of these stories. Hopefully enough people will read and absorb the lessons in “Get Rid of the Performance Review!” that this situation will become rarer in the future. But I’m not too sure about that.

Love your own products, but don’t demonize others’

Wednesday, June 9th, 2010

When I first started working for GTE, I went to a seminar where different operating divisions discussed their businesses with a group of recent hires. The highlight of the afternoon was the lighting division, where the presenters highlighted their contempt for their arch-competitor, General Electric, by smashing a four-pack of GE lightbulbs under their feet.

I was working for the Government Systems group at the time, on a long-term project, and felt light years away from competitors. I envied my colleagues for the intense loyalty they displayed.

More recently, an executive at a company I know sent an email to all employees outlining his displeasure that certain employees were using competitor products instead of the company’s. Using the company’s products was a matter of loyalty. He made it clear: competitor products were banned from the workplace, and suggested that employees who didn’t agree were perhaps working for the wrong company.

In Oded Shenkar’s provocative new book “Copycats: How Smart Companies Use Imitation to Gain a Strategic Edge,” he writes this:

Innovators must focus their efforts on a few core features, and even then they may produce a novel and creative recombination of imitated and innovative elements. This combination will surely be resisted by innovators that despise imitation and view it as anathema to their vision statement and claims of corporate leadership; but unless these companies accept imitation on equal terms, they may drown in “invented here” risks and costs while watching their competitors fuse innovation and innovation into a winning formula (p.182)

The lesson: you can’t figure everything out yourself, and shouldn’t. The same pride that causes you to smash your competitors’ lightbulbs under your feet can prevent you from using your curiosity and problem-solving skills to thoroughly understand companies who have the same issues and perfectly good solutions that you could adopt – rather than relying on your own skills to solve every problem.

Is loyalty of the type expressed by lightbulb smashing and the executive’s email bad? No. But it has side effects, and those can be significant. The balance between loving your own products and being curious and respectful about what others (even competitors) have done is very delicate, and executives, no matter how intense their own loyalty may be, must manage this balance.

Walter Kiechel’s “The Lords of Strategy” fills in a missing piece of business history

Wednesday, May 26th, 2010

lords of strategy coverHow did management consulting get to be where it is? Did firms like McKinsey, Bain, and Boston Consulting Group simply appear out of nowhere, fully formed, to foist re-engineering on companies everywhere and snap up graduates of the top business schools? Well, no. To find out what really happened you need to read “The Lords of Strategy: The Secret Intellectual History of the New Corporate World,” by former HBR editor Walter Kiechel, a well-written, cheeky history of the birth and growth of the modern consulting industry.

Kiechel paints vivid pictures of industry pioneers like Bruce Henderson of BCG and Bill Bain, and cannily outlines the keys to their success (in Henderson’s case, a passion for using mathematics to analyze business; in Bain’s, an ability to build relationships with CEOs and a willingness to tie project compensation to increased stock price). He also traces the next wave of strategy emerging from universities, most prominently the ideas of Michael Porter and their impact, through the re-engineering craze to the current day.

But most importantly, he puts into context what the strategy revolution, as applied by the firms he focuses on, meant to US (and eventually worldwide) business. One, a belief in the power of analytics; and two, the value of models to spread learning (i.e., best practices).

The book ends with a whimper rather than a bang. The last couple of chapters, looking ahead at the future of strategy and discussing the impacts of the financial crisis, are not up to the standards of the rest of the book, as if the events of 2007-2008 derailed Kiechel’s intended story arc. As a result, the summing up is a bit disoriented, as I suppose we all are in business after those cataclysmic recent events.

I also wish the book were more carefully sourced. After reading several chapters, it becomes clear that much of Kiechel’s source material comes from direct interviews with key members of the consulting world. The book would be better if those sources were identified and end-noted, and that other assertions connected back to their sources as well. Why this wasn’t done is a mystery to me and undermines the book’s authoritativeness.

Nonetheless, “The Lords of Strategy” is a valuable addition to the business bookshelf. It shines a light on and humanizes a part of the business world that operates in secret but which has significant influence on businesses the world over.

The Best Business Books of 2009

Thursday, December 10th, 2009

In the wake of the worst US economic catastrophe since the Great Depression, everybody realized this: Making money is harder than we thought. So, this year, books on innovation had special resonance. Luckily, there were some great ones out there. So many, in fact, that this year’s best-of list includes two “companion volumes”–other good books from this year that cover similar material from another perspective.

These are the best books I read this year:

design-driven innovation1. Design-Driven Innovation – Roberto Verganti. A fascinating book that looks at companies that don’t merely create new products, but develop products and services that create new meaning for customers. Is that important? Well, companies that do it well avoid commoditization and generate outsized profits for long periods of time. Think Apple.

(companion volume: The Design of Business by Roger Martin)

Discovery-Driven Growth2. Discovery-Driven Growth – Rita Gunther McGrath and Ian MacMillan. Verganti’s book covers the more creative side of innovation, while McGrath and MacMillan discuss the process that established companies should use to improve their innovation efficiency–that is, bringing more successful products to market and spending less on the failures. The central lesson: do more work on paper, and scrupulously document & validate assumptions as you go.

(companion volume: Innovation Tournaments by Christian Terweisch and Karl Ulrich)

enterprise2.0

3. Enterprise 2.0 – Andrew McAfee. A clear description for the general business audience of how web 2.0 products, like social network software, wikis, messaging services, and the like, can be deployed to help corporations work more effectively. Excellent combination of case studies, theoretical models, and a clear-eyed assessment of the obstacles in the way of wide adoption.


4. Think Again: Why Good Leaders Make Bad Decisions and How to Keep it From Happening to You – Sydney Finkelstein, Jo Whitehead and Andrew Campbell. A timely book that shows how smart, experienced people can make terrible decisions, and what safeguards companies can use to improve their decisionmaking. Illuminates the many cognitive biases at work during the decision process, which helps the reader to understand why so many decisions that look atrocious in hindsight were considered reasonable and logical at the time.

Collaboration by Morten Hansen5. Collaboration – Morten Hansen. Discusses how collaboration in business works, and when it doesn’t work, then provides a map for companies to improve their collaborative behavior – including unifying your workforce, nurturing “T-shaped” management and using networks intelligently. Key message: collaboration has a cost, and you need to make sure the payoff of collaboration outweighs it.

Related posts:
Podcast: Sydney Finkelstein on “Think Again”
On “Discovery-Driven Growth”
Podcast: Roberto Verganti on “Design-Driven Innovation”
On “Collaboration”
Video Review of “Enterprise 2.0″

Video review of Andrew McAfee’s “Enterprise 2.0″

Monday, November 30th, 2009

enterprise2.0TRANSCRIPT:

We’re here today to talk about “Enterprise 2.0” by Andrew McAfee. He is with MIT, used to be at Harvard Business School. Just switched over a couple of months ago. He writes an excellent blog on IT and business, that I’d recommend you read if you haven’t come across it yet. And so, he’s just produced his first book. To explain the title, Enterprise 2.0 is a term he coined to refer to using web 2.0 tools like Flickr, Facebook, YouTube, Twitter and similar tools in a business context.

The book is a lot like a recent book, “Groundswell,” that explained to general business people how social tools affected customers and markets and how to use those to communicate and listen. Communicating from inside the business to outside. “Enterprise 2.0″ performs a similar task, focusing on using those tools inside the business, more for collaboration and tapping the collective intelligence of employees. And so it takes this marginal topic and moves it to a general management-type discussion. Which I think is really important, to get it out of the IT discussion into the management discussion.

So as part of that objective he does a really good job of explaining how these tools work and also what ties them together because if you think about tools like Flickr or YouTube or a blogging platform or a messaging platform or a wiki there are a lot of differences among those but he’s tied together the common threads, using an acronym called SLATES (search, links, authoring, tags, extensions and signals). Signals, for example, like RSS that allows people who follow these platforms without having to log on to them every single hour to see what’s changed.

Another important part of the book is in putting the different tools into a context in terms of how useful they’d be for different organizational problems. He uses a bullseye metaphor focused on the strength of ties between colleagues to explain that. At the center of the bullseye are strongly-tied colleagues meaning people who work together in the same department, in the same location, all the way out to the edge of the bullseye. meaning colleagues who have no relationship at all. Different tools apply at different levels of the bullseye. In the center, people with strong ties would use tools like wikis, or collaborative development tools, like Google Docs.

Midway out the bullseye are colleagues with weak ties. People who know each other but don’t get together often, who don’t talk often, but would like to keep apprised of each other’s activities for the purposes of sharing knowledge, best practices, identifying solutions to problems, and so forth. For that ring of the bullseye, Facebook-like tools are very useful.

At the outer edge of the bullseye, where colleagues have no relationship other than that they work for the same company, a prediction market is a useful tool, that gathers people’s guesses about the possibility of certain things happening like a certain sales volume being reached or likelihood an innovation will succeed in the marketplace and aggregating that information to get a better answer than any individual would come up with themselves.

He doesn’t go overboard in terms of enthusiasm for how great these things are and how it’ll change companies overnight, and he has a pretty clear-eyed view of how difficult it is going to be to bring these tools to wide use. It just takes a long time -and he dwells on that at some extent – how long it takes for revolutionary innovations to take hold, and he doesn’t think this is any different, though he is optimistic that it’ll happen eventually.

And finally in the book he talks about kind of different management models or practices that work well with these tools, and by contrast he talks about typical Model 1 behaviors which are more command-and-control type behaviors, self-protecting behaviors and less-collaborative behaviors, which don’t go well with these new tools. To really utilize these new tools, people have to adopt what he calls Model 2 behaviors, which are collaborative, not so much focused on self-protection but looking out for the best interests of the company. Quite a different model than what most people have seen where they work. And I think that heaps underline the challenges in getting these systems adopted and in wide use.

It’s an excellent book, very well-organized and well-written. It takes an important topic and brings it into the mainstream. I really enjoyed it and I think you will too.

My reading journal: Roger Martin’s “The Design of Business”

Wednesday, November 11th, 2009

design of business coverThe Design of Business: Why Design Thinking is the Next Competitive Advantage,” by Roger Martin. 2009: Harvard Business Press, 190pp.

When did you read it? November 2009.

Subject: Hot on the heels of Tim Brown’s “Change by Design,” Rotman School dean Roger Martin, author of “The Opposable Mind” discusses how design thinking can help businesses balance exploration (the search for new solutions) and exploitation (extracting value from existing solutions) to improve their innovative capability.

Did you like it? How many stars would you give it (1-5)? 4

Summary: Martin describes the process of innovation in three steps, something he calls the “knowledge funnel”: (1) staring into a mystery; (2) coming up with a heuristic, or rule of thumb, that allows you to address the mystery; (3) systematizing your solution – in Martin’s words, turning the heuristic into an algorithm. This process, to Martin, is design thinking.

He spends time discussing the preference business has for reliability (i.e., consistency and repeatability) over validity (meeting a desired objective). Validity is the starting point for innovation – the discovery of something new that helps illuminate a mystery. Since validity is not predictable or repeatable, and tends to rely on qualitative, intuitive assessments (i.e., pattern matching), companies that rely on quantitative measurement struggle with it. It was easiest for me to understand validity, as Martin uses it, as a synonym for “right-brained” or “artistic.” Successful businesses balance the desire for reliability with a relentless search for new validity.

As Martin described this process – taking mysteries, developing heuristics and then refining algorithms from it, it seemed quite simple. Why doesn’t every company do this? But I also thought that there are lots of mysteries that don’t lend themselves to heuristics, and lots of heuristics that can’t turn into algorithms. There are lots of failures on the way to the next great business algorithm. Not only that, there are lots of successful businesses built on heuristics alone [for example, your favorite restaurant, assuming it's not part of a chain]. Martin’s point, which is not stated explicitly, is that you can’t build large businesses without this transition to algorithms. You can’t have McDonald’s without a cooking and serving system. You couldn’t have Wal-mart without its distribution model.

There’s not a discussion of the cost of algorithmized businesses to society. On my last trip to downtown Boston I was hard pressed to find a business that was not part of a national chain; much different from when I Iived there in the 1990’s. But I digress – Martin isn’t writing as a social critic; he’s a business professor.

Favorite quotes:

“Vice President of Marketing” denotes a permanent position with a set of ongoing tasks…. As well suited as that construct is for running known heuristics and algorithms, it is not an effective way to move along the knowledge funnel. That activity is by definition a project; it is a finite effort to move something from mystery to heuristic or from heuristic to algorithm. pp.118-119

Designers produce prototypes for feedback, but managers are accustomed to delivering final products. p.121

Status comes from running large, high-revenue business units whose operations have been reduced to reasonably reliable algorithms that product results on time and on budget. Those are the highest goals, that is, the ones that command the highest compensation. That is why most executives prefer the known to the unknown. p.125

Was it similar to anything you have read before? Of course, there are echoes of “Change by Design” (Brown’s earlier HBR article is referenced). And the idea of “staring into mysteries” reminds me somewhat of “changing the inherent meaning of a product” from Roberto Verganti’s “Design Driven Innovation.” 2009 is definitely the year of design thinking in business!

Martin’s book is less ambitious than Verganti’s, but broader (in a good way) than Brown’s. And his ability to create a powerful, memorable metaphor remains intact (I think I’ll be using “knowledge funnel” and maybe even “validity vs. reliability” in the future).

Will this book end up on your bookshelf or in the library donation pile? The bookshelf.

Related posts:
On “The Opposable Mind”
Processes can be art or science
On “Design-Driven Innovation”
Reading journal: “Change By Design”

My reading journal: Tim Brown’s “Change By Design”

Thursday, November 5th, 2009

Change By DesignChange by Design: How Design Thinking Transforms Organizations and Inspires Innovation,” by Tim Brown with Barry Katz. 2009: Harper Business, 264pp.

When did you read it? October 2009.

Subject: A presentation of the idea of “design thinking” – the use of close observation, imagination, and consideration of constraints to conceive and implement innovative solutions to problems in business and society.

Did you like it? How many stars would you give it (1-5)? 3.5

Summary: Brown is the CEO of IDEO, the acclaimed design consultancy that helped Apple create the iPod, designed the MyBook external hard drive for Western Digital and the Palm V, along with countless other products. The first part of the book, “What Is Design Thinking?” reviews the approach that IDEO uses to attack problems and come up with innovative solutions. To Brown, design is far more than putting an attractive package around an existing product – instead, it is a way to start from a ground-level assessment of a customer need and design a total solution to the problem. Emphasis is on going out in the field to observe potential users of products to see what they do (or don’t do), the value of divergent (idea-generating) vs. convergent (integrative) thinking and early and ongoing prototyping.

The second part of the book takes up questions for the future of design thinking, such as: can companies learn to do this themselves? can it improve our broken experiences, such as the dreaded airport security line? and can it help in some of our intractable problems, such as building a sustainable future?

Favorite quote: “Rarely will the everyday people who are the consumers of our products, the customers for our services, the occupants of our buildings, or the users of our digital interfaces be able to tell us what to do. Their actual behaviors, however, can provide us with invaluable clues about their range of unmet needs.” p.41

Did anything surprise you? I was surprised, and frankly a bit disappointed, that the book is focused almost solely on work done by IDEO. While there are occasional references to other thinkers like Peter Drucker, Gary Hamel and William Whyte, they are cursory. There is no bibliography or end notes (instead, there’s a list of IDEO projects referenced, along with people who worked on the projects, for each chapter). The only book discussed at any length is Roger Martin’s “The Opposable Mind.” [Interestingly, Martin has just published his own book on design thinking, called "The Design of Business: Why Design Thinking is the Next Competitive Advantage." I'm reading that now.]

Skating over people (other than a few brief anecdotes) who influenced design thinking and overwhelmingly referring to IDEO projects lends the book the air of a memoir as opposed to a work of scholarship. And given that Brown is IDEO’s CEO, it makes the book feel a bit like public relations. Which is a shame, because the topic is important and timely and Brown’s description of design thinking and case studies are excellent.

Will this book end up on your bookshelf or in the library donation pile? The bookshelf. While it doesn’t reach greatness, it’s a good book on an important topic.

Related posts:
On “The Opposable Mind”
On Gary Hamel’s “The Future of Management”

A wide-ranging (and free) e-book on narrative

Wednesday, September 16th, 2009

Kathy Hansen of the A Storied Career blog has been conducting interviews of storytelling figures large and small for nearly two years now, and has collected these into an e-book, available via this link.

I’ve been following the interview series with interest and, as mentioned in the title of this post, it’s a very wide-ranging look at storytelling and its uses. As such, there’s some of it that doesn’t speak to me very much. On the other hand, there are parts that I find extremely valuable. Like this…

Cynthia Kurtz on “approaches that don’t respect the integrity of the raw story and end up … injecting the biased interpretations of people outside the community:” There are two positions embedded in that statement — raw stories and self-interpretation — and I can tell a story from my own experience describing how I came to my current understanding of each position. The first position is that raw stories of personal experience are far superior to crafted stories for the things I care about when working with stories. For the purposes of advertising products and services, delivering specific purposeful messages, and entertaining people, crafted stories are often (but not always) best. But for the purposes of helping people learn, think, make decisions, get new ideas, grow, and get along, I’ve found that there is nothing better than a raw story. (NB: The entire interview with Cynthia is so valuable I have printed it out and refer to it regularly.)

and this:

Whitney Quesenbery on storytelling in user experience design: Although user experience [UX] stories are built on insights from research, their purpose is to help create something new. Often, they explore how a new or updated product can change an unsatisfactory experience into a good one. They describe a possible future condition, and in doing so help it become a reality.

This is not all user experience stories, of course. Sometimes, we use stories to present a current or past situation. But the reason we spend time thinking about current experience is to be able to create new experiences — and move us into the future. … Every UX project involves managing a lot of information. Even a small site involves balancing the business goals, user needs, and technical possibilities. When you are working on a large project it’s hard to stay focused on the goal of creating an excellent user experience, because you are managing so many details and (sometimes) conflicting needs. The other difficulty is keeping the “user” in sight. Perhaps that sounds strange for work on the user experience, but typically the users are not part of the design and development team, so it’s easy to ignore them.

With their ability to communicate so effectively, and on such a deep level, stories are one way to manage both challenges. They are a natural way to describe events, brainstorm ideas, engage the imagination, and build community around the new design.

oh, and this (self-promotion alert):

John Caddell: There has been an immense amount of investment in the last 20 years in business-process re-engineering and process standardization and in IT systems and to support those initiatives. We’ve taken process improvement about as far as it can go. In fact, we’ve taken it a bit too far. With companies applying Six Sigma to things like sales processes (???), and not surprisingly achieving poor results, it is time to seek new tools. And narrative is a perfect tool to help shed light on complex questions (Is our reorganization helping the company to perform better? Is this a good or lousy place to work? Why aren’t people buying our new product?).

Here are some of the other contributors whose work I know and respect:
Stephane Dangel
Thaler Pekar
Shawn Callahan
Ardath Albee

So, I’d recommend you take a look; you’ll likely find things that you can use.

Follow ups – Netflix & “Harry Potter Marketing”

Tuesday, June 23rd, 2009

Both the above topics, subjects of recent posts, were discussed today in separate articles in the Wall Street Journal.

This article recounts the history of Netflix’s move into on-demand video, with a nice behind-the-scenes view into the thinking of CEO Reed Hastings, and the senior team’s discussions as they pondered trying to make their old business model, delivering DVDs by mail, obsolete. (Here’s our earlier post on the subject.) The story of the development of the device that eventually became Roku is fascinating – demonstrating a collaborative approach and healthy dissent that’s rare in senior teams I’ve known. (In particular, Hastings is candid about his Apple envy–as we learned from “Think Again: Why Good Leaders Make Bad Decisions and How to Keep it From Happening to You,” being aware of how attachments can affect decisions is crucial for avoiding disasters.)

And this piece discusses the relaunch of the Ford Taurus. This one particular quote caught my eye:

“I think Ford is chasing the original Taurus fans with this car, all of which are much older than when that car was at its peak,” said Karl Brauer, editor in chief at Edmunds.com, an auto-sales Web site. “The new model seems more like a Ford Town Car targeted at 45-plus drivers rather than a high-volume family sedan.”

Does this mean that Ford is engaging in “Harry Potter Marketing” – in which a brand ages with its audience? If so, it provides a stark contrast with its competitor GM, whose attempts to reposition Cadillac triggered this recent post.

I look forward to following the Taurus’ progress in the marketplace – to see if the target group will buy it enough numbers to inspire further attempts at HPM.

Related posts:
Frontiers of innovation: Netflix demolishes own business model
Shop Talk Podcast: Sydney Finkelstein on “Think Again”
Why didn’t GM use “Harry Potter Marketing”?

“The Silver Lining” is a good intro to the new innovation methods

Thursday, June 11th, 2009

While reading Scott Anthony’s new book “The Silver Lining: An Innovation Playbook for Uncertain Times” you get the feeling of a project rushed into production. It’s written as a reaction to the financial crisis and resulting upheaval, which means it’s been less than a year in creation. It’s small-sized and brief (180 pages). As a result it doesn’t go into the depth other recent innovation books do.

Nonetheless, it’s a worthwhile read, especially if you want a quicker overview than you can get with “The Catalyst,” “Discovery-Driven Growth” or “The Innovator’s Guide To Growth” (co-written by Anthony, a book which “The Silver Lining” owes a particular debt to).

Anthony, president of the Innosight consultancy (co-founded by “Innovators’ Dilemma” author Clayton Christensen) is an acolyte for Christensen’s brand of disruptive innovation–which often means developing “good enough” products that do less, for significantly less cost, than incumbent products. A theme of “The Silver Lining,” then, is creating entirely new products without low-value features, as opposed to the incumbent’s default innovation approach–adding new features. This remains an important and underused insight more than a decade after it was first put forth.

My favorite bit of the book has to do with companies’ often distorted view of what the market needs their products to do–views that shape the product’s evolution and often, paradoxically, make it less useful to the customers it intends to serve. Writes Anthony, “A company’s view of performance rarely matches the market’s view of performance” (p.133). My experience with Customers Are Talking projects bears this out. My clients are consistently surprised by (and sometimes upset with) what the marketplace says they’re good, and not so good, at doing.

2009 has been a good year for innovation books so far. If you can only buy one, I’d go with “Discovery-Driven Growth.” If you can afford three, add “The Catalyst” and “The Silver Lining” to the list.