Book Short:  Go Where They Ain’t

Blue Ocean Strategy: How to Create Uncontested Market Space and Make Competition Irrelevant, by W. Chan Kim and Renée Mauborgne isn’t bad, but it could literally be summed up by the title of this post.  I think it’s probably a better book for people who aren’t already entrepreneurs.

That said, there are two chapters that I found pretty valuable.  One is called “Reconstruct Market Boundaries,” which is a great way of thinking about either starting a new business or innovating an existing one.  It’s a strategy that we’ve employed a few times over the years at both Return Path and Authentic Response.  It’s hard to do, but it expands the available territory you have to cover.  The classic Jack Welch/GE “we don’t just sell jet engines, we sell AND SERVICE jet engines” which expanded their addressable market 9x.

The other useful chapter was “Get the Strategic Sequence Right.”  The sequence of questions to answer, according to the authors, is:

• Will buyers get enough utility out of it?
• What’s the right price?
• Can you cost it low enough to make good margin?
• Are you dealing with adoption hurdles?

The reason I found this sequence so interesting is that I think many entrepreneurs mix the order up once they get past the first one.  It’s easy to start with market need and then quickly jump to adoption hurdles, cost things out, and go with a cost-plus pricing strategy.  The book documents nicely why this order is more productive.  In particular, pricing first, then costing second, is both more market-focused (what will people pay?) and more innovative (how can I think creatively to work within the constraint of that price point?).

The common theme that’s most interesting out of the book is that new frameworks for thought produce killer innovation.  That’s clearly something most entrepreneurs and innovators can hang their hat on.

Wither the News? (Plus a Bonus Book Short)

It’s unusual that I blog about a book before I’ve actually finished it, but this one is too timely to pass up given today’s news about newspapers.  The Cult of the Amateur: How Today’s Internet is Killing Our Culture, by Andrew Keen, at least the first 1/2 of it, is a pretty intense rant about how the Internet’s trend towards democratizing media and content production has a double dirty underbelly:

poor quality — “an endless digital forest of mediocrity,”

no checks and balances — “mainstream journalists and newspapers have the organization, financial muscle, and and credibility to gain access to sources and report the truth…professional journalists can go to jail for telling the truth” (or, I’d add, for libel)

So what’s today’s news about newspapers?  Another massive circulation drop — 3.6% in the last six months.  Newspaper readership across the country is at its lowest level since 1946, when the population was only 141 million, or less than half what it is today.  The digital revolution is well underway.  Print newspapers are declining asymptotically to zero.

Don’t get me wrong.  I’m an Internet guy, and I love the democratization of media for many reasons.  I also think it will ultimately force old media companies to be more efficient as individual institutions and as an industry in order to survive (not to mention more environmentally friendly).  But Keen has good thoughts about quality and quantity that are interesting counterpoints to the revolution.  I hope at least some newspapers survive, change their models and their cost structures, and start competing on content quality.  The thought that everyone in the world will get their news ONLY from citizen journalists is scary.

I’m curious to see how the rest of the book turns out.  I’ll reblog if it’s radically different from the themes expressed here.

Update (having finished the book now): Keen puts the mud in curmudgeon. He doesn’t appear to have a good word to say about the Internet, and he allows his very good points about journalistic integrity and content quality and our ability to discern the truth to get washed up in a rant against online gambling, porn, and piracy. Even some of his rant points are valid, but saying, for example, that Craigslist is problematic to society because it only employs 22 people and is hugely profitable while destroying jobs and revenue at newspapers just comes across as missing some critical thinking and basically just pissing in the wind. His final section on Solutions is less blustry and has a couple good examples and points to offer, but it’s a case of too little, too late for my liking.

Book Short:  A SPIN Selling Companion

At Return Path, we’re big believers in the SPIN Selling methodology popularized by Neil Rackham. It just makes sense. Spend more time listening than talking on a sales call, uncover your prospect’s true needs and get him or her to articulate the need for YOUR product. Though it doesn’t reference SPIN Selling, Why People Don’t Buy Things, by Kim Wallace and Harry Washburn is a nice companion read.

Rooted in psychology and cognitive science, Why People Don’t Buy Things presents a very practical sales methodology called Buying Path Selling. Understand how your prospect is making his or her buying decision and what kind of buyer he or she is, be more successful at uncovering needs and winning the business.

The book has two equally interesting themes, rich with examples, but the one I found to be easiest to remember was to vary your language (both body and verbal) with the buyer type. And the book illustrates three archetypes: The Commander, The Thinker, and The Visualizer. There are some incredibly insightful and powerful ways to recognize the buyer type you’re dealing with in the book.

But most of the cues the authors rely on are physical, and lots of sales are done via telephone. So I emailed the author to ask for his perspective on this wrinkle.  Kim wrote back the following (abridged):

Over the phone it is fairly easy to determine a prospect’s modality. I’ve developed a fun, conversational question which can be asked up front, “As you recall some of your most meaningful experiences at XYZ, what words, thoughts, feelings or visuals come to mind? Anything else?”

If you’re interested in letting your blog readers test their modalities, the link below will activate a quick 10 question quiz from our website that generates ones modality scores along how they compare with others. (It’s like Myers-Briggs applied to decision making.) http://www.wallacewashburn.com/quiz.shtml

In any case, if you are a sales, marketing, or client services professional (or even if you just play one on TV), Why People Don’t Buy Things is a quick, insightful read.  Thanks for the quick response, Kim!

Book Short:  Finishing First

The Power of Nice:  How to Conquer the Business World with Kindness, by Linda Kaplan Thaler and Robin Koval, is one of those “airport books” that takes about an hour to read.  I had an ear-to-ear grin reading the book, in part because, well, it’s just a happy book, filled with anecdotes about how a smile here or a gesture of kindness there made a difference in someone’s life — both personally and professionally.

But part of my interest in the book was also driven by a long-standing debate we have at Return Path over whether we’re “too nice” as a company and whether we should have “sharper elbows.”  I was struck by a few comments the authors made, things you would expect like “nice doesn’t mean naïve” as well as things you wouldn’t like “help your enemies.”  To me, that says it all about success in business:  you can be a fierce competitor externally and demand accountability internally and still be a warm and kind person, and that’s the best (and most rewarding) place to be.

9/11’s 10th

I wasn’t yet writing this blog on 9/11 (no one was writing blogs yet), and if I had had one, I’m not sure what I would have written.  The neighborhood immediately surrounding the World Trade Center had been my home for more than seven years before the twin towers fell, and it continued to be my home for more than seven years after they fell.  That same neighborhood was Return Path‘s home for its first 18 months or so, across two different offices.  Like all Americans, the attack felt personal.  Like all New Yorkers, it was in our face.  But it hit home in a different way for those of us who lived and worked in Lower Manhattan.

For the seven years after the attacks, I stopped by Ground Zero on the morning of 9/11 to reflect and memorialize the event.  I won’t be doing that this year — between living outside the city, the kids, and the likely overwhelming crowds, it doesn’t make sense.  So this post will have to suffice as this year’s reflection on the 10th anniversary of that awful day.

My memories from that day and the weeks that followed are a little jumbled now, as memories often are.  The things I remember most vividly, both personal and professional, are:

• The smell and the smoke.  Up until the New Year, over 3 months after the attacks, a plume of smoke was rising from Ground Zero, and the air had a putrid smell of burning everything — building materials, fuel, fragments of life
• I had left the city that morning to drive to a meeting in Danbury, Connecticut at Pittney-Bowes with our then head of sales, Dave Paulus.  We both received calls on our cell phones at the same instant from Mariquita and Pam telling us to turn on the news, that a plane had crashed into the World Trade Center.  For a while, everyone assumed it was an accident.  We continued with our meeting, although it kept getting interrupted with more bad news coming in via our senior contact’s assistant, until she wheeled a TV into the conference room so we could watch for ourselves
• I couldn’t get back into the city that night, so Dave and I crashed at my Grandma Hazel’s house in Westchester.  When I finally did get home, Mariquita and I met up and stayed with our friends Christine and Andrew on the upper west side and listened all night to the fighter planes cruising up and down the Hudson River, sentries on patrol
• When we finally could go back to our apartment, we had to go on foot from Canal Street south, and we had to show proof of residence (in our case, a copy of our lease) to get past the military guards.  With no traffic allowed and no subways running in Lower Manhattan for a week or two, the streets had an eerie emptiness about them.  The prevalence of national guardsmen and NYPD patrols toting machine guns made it feel like a war zone
• At work, where the Internet 1.0 meltdown was still in process, we were in the middle of negotiating a life-saving financing and acquisition of Veripost with Eric Kirby and George.  We hit the pause button on everything, but we picked back up and dusted ourselves off within a day and got those deals done within a few weeks and saved the company
• We had one junior employee in our New York office who got into his car on the afternoon of 9/11, drove to New Hampshire, and never contacted us again.  Just completely blew a fuse and dropped out.  It wasn’t until we tracked down his parents a few days later that we even knew he was safe and sound
• I was fortunate not to lose anyone close in the attacks, but my friend Morten lost over a dozen close friends who were all traders from his town in New Jersey.  He attended every single funeral.  How he got through that (and how others got through their many losses) remains beyond my comprehension, even today

The only thing I have really blogged about over the years related to 9/11 was my post Morning in Tribeca in 2004 when the skeleton of WTC7, the first rebuilt building, was going up.  Now that the Freedom Tower is rising, it finally feels like the Ground Zero site has great forward momentum and will in fact be fully renewed in a few years once the bulk of this construction is done and the tenants have moved in.  That will be a great day for New York, and for America.

The Tension That Will Come With the Future of Work

A lot has been written about the Work From Anywhere life that knowledge workers are leading right now due to the pandemic, and what will come next.  Fred has a great post on it, and I’m curious to see how his and Joanne’s “Home Office Away From Home” space called FrameWork does when it opens.  In that post, he references a few other posts and articles worth reading:

• Imagine Your Flexible Office Work Future – Anne Helen Petersen
• We’re Never Going Back – Packy McCormick
• The Future of Offices When Workers Have Choice – Dror Poleg

Instead of entering the debate about what the future will look like, which no one really knows other than to say “not like the past,” I want to focus on a tension I’ve been mulling over lately, and that is the tension between a company’s leaders and its employees.  You could also call it a tension between extroverts and introverts.  And in this regard, Packy McCormick is both right and wrong about the debate:  right in the sense that employees will make the decision, not companies; wrong in the sense that the best employees “are not going to work for companies that make them shave, get dressed, hop into a car or a crowded subway, and sit at a desk in an office five days a week with their headphones on trying to avoid distractions and get work done.”  That’s a blanket statement that, as with most blanket statements, misses an incredibly important point.

That some people like, want to, need to, or benefit from working in offices more often than not.

That those people are some of the most talented, creative, and high potential people in an organization.

And that those people are frequently the ones with the least “voice” in an organization — new employees, younger workers, introverts, and people from underrepresented groups.

It will be really easy for senior people who, in many cases, have longer commutes and kids they are now accustomed to seeing a lot more, not to mention really nice and private home offices, to default to working from home.  In many cases, they’ve already done more of that than most employees, well, because they can.  But the problem is that those people are perfectly fine working from home.  Work and decisions come to them.  Their career trajectories are pretty set.  They will seek out anyone in the organization to ask them any question, any time.

But think about the topic from the perspective of an entry level account coordinator, an associate product manager, a graphic designer in marketing, a financial analyst in the FP&A group, or an AR specialist in accounting. .  Less exposure to decision makers can’t possibly help this.  If you’re one of those people, here are the things you miss out on when there’s no office:

• You don’t get to participate in or overhear interesting conversations in the break/lunch room or at the water cooler about something going on in the company that you’re not working on.  This reduces your ability to learn in unstructured ways at work or get thoroughly onboarded into a new company
• You don’t get to see who comes and goes from the office or different meeting rooms.  This may sound silly, but watching a business in, seeing who is in a glass-walled conference room or what slides are up on the wall, helps employees stimulate good ideas about their day to day work.  This limits your ability to connect the dots and better understand the big picture at work 
• You don’t get to have a casual conversation with your department head or CEO in the elevator or hallway or a conference room between meetings.  That “skip level” leader is much less likely to know who you are or what you do.  This can make it harder for you, the next time you have an idea you want to share or feedback you want to give, to approach a leader.  It also makes it a little tougher for you the next time you’re in line for some kind of promotion or development opportunity

Of course all employees CAN in theory make themselves known, can learn, can seek out others in the organization, and can try to re-create hallway serendipity from the comfort of their own Zoom screens.  It just doesn’t come naturally to most; practically speaking for many, it’s impossible; and it’s particularly hard for younger or quieter team members.  There’s a ton of research about how women in particular aren’t as comfortable advocating for themselves when it comes time to ask for a raise or a promotion.  If you’re the CEO of a 100 person organization, you might be inclined to chat with the new entry level AR person at the coffee machine for a few minutes; you’re unlikely to be excited about a 30-minute Zoom with her.  

(By the way, this whole construct may be different for engineering, where engineers are likely more comfortable with remote work AND aren’t held back in their career development as a result.)

I’ll close this post with an anecdote.  As part of our work at Bolster, I was doing something called an Executive Team Scalability Assessment with the CEO of a $75mm SaaS company a month or so ago.  When we were doing a review of how strongly each of his leaders role modeled company values, he paused when he got to one leader and said, “I honestly don’t know.  That person has only been here 10 months, but don’t worry, that’s just because of the pandemic.  I haven’t seen them in action.”  10 months!  People will discover at some point that it was much easier to “lift and shift” an existing organization to the cloud in year 1 of the pandemic than it will be to sustain or build a culture with a lot of new employees in year 2 or 3 of remote-first work.

CEOs who care about their culture, their people, inclusion and belonging, and their people’s professional development will have to really re-think how things work if they are going to steer their companies towards remote-only policies, or even remote-first employees, and still be inclusive workplaces.  That doesn’t mean it can’t be done.  But gravitating to a remote-only way of life, even if it’s personally enticing or if some talented and vocal employees demand it, may not be in the best interest of their overall company and employee population.

(This is the sixth post in a series documenting the work I did in Colorado on the Governor’s COVID-19 Innovation Response Team – IRT.  Other posts in order are 1, 2, 3, 4, and 5.)

As these posts have been running, a few people have asked me to quickly compare this experience to the experience of being a Startup CEO.  And that’s an interesting way to think about it. In a lot of ways, the couple of weeks of getting the IRT up and running felt like starting up a new business, only a lot more intense.  Following the outline of sections in Startup CEO:  a field guide to scaling up your business…

Part One: Storytelling.  The whole timeframe was super compressed.  It took us 2 days to be able to spend 4 hours writing our initial pitch deck defining scope, structure, and staffing request – and that was while we were working hard on our first two workstreams.  In a startup environment, that process would have taken much longer, involved more customer discovery and product/market fit research and spending 100% of our time on that. But then we got our “approval and funding” in about 45 minutes – that would have taken weeks and involved dozens of pitch meetings.  In terms of creating the organization’s Mission, Vision, and Values, we didn’t even bother, although I think it helped that the three of us were generally on the same page with how to work and that urgency was the essence of our job. The larger emergency operations team that we were more or less embedded in also had a very clear set of values and operating principles on display…although we didn’t actually go read them, I think they were in sync with our view of our team’s mission and principles.  In terms of “bringing our story to life,” that was wholly unnecessary!

Part Two: Building The Company’s Human Capital.  Like a startup, getting it right with the first handful of employees means everything.  In this case, the first two deputies on the team, handpicked by the Governor’s staff, were awesome and critical.  Bringing someone in from the private sector to run a public sector team only works when the rest of the team is incredibly knowledgeable about how the machinery of state government works.  And in the end, I think Sarah will be a better leader for the team than I was because she had a combination of private and public sector experience (and within her public sector experience, she had a lot of emergency response experience).  In general, the recruiting process was soooo different than private sector and public sector normally are. The first two team members handpicked the best people they knew in other relevant parts of the government. People were brought onto the team after one short phone call.  Other state departments heads loaned their people willingly. No such thing as a comp negotiation or a reference check. There were a bunch of other things under the “Human Capital” heading that are interesting notes/comparables as well. First, feedback in a compressed-timeframe emergency is something that you absolutely can’t skip – and you can’t wait for a formal process either.  Our team was pretty good about giving feedback at least daily in a semi-structured way as well as in the moment. We didn’t really have time to get into things like career pathing and compensation and firing. We did, after about 6 days at the suggestion of Kacey, our Chief of Staff, move the team to almost entirely remote (other than leadership and occasional critical meetings). This worked surprisingly well for a workforce probably unaccustomed to remote work.  The rest of the world is also learning how to do a lot of that now, too.

Part Three: Execution.  This whole experience was 97% execution.  In fact, we had a hard time finding time for things like strategy and planning because there was a crushing amount of work to do (welcome to emergency response), and a small team to do it.  We didn’t have to worry about raising money, budgeting, forecasting, reporting, and some of the other major execution steps in the private sector. We did do a good job of creating goals and milestones for our workstreams, but even that took a couple of weeks, and in retrospect, I wish we’d been able to do some of those sooner.  In terms of how our work got done, we were very conscious of creating daily meeting routines to structure our day and work – but there was no such thing as even a weekly meeting (let alone monthly strategics or quarterly offsites!), only daily meetings, multiple times per day. One thing that was interesting – I talk in the book about being deliberate and consistent with your platforms, especially around communication.  Channel proliferation is a real issue today (much more so than when I wrote the book), but we had an interesting mismatch at the beginning. The public sector team was used to email, text, and Google hangouts for comms. Nothing else. The private sector team used those things but was a lot more comfortable with Trello, Zoom, and Slack. Thank goodness both teams used G-Suite and not a mix of that and LiveOffice. But getting everyone on the team to converge on a couple systems is a work in progress and was messy, as evidenced in this great moment where Kacey was holding a laptop up to an actual whiteboard to show one of our private sector teams how she was thinking about something. 

Part Four: Building and Leading a Board of Directors.  This is kind of N/A, although the proxy for it in our case on the IRT was the leadership structure of the Emergency Operations Center and then the Governor and the part of his cabinet that was keyed into the emergency response.  In this regard, the main differences between the private sector and public sector were speed/formality (no room for formality when you’re meeting daily or at a moment’s notice!), and, interesting, the need for integration. A company reports to its board on how it’s doing.  This team had to use its “board” to make sure it was integrating with other state agencies and initiatives. In this way, the team functioned more like a business unit within a company than an actual company.

Part Five: Managing Yourself So You can Manage Others.  This was obviously critical…and obviously quite difficult.  And within the overall Emergency Operations Center (outside of our team, the real emergency professionals), there were people, including leaders, who were working 7 days/week for multiple weeks on end, and long days, too.  At one point, the EOC leader posted this note on the wall, and he frequently took time in daily briefings to encourage everyone to take a day or two off and take care of themselves physically.  He role-modeled that behavior as well. You can only run a sprint for so long. Once it becomes clear it’s a marathon, well, you know.

Stay tuned for the final post in the series tomorrow…

I wrote part I of this post in 2011, and I feel even more strongly about it today. I generally keep this blog away from politics (don’t we have enough of that running around?), but periodically, I find some common sense, centrist piece of information worth sharing. In this case, I just read a great and very short book, Six Amendments: How and Why We Should Change the Constitution, by former Supreme Court Justice John Paul Stevens, that, if you care about the polarization and fractiousness going on in our country now, you’d appreciate.

If nothing else, the shattered norms and customs of the last several years should point people to the fact that our Constitution needs some revision. Not a massive structural overhaul, but some changes on the margin to keep it fresh, as we approach its 250th anniversary in the next couple decades.

Book Short: Sequel Not Worth It

Mastering the 7 Essentials of High Growth Companies, by David Thomson, was a poor sequel to the solid Blueprint to a Billion [review] [buy]– and not worth reading if you’ve read the original.  It was very short for its price and contained mildly interesting examples of “blueprint companies” that augmented the original book but didn’t uncover any new material or add any thinking to the mix.  Basically, it was like another couple chapters that should have been part of Blueprint.

It is not a bad buy in lieu of the original if you haven’t read either one yet, as Blueprint is a bit longer than necessary, but otherwise, you can skip this one.

On a side note – the author’s interactive scorecard is a decent diagnostic tool (though also, I am sure, a lead gen tool for his consulting business).

Book Short:  Way, Way Beyond Books

The Everything Store: Jeff Bezos and the Age of Amazon, by Brad Stone, was a great read.  Amazon is a fascinating, and phenomenally successful company, and Jeff is a legendary technology leader.  The Everything Store is a company and personal biography and totally delivers.

Forget about the fact that Amazon is now almost $100B in revenues and still growing like mad.  I find it even more amazing that a single company could be the largest ecommerce site on the planet while successfully pioneering both cloud computing services and e-readers.  The stories of all these things are in the book.

As a CEO, I enjoyed reading more of the vignettes behind the things that Amazon is reputationally known for in the tech world – doors as desks, their unique meeting formats, the toughness of the culture, the extensive risk taking of growth over profits, and what works and does not work about Bezos’ authoritative and domineering style.  And it’s always great to be reminded that even the biggest and best companies had to cheat death 10 times over before “arriving.”

This is good fun and learning for anyone in the business world.  It reminded me most of Walter Isaacson’s biography of Steve Jobs ,which I wrote about here, although it’s more of a company history and less of a biography than the Jobs book.

Book Short – A Smattering of Good Ideas that further my Reboot path

Ram Charan’s The Attacker’s Advantage was not his best work, but it was worth the read.  It had a cohesive thesis and a smattering of good ideas in it, but it felt much more like the work of a management consultant than some of his better books like Know How (review, buy), Confronting Reality (review, buy), Execution (review, buy), What the CEO Wants You to Know ( buy), and my favorite of his that I refer people to all the time, The Leadership Pipeline (review, buy).

Charan’s framework for success in a crazy world full of digital and other disruption is this:

Perceptual acuity (I am still not 100% sure what this means)

1. A mindset to see opportunity in uncertainty
2. The ability to see a new path forward and commit to it
3. Adeptness in managing the transition to the new path
4. Skill in making the organization steerable and agile

The framework is basically about institutionalizing the ability to spot pending changes in the future landscape based on blips and early trends going on today and then about how to seize opportunity once you’ve spotted the future.  I like that theme.  It matches what I wrote about when I read Mark Penn’s Microtrends (review, buy) years ago.

Charan’s four points are important, but some of the suggestions for structuring an organization around them are very company-specific, and others are too generic (yes, you have to set clear priorities).  His conception of something he calls a Joint Practice Session is a lot like the practices involved in Agile that contemporary startups are more likely to just do in their sleep but which are probably helpful for larger companies.

I read the book over a year ago, and am finally getting around to blogging about it.  That time and distance were helpful in distilling my thinking about Charan’s words.  Probably my biggest series of takeaways from the book – and they fit into my Reboot theme this quarter/year, is to spend a little more time “flying at higher altitude,” as Charan puts it:  talking to people outside the company and asking them what they see and observe from the world around them; reading more and synthesizing takeaways and applicability to work more; expanding my information networks beyond industry and country; creating more routine mechanisms for my team to pool observations about the external landscape and potential impacts on the company; and developing a methodology for reviewing and improving predictions over time.

Bottom line:  like many business books, great to skim and pause for a deep dive at interesting sections, but not the author’s best work.