🔎
Oct 20 2005

links for 2005-10-20

  • Get your mind out of the gutter! These are very useful and oddly hard to find graphics for doing checklists in presentations (thanks to my colleague George Bilbrey for this link).
    (tags: Graphics)
Aug 19 2005

links for 2005-08-19

Sep 22 2005

links for 2005-09-22

Oct 11 2005

links for 2005-10-11

Nov 25 2005

links for 2005-11-26

Oct 22 2005

links for 2005-10-22

  • From our client, Business & Legal Reports, a HILARIOUS read in the strange-but-true category. This is essential reading for any manager who has ever mediated an employee dispute. Tthanks to Tami Forman for citing this one!
    (tags: Humor)
Oct 23 2005

links for 2005-10-23

Dec 5 2005

links for 2005-12-06

Jun 2 2022

Book Short: New to the Canon of Great CEO Books

Please go put Decide and Conquer: 44 Decisions that will Make or Break All Leaders by David Siegel on your reading list, or buy it. David’s book is up there on my list with Ben Horowitz’s The Hard Thing About Hard Things. It’s a totally different kind of book than Startup CEO, and in some ways a much better one in that there’s a great through-line or storyline, as David shares his leadership framework in the context of his journey of getting hired to replace founder Scott Heiferman as Meetup’s CEO after its acquisition by WeWork, including some juicy interactions with Adam Neumann, through the trials and tribulations of WeWork as a parent company, through COVID and its impact on an in-person meeting facilitator like Meetup, through to the sale of Meetup OUT of WeWork.

It’s hard to do the book justice with a quick write up. It’s incredibly concise. It’s clear. It’s witty. Most of all, it’s very human, and David shares a very human, common sense approach to leadership. I particularly like a device he uses to reinforce his main points and principles by bolding the key phrases every time they show up in the book: be kind, be confident, be bold, expand your options, focus on the long-term picture, be pragmatic, be honest, be speedy, do what’s right for the business, work for your people and they’ll work for you, be surprised only about being surprised. These all resonate with me so much.

One of the interesting things about the book is that David is a CEO, but not a founder (although he was sort of a re-founder in this case). A lot of CEO books talk about how to run a company, or give stories from the trials and tribulations thereof, but few focus on the elements of interviewing for the CEO job, or taking over the reins of a company in the midst of a turbulent flight. So the book is about getting the job, starting the job, doing a turnaround, leading a company through growth, a buy-out, and managing a company inside of another company. And because Meetup is such an iconic brand and business, it’s easy to understand a lot of the backdrop to David’s story.

I just met David for the first time a few weeks ago. We knew a bunch of people in common from his DoubleClick days. We instantly hit it off and traded copies of our books, and then were reading them at the same time trading emails about the parts that clicked. I just can’t recommend the book enough to any CEO or founder. In my view, it joins a pretty elite canon.

May 8 2014

Book Short: Like Reading a Good Speech

Book Short:  Like Reading a Good Speech

Leaders Eat Last, by Simon Sinek, is a self-described “polemic” that reads like some of the author’s famous TED talks and other speeches in that it’s punchy, full of interesting stories, has some attempted basis in scientific fact like Gladwell, and wanders around a bit.  That said, I enjoyed the book, and it hit on a number of themes in which I am a big believer – and it extended and shaped my view on a couple of them.

Sinek’s central concept in the book is the Circle of Safety, which is his way of saying that when people feel safe, they are at their best and healthiest.  Applied to workplaces, this isn’t far off from Lencioni’s concept of the trust foundational layer in his outstanding book, Five Dysfunctions of a Team.  His stories and examples about the kinds of things that create a Circle of Safety at work (and the kinds of things that destroy them) were very poignant.  Some of his points about how leaders set the tone and “eat last,” both literally and figuratively, are solid.  But his most interesting vignettes are the ones about how spending time face-to-face in person with people as opposed to virtually are incredibly important aspects of creating trust and bringing humanity to leadership.

My favorite one-liner from the book, which builds on the above point and extends it to a corporate philosophy of people first, customer second, shareholders third (which I have espoused at Return Path for almost 15 years now) is

Customers will never love a company unless employees love it first.

A couple of Sinek’s speeches that are worth watching are the one based on this book, also called Leaders Eat Last, and a much shorter one called How Great Leaders Inspire Action.

Bottom line:  this is a rambly book, but the nuggets of wisdom in it are probably worth the exercise of having to find them and figure out how to connect them (or not connect them).

Thanks to my fellow NYC CEO Seth Besmertnik for giving me this book as well as the links to Sinek’s speeches.

Jun 5 2014

Book short: Life Isn’t Just a Wiki

Book short:  Life Isn’t Just a Wiki

One of the best things I can say about Remote: Office Not Required,  by Jason Fried and David Heinemeier Hansson, is that it was short.  That sounds a little harsh – part of what I mean is that business books are usually WAY TOO LONG to make their point, and this one was blessedly short.  But the book was also a little bit of an angry rant against bad management wrapped inside some otherwise good points about remote management.

The book was a particularly interesting read juxtaposed against Simon Sinek’s Leaders Eat Last which I just finished recently and blogged about here, which stressed the importance of face-to-face and in-person contact in order for leaders to most effectively do their jobs and stay in touch with the needs of their organizations.

The authors of Remote, who run a relatively small (and really good) engineering-oriented company, have a bit of an extreme point of view that has worked really well for their company but which, at best, needs to be adapted for companies of other sizes, other employee types, and other cultures.  That said, the flip side of their views, which is the “everyone must be at their cubicle from 9 to 5 each day,” is even dumber for most businesses these days.  As usual with these things, the right answer is probably somewhere in between the extremes, and I was reminded of the African proverb, “If you want to go fast, go alone. If you want to go farm go together” when I read it.  Different target outcomes, different paths.

I totally agree with the authors around their comments about trusting employees and “the work is what matters.”  And we have a ton of flexibility in our work at Return Path.  With 400 people in the company, I personally spend six weeks over the summer working largely remote, and I value that time quite a bit.  But I couldn’t do it all the time.  We humans learn from each other better and treat each other better when we look at each other face to face.  That’s why, with the amount of remote work we do, we strongly encourage the use of any form of video conferencing at all times.  The importance of what the authors dismiss as “the last 1 or 2% of high fidelity” quality to the conversation is critical.  Being in person is not just about firing and hiring and occasional sync up, it’s about managing performance and building relationships.

Remote might have been better if the authors had stressed the value that they get out of their approach more than ranting against the approaches of others.  While there are serious benefits of remote work in terms of cost and individual productivity (particularly in maker roles), there are serious penalties to too much of it as well in terms of travel, communication burden, misunderstandings, and isolation.  It’s not for everyone.

Thanks to my colleague Hoon Park for recommending this to me.  When I asked Hoon what his main takeaway from the book was, he replied:

The importance of open communication that is archived (thus searchable), accessible (transparent and open to others) and asynchronous (doesn’t require people to be in the same place or even the same “timespace”).  I love the asynchronous communication that the teams in Austin have tried: chatrooms, email lists (that anyone can subscribe to or read the archives of), SaaS project management tools. Others I would love to try or take more advantage of include internal blogs (specifically the P2 and upcoming O2 WordPress themes; http://ma.tt/2009/05/how-p2-changed-automattic/), GitHub pull requests (even for non-code) and a simple wiki.

These are great points, and good examples of the kinds of systems and processes you need to have in place to facilitate high quality, high volume remote work.