Book Short:  Steve Jobs and Lessons for CEOs and Founders

First, if you work in the internet, grew up during the rise of the PC, or are an avid consumer of Apple products, read the Walter Isaacson biography of Steve Jobs (book, kindle).  It’s long but well worth it.

I know much has been written about the subject and the book, so I won’t be long or formal, but here are the things that struck me from my perspective as a founder and CEO, many taken from specific passages from the book:

• In the annals of innovation, new ideas are only part of the equation. Execution is just as important.  Man is that ever true.  I’ve come up with some ideas over the years at Return Path, but hardly a majority or even a plurality of them.  But I think of myself as innovative because I’ve led the organization to execute them.  I also think innovation has as much to do with how work gets done as it does what work gets done.

• There were some upsides to Jobs’s demanding and wounding behavior. People who were not crushed ended up being stronger. They did better work, out of both fear and an eagerness to please.  I guess that’s an upside.  But only in a dysfunctional sort of way.

• When one reporter asked him immediately afterward why the (NeXT) machine was going to be so late, Jobs replied, “It’s not late. It’s five years ahead of its time.”  Amen to that.  Sometimes product deadlines are artificial and silly.  There’s another great related quote (I forget where it’s from) that goes something like “The future is here…it’s just not evenly distributed yet.”  New releases can be about delivering the future for the first time…or about distributing it more broadly.

• People who know what they’re talking about don’t need PowerPoint.”  Amen.  See Powerpointless.

• The mark of an innovative company is not only that it comes up with new ideas first, but also that it knows how to leapfrog when it finds itself behind.  This is critical.  You can’t always be first in everything.  But ultimately, if you’re a good company, you can figure out how to recover when you’re not first.  Exhibit A:  Microsoft.

• In order to institutionalize the lessons that he and his team were learning, Jobs started an in-house center called Apple University. He hired Joel Podolny, who was dean of the Yale School of Management, to compile a series of case studies analyzing important decisions the company had made, including the switch to the Intel microprocessor and the decision to open the Apple Stores. Top executives spent time teaching the cases to new employees, so that the Apple style of decision making would be embedded in the culture.  This is one of the most emotionally intelligent things Jobs did, if you just read his actions in the book and know nothing else.  Love the style or hate it – teaching it to the company reinforces a strong and consistent culture.

• Some people say, “Give the customers what they want.” But that’s not my approach. Our job is to figure out what they’re going to want before they do. I think Henry Ford once said, “If I’d asked customers what they wanted, they would have told me, ‘A faster horse!’” People don’t know what they want until you show it to them. That’s why I never rely on market research. Our task is to read things that are not yet on the page.  There’s always a tension between listening TO customers and innovating FOR them.  Great companies have to do both, and know when to do which.

• What drove me? I think most creative people want to express appreciation for being able to take advantage of the work that’s been done by others before us. I didn’t invent the language or mathematics I use. I make little of my own food, none of my own clothes. Everything I do depends on other members of our species and the shoulders that we stand on. And a lot of us want to contribute something back to our species and to add something to the flow. It’s about trying to express something in the only way that most of us know how—because we can’t write Bob Dylan songs or Tom Stoppard plays. We try to use the talents we do have to express our deep feelings, to show our appreciation of all the contributions that came before us, and to add something to that flow. That’s what has driven me.  This is perhaps one of the best explanations I’ve ever heard of how creativity can be applied to non-creative (e.g., most business) jobs.  I love this.

My board member Scott Weiss wrote a great post about the book as well and drew his own CEO lessons from it – also worth a read here.

Appropos of that, both Scott and I found out about Steve Jobs’ death at a Return Path Board dinner.  Fred broke the news when he saw it on his phone, and we had a moment of silence.  It was about as good a group as you can expect to be with upon hearing the news that an industry pioneer and icon has left us.  Here’s to you, Steve.  You may or may not have been a management role model, but your pursuit of perfection worked out well for your customers, and most important, you certainly had as much of an impact on society as just about anyone in business (or maybe all walks of life) that I can think of.

Book Short:  Culture is King

Joy, Inc.:  How We Built a Workplace People Love, by Richard Sheridan, CEO of Menlo Innovations, was a really good read. Like Remote  which I reviewed a few weeks ago, Joy, Inc. is ostensibly a book about one thing — culture — but is also full of good general advice for CEOs and senior managers.

Also like Remote, the book was written by the founder and CEO of a relatively small firm that is predominately software engineers, so there are some limitations to its specific lessons unless you adapt them to your own environment. Unlike Remote, though, it’s neither preachy nor ranty, so it’s a more pleasant read.  And I suppose fitting of its title, a more joyful read as well. (Interestingly on this comparison, Sheridan has a simple and elegant argument against working remotely in the middle of the book around innovation and collaboration.)

Some of the people-related practices at Sheridan’s company are fascinating and great to read about. In particular, the way the company interviews candidates for development roles is really interesting — more of an audition than an interview, with candidates actually writing code with a development partner, the way the company writes code. Different teams at Return Path interview in different ways, including me for both the exec team and the Board, but one thing I know is that when an interview includes something that is audition-like, the result is much stronger. There are half a dozen more rich examples in the book.

Some of the other quotable lines or concepts in the book include:

• the linkage between scalability with human sustainability (you can’t grow by brute force, you can only grow when people are rested and ready to bring their brain to work)
• “Showcasing your work is accountability in action” (for a million reasons, starting with pride and ending with pride)
• “Trust, accountability, and results — these get you to joy” (whether or not you are a Myers-Briggs J, people do get a bit of a rush out of a job well done)
• “…the fun and frivolity of our whimsically irreverent workplace…” (who doesn’t want to work for THAT company?)
• “When even your vendors want to align with your culture, you know you’re on the right path” (how you treat people is how you treat PEOPLE, not just clients, not just colleagues)
• “One of the key elements of a joyful culture is having team members who trust one another enough to argue” (if you and I agree on everything, one of us is not needed)
• “The reward is in the attempt” (do you encourage people to fail fast often enough?)
• “Good problems are good problems for the first five minutes. Then they just feel like regular problems until you solve them” (Amen, Brother Sheridan)

The benefits of a joyful culture (at Return Path, we call it a People-First culture) have long been clear to me. As Sheridan says, we try to “create a culture where people want to come to work every day.” Cultures like ours look soft and squishy from the outside, or to people who have grown up in tough, more traditional corporate environments. And to be fair, the challenge with a culture like ours is keeping the right balance of freedom and flexibility on one side and high performance and accountability on the other. But the reality is that most companies struggle with most of the same issues — the new hire that isn’t working out or the long-time employee who isn’t cutting it any more, the critical path project that doesn’t get done on time, the missed quarter or lost client.  As Sheridan notes though, one key benefit of working at a joyful company is that problems get surfaced earlier when they are smaller…and they get solved collaboratively, which produces better results. Another key benefit, of course, is that if you’re going to have the same problems as everyone else, you might as well have fun while you’re dealing with them.

If you don’t love where you work and wish you did, read Joy, Inc. If you love where you work but see your company’s faults and want to improve them, read Joy, Inc. If you are not in either of the above camps, go find another job!

The Phoenix Project:  a novel about IT, DevOps, and Helping Your Business Win, by Gene Kim, Kevin Behr, and George Spafford  is a logical intellectual successor and regularly quotes Eli Goldratt’s seminal work The Goal and its good but less known sequel It’s Not Luck.

The more business books I read, the more I appreciate the novel or fable format. Most business books are a bit boring and way too long to make a single point. The Phoenix Project is a novel, though unlike Goldratt’s books (and even Lencioni’s), it takes it easy on the cheesy and personal side stories. It just uses storytelling techniques to make its points and give color and examples for more memorable learning.

If your organization still does software development through a waterfall process or has separate and distinct development, QA, and IT/Operations teams, I’d say you should run, not walk, to get this book. But even if you are agile, lean, and practice continuous deployment, it’s still a good read as it provides reminders of what the world used to be like and what the manufacturing-rooted theories are behind these “new” techniques in software development.

I am so glad our technology team at Return Path, led by my colleagues Andy Sautins and David Sieh, had the wisdom to be early adopters of agile and lean processes, continuous deployment many years ago, and now dockers. Our DevOps process is pretty well grooved, and while I’m sure there are always things to be done to improve it…it’s almost never a source of panic or friction internally the way more traditional shops function (like the one in the book). I can’t imagine operating a business any other way.

Thanks to my long time friend and Board member Greg Sands of Costanoa Venture Capital for suggesting this excellent read.

Subtract: The Untapped Science of Less, by Leidy Klotz is a great read, and in concert with the philosophy of the book, this will be a short blog post.

The book’s basic premise is that less is more, addition by subtraction. The author’s examples range from the genius of the Strider Bike (bike without pedals) that allows 2-year olds to ride bikes to the Embarcadero in San Francisco. Many people don’t remember that that road used to be called the Embarcaro Freeway, a massive, ugly, two-tiered structure that blocked out the views and waterfront, and that the opportunity to tear down the whole thing following the massive 189 earthquake left San Francisco with a much simpler, beautiful, liveable waterfront by the Ferry Terminal.

There are many great takeaways in the book as well as an action plan for how to think about subtracting AND adding, not just adding, which is the normal reflex for humans, and I’d add ESPECIALLY for entrepreneurs!

We put these principles into action a couple weeks ago at Bolster. When we were crafting our 2024 plan, we worked methodically as a leadership team to reduce. We cut out words, but we also cut out topics and strategic initiatives. The end product was less than 50% the size (word for word) of the 2023 plan, and I think it’s much crisper, more memorable, and more actionable for our team than last year’s.

Hopefully over time, we will find more occasions to do less.

I’ll close with two of my favorite quotes, both of which were in the book. One is by Mark Twain, which is “I didn’t have time to write a short letter, so I wrote a long one instead.” The other is by Lao Tzu, which is “To attain knowledge, add things every day. To attain wisdom, subtract things every day.”

Sometimes less takes more time. But it’s almost always more valuable.

Inbox = Zero = Satisfying (Quasi Book Short)

I’m a big David Allen fan.  Amazingly enough, I haven’t blogged about him and his books yet, probably for the most part because I read the books before I started blogging.  But here they are.  The first one,  Getting Things Done: The Art of Stress-Free Productivity, is probably a little better than the sequel, Ready for Anything: 52 Productivity Principles for Work and Life, but both are worth reading.  When I first read them, they didn’t revolutionize my thinking about productivity and workflow management (I was already at least decent at those things), but they did really sharpen my thinking around the edges and give me a great framework to plug all my to-do lists into.

One of Allen’s great principles is Inbox = Zero…that in an email-centric office, you should try to completely empty out your Inbox at the end of every day.  Every item should have its home, even if that home is a “Will handle tomorrow” or “Waiting for Susie” folder.

Anyway, I usually get pretty close to Inbox = Zero, but the times I actually achieve it are few and far between.  This morning was one of those times.  It’s just incredibly satisfying.

Of course, it only lasted 8 minutes.

A Sense of Urgency, by John Kotter, is a solid book – not his best, but worth a read and happily short, as most business books should be.  I originally was going to hold off on writing this post until I had more time, but the subject matter alone made me think that was a mistake and that I should write it while it’s fresh in my mind.  <g>

The three tools to fight complacency are the organizing framework for the book — bring the outside in, behave with urgency every day, and turn crises into opportunities — are all good thoughts, and good reminders of basic management principles.  But there were a couple other themes worth calling out even more.

First up, the notion that there is a vicious cycle at play in that urgency begets success which creates complacency which then requires but does not beget urgency.  The theme is really that success can drive arrogance, stability, and scale that requires inward focus — not that success itself is bad, just that it requires an extra level of vigilance to make sure it doesn’t lead to complacency.  I’ve seen this cycle at different times over the years in lots of organizations, and it’s one of the reasons that if you look at the original companies on the Dow Jones Industrials index when it was expanded from 12 to 30 around 100 years ago, only one of them (GE) still exists.

Second, that busy-ness can masquerade as urgency but actually undermines urgency.  A full calendar doesn’t mean you’re behaving with urgency.  Kotter’s example of an Indian manager is great:

If you watch the Indian manager’s behavior carefully and contrast it with the hospital executive’s, you find that the former relentlessly eliminates low-priority items from his appointment diary. He eliminates clutter on the agenda of the meetings that do make it into his diary. The space that is freed up allows him to move faster. It allows him to follow up quickly on the action items that come out of meetings. The time freed up allows him to hold impromptu interactions that push along important projects faster. The open space allows him to talk more about issues he thinks are crucial, about what is happening with customers and competitors, and about the technological change affecting his business.

Finally, Kotter’s theme of “Urgent patience” is a wonderful turn of phrase.  As he says,

It means acting each day with a sense of urgency but having a realistic view of time. It means recognizing that five years may be needed to attain important and ambitious goals, and yet coming to work each day committed to finding every opportunity to make progress toward those goals.

How true is that?  It’s not just that big ships take a long time to turn…it’s that big opportunities take a long time to pursue and get right.  If they didn’t…everyone would do them!  Urgent patience is what allows you to install a bias for action in your team without causing panic and frenzy, which is never productive.

Thanks to my friend Chad Dickerson for recommending this book, a great read as part of Operation Reboot Matt.

Startup CEO (OnlyOnce – the book!), Part III – Pre-Order Now

My book, Startup CEO:  A Field Guide to Scaling Up Your Business, is now available for pre-order on Amazon in multiple formats (Print, Kindle), which is an exciting milestone in this project!  The book is due out right after Labor Day, but Brad Feld tells me that the more pre-orders I have, the better.  Please pardon the self-promotion, but click away if you’re interested!

Here are a few quick thoughts about the book, though I’ll post more about it and the process at some point:

• I’ll be using the hashtag #startupceo more now to encourage discussion of topics related to startup CEOs – please join me!
• The book has been described by a few CEOs who read it and commented early for me along the lines of “The Lean Startup movement is great, but this book starts where most of those books end and takes you through the ‘so you have a product that works in-market – now what?’ questions”
• The book is part of the Startup Revolution series that Brad has been working on for a couple years now, including Do More (Even) Faster, Venture Deals, Startup Communities, and Startup Life (with two more to come, Startup Boards and Startup Metrics)
• Writing a book is a LOT harder than I expected!

At this point, the best thing I can do to encourage you to read/buy is to share the full and final table of contents with you, sections/chapters/headings.  When I get closer in, I may publish some excerpts of new content here on Only Once.  Here’s the outline:

Part I: Storytelling

• Chapter 1: Dream the Possible Dream…Entrepreneurship and Creativity, “A Faster Horse,” Vetting Ideas
• Chapter 2: Defining and Testing the Story…Start Out By Admitting You’re Wrong, A Lean Business Plan Template, Problem, Solution, Key Metrics, Unique Value Proposition and Unfair Advantages, Channels, Customer Segments, Cost Structure and Revenue Streams
• Chapter 3: Telling the Story to Your Investors…The Business Plan is Dead. Long Live the Business Plan, The Investor Presentation, The Elevator Pitch, The Size of the Opportunity, Your Competitive Advantage, Current Status and Roadmap from Today, The Strength of Your Team, Summary Financials, Investor Presentations for Larger Startups
• Chapter 4: Telling the Story to Your Team…Defining Your Mission, Vision and Values, The Top-down Approach, The Bottom-Up Approach, The Hybrid Approach, Design a Lofty Mission Statement
• Chapter 5: Revising the Story…Workshopping, Knowing When It’s Time to Make a Change, Corporate Pivots: Telling the Story Differently, Consolidating, Diversifying, Focusing, Business Pivots: Telling a Different Story
• Chapter 6: Bringing the Story to Life…Building Your Company Purposefully, The Critical Elements of Company-Building, Articulating Purpose:  The Moral of the Story, You Can Be a Force for Helping Others—Even If Indirectly

Part II: Building the Company’s Human Capital

• Chapter 7: Fielding a Great Team…From Protozoa to Pancreas, The Best and the Brightest, What About HR?, What About Sales & Marketing?, Scaling Your Team Over Time
• Chapter 8: The CEO as Functional Supervisor…Rules for General Managers
• Chapter 9: Crafting Your Company’s Culture…, Introducing Fig Wasp #879, Six Legs and a Pair of Wings, Let People Be People, Build an Environment of Trust
• Chapter 10: The Hiring Challenge…Unique Challenges for Startups, Recruiting Outstanding Talent, Staying “In-Market”, Recruitment Tools, The Interview: Filtering Potential Candidates, Two Ears One Mouth, Who Should You Interview?, Onboarding: The First 90 Days
• Chapter 11: Every Day in Every Way, We Get a Little Better…The Feedback Matrix, 1:1 Check-ins, “Hallway” Feedback, Performance Reviews, The 360, Soliciting Feedback on Your Own Performance, Crafting and Meeting Development Plans      
• Chapter 12: Compensation…General Guidelines for Determining Compensation, The Three Elements of Startup Compensation, Base Pay, Incentive Pay, Equity              
• Chapter 13: Promoting                …Recruiting from Within, Applying the “Peter Principle” to Management, Scaling Horizontally, Promoting Responsibilities Rather than Swapping Titles               
• Chapter 14: Rewarding: “It’s the Little Things” That Matter…It Never Goes Without Saying, Building a Culture of Appreciation
• Chapter 15: Managing Remote Offices and Employees…Brick and Mortar Values in a Virtual World, Best Practices for Managing Remote Employees
• Chapter 16: Firing: When It’s Not Working…No One Should Ever Be Surprised to Be Fired, Termination and the Limits of Transparency, Layoffs

Part III: Execution

• Chapter 17: Creating a Company Operating System…Creating Company Rhythms, A Marathon? Or a Sprint?
• Chapter 18: Creating Your Operating Plan and Setting Goals…Turning Strategic Plans into Operating Plans, Financial Planning, Bringing Your Team into Alignment with Your Plans, Guidelines for Setting Goals
• Chapter 19: Making Sure There’s Enough Money in the Bank…Scaling Your Financial Instincts, Boiling the Frog, To Grow or to Profit? That Is the Question, First Perfect the Model, Choosing Growth, Choosing Profits, The Third Way
• Chapter 20: The Good, the Bad, and the Ugly of Financing…Equity Investors, Venture Capitalists, Angel Investors, Strategic Investors, Debt, Convertible Debt, Venture Debt, Bank Loans, Personal Debt, Bootstrapping, Customer Financing, Your Own Cash Flow
• Chapter 21: When and How to Raise Money…When to Start Looking for VC Money, The Top 11 Takeaways for Financing Negotiations
• Chapter 22: Forecasting and Budgeting…Rigorous Financial Modeling, Of Course You’re Wrong—But Wrong How?, Budgeting in a Context of Uncertainty, Forecast, Early and Often
• Chapter 23: Collecting Data…External Data, Learning from Customers, Learning from (Un)Employees, Internal Data, Skip-Level Meetings, Subbing, Productive Eavesdropping
• Chapter 24: Managing in Tough Times…Managing in an Economic Downturn, Hope Is Not a Strategy—But It’s Not a Bad Tactic, Look for Nickels and Dimes under the Sofa, Never Waste a Good Crisis, Managing in a Difficult Business Situation
• Chapter 25: Meeting Routines…Lencioni’s Meeting Framework, Skip-Level Meetings, Running a Productive Offsite
• Chapter 26: Driving Alignment…Five Keys to Startup Alignment, Aligning Individual Incentives with Global Goals
• Chapter 27: Have You Learned Your Lesson?…The Value (and Limitations) of Benchmarking, The Art of the Post-Mortem
• Chapter 28: Going Global…Should Your Business Go Global?, How to Establish a Global Presence, Overcoming the Challenges of Going Global, Best Practices for Managing International Offices and Employees
• Chapter 29: The Role of M&A…Using Acquisitions as a Tool in Your Strategic Arsenal, The Mechanics of Financing and Closing Acquisitions, Stock, Cash, Earn Out, The Flipside of M&A: Divestiture, Odds and Ends, Integration (and Separation)
• Chapter 30: Competition…Playing Hardball, Playing Offense vs. Playing Defense, Good and Bad Competitors
• Chapter 31: Failure…Failure and the Startup Model, Failure Is Not an Orphan

Part IV: Building and Leading a Board of Directors

• Chapter 32: The Value of a Good Board…Why Have a Board?, Everybody Needs a Boss, The Board as Forcing Function, Pattern Matching, Forests, Trees, Honest Discussion and Debate
• Chapter 33: Building Your Board…What Makes a Great Board Member?, Recruiting a Board Member, Compensating Your Board, Boards as Teams, Structuring Your Board, Board Size, Board Committees, Chairing the Board, Running a Board Feedback Process, Building an Advisory Board
• Chapter 34: Board Meeting Materials…“The Board Book”, Sample Return Path Board Book, The Value of Preparing for Board Meetings
• Chapter 35: Running Effective Board Meetings…Scheduling Board Meetings, Building a Forward-Looking Agenda, In-Meeting Materials, Protocol, Attendance and Seating, Device-Free Meetings, Executive and Closed Sessions
• Chapter 36: Non-Board Meeting Time…Ad Hoc Meetings, Pre-Meetings, Social Outings
• Chapter 37: Decision-Making and the Board…The Buck Stops—Where?, Making Difficult Decisions in Concert, Managing Conflict with Your Board
• Chapter 38: Working with the Board on Your Compensation and Review…The CEO’s Performance Review, Your Compensation, Incentive Pay, Equity, Expenses
• Chapter 39: Serving on Other Boards…The Basics of Serving on Other Boards, Substance, or Style?

Part V: Managing Yourself So You Can Manage Others

• Chapter 40: Creating a Personal Operating System…Managing Your Agenda, Managing Your Calendar, Managing Your Time, Feedback Loops
• Chapter 41: Working with an Executive Assistant…Finding an Executive Assistant, What an Executive Assistant Does
• Chapter 42: Working with a Coach…The Value of Executive Coaches, Areas Where an Executive Coach Can Help
• Chapter 43: The Importance of Peer Groups…The Gang of Six, Problem-Solving in Tandem
• Chapter 44: Staying Fresh…Managing the Highs and Lows, Staying Mentally Fresh, At Your Company, Out and About, Staying Healthy, Me Time
• Chapter 45: Your Family…Making Room for Home Life, Involving Family in Work, Bringing Work Principles Home
• Chapter 46: Traveling…Sealing the Deal with a Handshake, Making the Most of Travel Time, Staying Disciplined on the Road
• Chapter 47: Taking Stock of the Year…Celebrating “Yes”; Addressing “No”, Are You Having Fun?, Are You Learning and Growing as a Professional?, Is It Financially Rewarding?, Are You Making an Impact?
• Chapter 48:  A Note on Exits…Five Rules of Thumb for Successfully Selling Your Company

 If you’re still with me and interested, again here are the links to pre-order (Print, Kindle).

Book short:  Blink

Blink, by Malcolm Gladwell, is a must read for marketers, entrepreneurs, and VCs alike, just as is the case with Gladwell’s first book, The Tipping Point.

Where The Tipping Point theorizes about how humans relate to each other and how fads start and flourish in our society, Blink theorizes about how humans make decisions and about the interplay between the subconscious, learned expertise, and real-time inputs.  But Gladwell does more than theorize — he has plenty of real world examples which seem quite plausible, and he peppers the book with evidence from some (though hardly a complete coverage of relevant) scientific and quasi-scientific studies.

Blink for Entrepreneurs/CEOs:  What’s the most critical lesson in Malcolm Gladwell’s Blink, as it relates to entrepreneurs/CEOs?  It’s about bias in hiring.  Most of us make judgments about potential new hires quite quickly in the initial interview.  The symphony example in the book is the most painfully poignant — most major symphony orchestras hired extremely few women until they started conducting auditions behind a screen.  It’s not clear to me yet how to stop or even shrink hiring bias, but I suspect the answer lies in pre-interview work around defining specific criteria for the job and scoring all candidates on the same set of criteria.

Blink for VCs:  What’s the most critical lesson in Malcolm Gladwell’s Blink, as it relates to VCs?  It’s about picking companies to back.  Even VCs who are virtuosos, as Gladwell would call them, can make poor judgments on companies to back based on their own personal reaction to a company’s product or service, as opposed to the broader marketplace’s reaction.  Someone poured a whole lot of money into Webvan, Pets.com, eToys, and the like.

Blink for Marketers:  What’s the most critical lesson in Malcolm Gladwell’s Blink, as it relates to Marketers?  It’s the importance of multivariate regression testing.  No, really, I’m not kidding, although there’s no doubt a less math-y way of saying it — “test everything.”  The Coca-Cola Company thought they were doing the right thing in creating New Coke because they were losing the Pepsi Challenge.  But what they didn’t realize was that Pepsi (unintentionally or not) had suckered them into believing that the single-sip test was cause for reengineering a century of product, when in reality Coke was probably just being out-advertised.  Christian Brothers Brandy was going out of its mind losing market share to competitor E&J until someone realized that they just needed to change the shape of their bottle.

If you haven’t yet done so, go buy the book!  It’s a very quick read and incredibly thought provoking.  And if you haven’t yet read The Tipping Point, it’s a must as well.

Book Short:  Internet Fiction

It’s been a long time since I read Tom Evslin’s Hackoff.com, which Tom called a “blook” since he released it serially as a blog, then when it was all done, as a bound book.  Mariquita and I read it together and loved every minute of it.  One post I wrote about it at the time was entitled Like Fingernails on a Chalkboard.

The essence of that post was “I liked it, but the truth of the parts of the Internet bubble that I lived through were painful to read,” applies to two “new” works of Internet fiction that I just plowed through this week, as well.

Uncommon Stock

Eliot Pepper’s brand new startup thriller, Uncommon Stock, was a breezy and quick read that I enjoyed tremendously. It’s got just the right mix of reality and fantasy in it. For anyone in the tech startup world, it’s a must read. But it would be equally fun and enjoyable for anyone who likes a good juicy thriller.

Like my memory of Hackoff, the book has all kinds of startup details in it, like co-founder struggles and a great presentation of the angel investor vs. VC dilemma. But it also has a great crime/murder intrigue that is interrupted with the book’s untimely ending.  I eagerly await the second installment, promised for early 2015.

The Circle

While not quite as new, The Circle  has been on my list since it came out a few months back and since Brad’s enticing review of it noted that:

The Circle  was brilliant. I went back and read a little of the tech criticism and all I could think was things like “wow – hubris” or “that person could benefit from a little reflection on the word irony”… We’ve taken Peter Drucker’s famous quote “‘If you can’t measure it, you can’t manage it” to an absurd extreme in the tech business. We believe we’ve mastered operant conditioning through the use of visible metrics associated with actions individual users take. We’ve somehow elevated social media metrics to the same level as money in the context of self-worth.

So here’s the scoop on this book.  Picture Google, Twitter, Facebook, and a few other companies all rolled up into a single company.  Then picture everything that could go wrong with that company in terms of how it measures things, dominates information flow, and promotes social transparency in the name of a new world order.  This is Internet dystopia at its best – and it’s not more than a couple steps removed from where we are.  So fiction…but hardly science fiction.

The Circle  is a lot longer than Uncommon Stock and quite different, but both are enticing reads if you’re up for some internet fiction.

Book Short:  Innovation and Discipline

The Puritan Gift, by Kenneth and William Hopper, is a bit of a mixed bag.  The authors have a wonderful point to make — that American businesses have thrived over the centuries due to a mix of innovation and discipline that descended from the country’s Puritan roots, and that when they lose their way, it’s because they diverge from those roots.  The book is also an interesting, if somewhat cursory, history of American industry.  And it playfully debunks some great myths of corporate American life over the last 50 years.  But the book has a few too many moments where assertions aren’t supported by data — where its theories overreach into explanations of other aspects of American life that may or may not be appropriate.

That said, it is a good read.  The main point is that there are five driving principles behind American business success over the years, the first four coming from the Puritans and the fifth from the French:

– the melding of the workplace with the search for a higher purpose in life
– an aptitude for the application of mechanical skills
– the subordination of the individual to the group
– the ability to assemble and galvanize forces to a single purpose on a massive scale
– a keen interest in and passion for technology

These things ring true as driving forces of successful businesses today.  The distillation (or abstraction) of these forces, though, is the most powerful lesson from the book as far as I’m concerned, which is that businesses, and organizations in general, succeed the most when they are led by people who really understand the substance of the business and not by professional managers or financial engineers, and when they practice integrated decision-making, which is to say that the same people make decisions, plan for execution, execute, and follow up.  You don’t have to look too far to see a lot of examples of how the absence of domain expertise and integrated decision-making has led to spectacular failures, from Enron to Wall Street’s meltdown to the Iraq War.

The Puritan Gift ends on a hopeful note about restoring America’s leadership in global industry by returning to our Puritan roots.  It’s way too early to assess whether or not this hypothesis will turn out to be correct, but the examples the authors give in the concluding chapter are certainly good food for thought for anyone who runs a business.  Thanks to my friend Marc Maltz of Triad Consulting for the book.

Book Short:  Underdog Victorious

The Underdog Advantage, by David Morey and Scott Miller, was a worthwhile read, though not a great book.  It was a little shallow, and although I enjoyed its case studies (who doesn’t love hearing about Ben & Jerry’s, Southwest, JetBlue, Starbucks?), I didn’t feel like the authors did enough to tie the details of the success of the case study companies back to the points they made in the book.

That said, the book had some great reminders in it for companies of all sizes and stages.  The main point was that successful companies always think of themselves as the underdog, the insurgent, and never get complacent.  They run themselves like a political campaign, needing to win an election every single day.  A lot of the tactics suggested are timeless and good to remember…things like never declare victory, always play offense, always respond to attacks, remember to communicate from the inside out, and remember to sell employees on a mision and purpose in order to make them your main ambassadors.  The laundry list of tactics is the book’s greatest strength.