🔎
Apr 29 2008

Wither the News? (Plus a Bonus Book Short)

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.

Feb 19 2006

Book Short: Which Runs Faster, You or Your Company?

Book Short:  Which Runs Faster, You or Your Company?

Leading at the Speed of Growth, by Katherine Catlin at the Kauffman Center for Entrepreneurial Leadership is a must read for any entrepreneur or CEO of a growth company.  It’s one of the best books I’ve ever read targeted to that audience – its content is great, its format is a page-turner, and it’s concise and to the point.

The authors take you through three stages of a growth company’s lifestyle (Initial Growth, Rapid Growth, and Continuous Growth) and describe the “how to’s” of the transition into each stage:  how you know it’s coming, how to behave in the new stage, how to leave the old stage behind.

I didn’t realize it when I started reading the book, but Brad had one of the quotes on the back cover that says it all:  “There are business books about starting a company, but they tend to deal with the mechanics of business plans and financing.  Then there are books about ‘how to be the CEO of a Fortune 500 company.’  This is the first book I’ve seen that details the role of the CEO of a small but growing company.”  Thanks to my colleague George Bilbrey for pointing this one out to me.

UPDATE:  Brad corrects me and says that I should mention Jana Matthews, who co-wrote the book with Katherine Catlin and is actually the Kauffman Center person of the duo.

Feb 18 2008

Book Short: Tech Founder? Varsity Basketball Captain? Both! At the Same Time!

Book Short: Tech Founder? Varsity Basketball Captain? Both!  At the Same Time!

Ben Casnocha’s My Startup Life has some of the same appeal as The Mousedriver Chronicles (which I reviewed years go here) in its tale of a startup, its successes, failures, and lessons learned. If you like that kind of book or are starting a company and are looking for kindred spirits, it’s a good book for you.

Ben’s story is more remarkable in some ways because he started his eGovernment software (SaaS of course) company Comcate at the age of 13. That’s right, 13. When I was learning how to shave, having a bar mitzvah, and dealing with acne and a voice dropping at terminal velocity. Starting a business was the furthest thing from my mind. Though to be fair, teenage entrepreneurs are a featured new demographic in Mark Penn’s Microtrends (also worth a read). Perhaps if I were Ben’s age today, I would be a startup junkie, too.

I’ve had the pleasure of meeting Ben a couple times via Brad — I think Brad MUST have been a lot like him 20ish years ago. The advice in the book is good and relevant and incredibly mature for a 20-year old, and Ben, I mean that in an impressed way, not a patronizing one. It’s not necessarily revolutionary, but it’s a very quick and light read if you like the genre/premise.

Apr 22 2009

Book Short: Wither the Team

Book Short:  Wither the Team

I keep expecting one of his books to be repetitive or boring, but Patrick Lencioni’s The Five Dysfunctions of a Team held my interest all the way through, as did his others.  It builds nicely on the last one I read, Death by Meeting (post, link).

I’d say that over the 9 1/2 years we’ve been in business at Return Path, we’ve systematically improved the quality of our management team.  Sometimes that’s because we’ve added or changed people, but mostly it’s because we’ve been deliberate about improving the way in which we work together.  This particular book has a nice framework for spotting troubles on a team, and it both reassured me that we have done a nice job stamping out at least three of the dysfunctions in the model and fired me up that we still have some work to do to completely stamp out the final two (we’ve identified them and made progress, but we’re not quite there yet.

The dysfunctions make much more sense in context, but they are (in descending order of importance):

  • Absence of trust
  • Fear of conflict (everyone plays politically nice)
  • Lack of commitment (decisions don’t stick)
  • Avoidance of accountability
  • Inattention to results (individual ego vs. team success)

For those who are wondering, the two we’re still working on at the exec team level here are conflict and commitment.  And the two are related.  If you don’t produce engaged discussion about an issue and allow everyone to air their opinions, they will invariably be less bought into a decision (especially one they don’t agree with).  But we’re getting there and will continue to work aggressively on it until we’ve rooted it out.

There’s one other interesting takeaway from the book that’s not part of the framework directly, which is that an executive has to be first and foremost a member of his/her team of peers, not the head of his/her department.  That’s how successful teams get built.  AND (this is key) this must trickle down in the organization as well.  Everyone who manages a team of group heads or managers needs to make those people function well as a team first, then as managers of their own groups second.

At any rate, another quick gem of a book.  I’m kind of sorry there’s only one left in the series.

So far the series includes:

I have one or two more to go, which I’ll tackle in due course and am looking forward to.

Jan 27 2008

Book Short: A Must Read

Book Short:  A Must Read

Every once in a while, I read a book and think, “This is an important book.”  Microtrends, by Mark Penn, was just that kind of read.  Penn is the CEO of one of our largest clients in the market research business as well as CEO of Burson Marstellar and, more notably, the Clintons’ pollster and strategy director for much of the last 16 years.  He’s a smart guy, and more important than that, he’s awash in primary research data.

The premise of Microtrends is that America is no longer a melting pot, where lots of different people come together to try to be the same, but rather that it’s a big tent, where lots of small groups are now large enough to express their individuality powerfully.  The book is also perfect for the ADD-afflicted among us, with 75 chapters each of about 4 pages in length describing one new “microtrend” or small faction of American identity.  Penn not only describes the trend in a data-rich way but then goes on to postulate about the impact that trend will have on society at large and/or on the business opportunities that could come from serving those in the trend.

Just to give you a sample of the trends he covers:  Sex-ratio singles (explaining why there really are more single women than men), Extreme commuters (we certainly have a couple of those at Return Path),
Pro-Semites vs. Christian Zionists (they sound the same but are completely different), Newly-released Ex-cons (hint – there are a ton of them), and the rise of Chinese artists.

Whether you’re interested in marketing, entrepreneurship (you’ll get loads of ideas here), investing (more loads of ideas), or just trends in American and global society, Microtrends is a must must must read.  All 75 chapters were interesting to me, but even if you don’t love some…they’re only 4 pages each!

Oct 31 2005

Book Short: Reality Doesn’t have to Bite

Book Short:  Reality Doesn’t have to Bite

I just read Confronting Reality (book; audio), the sequel to Execution, by Larry Bossidy and Ram Charan.  Except I didn’t read it, I listened to it on Mariquita’s iPod Shuffle over the course of two or three long runs in the past week.  The book was good enough, but I also learned two valuable lessons.  Lesson 1:  Listening to audio books when running is difficult – it’s hard to focus enough, easy to lose one’s place, can’t refer back to anything or take notes.  Lesson 2:  If you sweat enough on your spouse’s Shuffle, you can end up owning a Shuffle of your own.

Anyway, I was able to focus on the book enough to know that it’s a good one.  It’s chock full of case studies from the last few years, including some “new economy” ones instead of just the industrial types covered in books like Built to Last and Good to Great.  Cisco, Sun, EMC, and Thomson are all among those covered.  The basic message is that you really have to dig into external market realities when crafting a strategic plan or business model and make sure they’re in alignment with your financial targets as well as people and processes.  But the devil’s in the details, and the case studies here are great.

Sep 9 2011

9/11’s 10th

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.

Mar 18 2021

The Tension That Will Come With the Future of Work

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:

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.

Apr 10 2014

Understanding the Drivers of Success

Understanding the Drivers of Success

Although generally business is great at Return Path  and by almost any standard in the world has been consistently strong over the years, as everyone internally knows, the second part of 2012 and most of 2013 were not our finest years/quarters.  We had a number of challenges scaling our business, many of which have since been addressed and improved significantly.

When I step back and reflect on “what went wrong” in the quarters where we came up short of our own expectations, I can come up with lots of specific answers around finer points of execution, and even a few abstracted ones around our industry, solutions, team, and processes.  But one interesting answer I came up with recently was that the reason we faltered a bit was that we didn’t clearly understand the drivers of success in our business in the 1-2 years prior to things getting tough.  And when I reflect back on our entire 14+ year history, I think that pattern has repeated itself a few times, so I’m going to conclude there’s something to it.

What does that mean?  Well, a rising tide — success in your company — papers over a lot of challenges in the business, things that probably aren’t working well that you ignore because the general trend, numbers, and success are there.  Similarly, a falling tide — when the going gets a little tough for you — quickly reveals the cracks in the foundation.

In our case, I think that while some of our success in 2010 and 2011 was due to our product, service, team, etc. — there were two other key drivers.  One was the massive growth in social media and daily deal sites (huge users of email), which led to more rapid customer acquisition and more rapid customer expansion coupled with less customer churn.  The second was the fact that the email filtering environment was undergoing a change, especially at Gmail and Yahoo, which caused more problems and disruption for our clients’ email programs than usual — the sweet spot of our solution.

While of course you always want to make hay while the sun shines, in both of these cases, a more careful analysis, even WHILE WE WERE MAKING HAY, would have led us to the conclusion that both of those trends were not only potentially short-term, but that the end of the trend could be a double negative — both the end of a specific positive (lots of new customers, lots more market need), and the beginning of a BROADER negative (more customer churn, reduced market need).

What are we going to do about this?  I am going to more consistently apply one of our learning principles, the Post-Mortem  –THE ART OF THE POST-MORTEM, to more general business performance issues instead of specific activities or incidents.  But more important, I am going to make sure we do that when things are going well…not just when the going gets tough.

What are the drivers of success in your business?  What would happen if they shifted tomorrow?

Apr 4 2020

State of Colorado COVID-19 Innovation Response Team, Part VI – How This Compared to Running a Company

(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…

Feb 14 2020

The Beginnings of a Roadmap to Fix America’s Badly Broken Political System, part II

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.