🔎
Jun 9 2022

Open All-Hands Meetings

I love stealing/borrowing other people’s good ideas for management and leadership when they’re made public, and I always encourage others to do so from me. I call it “plagiarizing with pride.” So I was intrigued when I saw a new way of doing all-hands meetings published by my friend Daniel Odio (DROdio) on his founder community called FounderCulture. You can see the original post here.

We’ve experimented with different formats and cadences for all-hands meetings over the years. They tend to vary with the size of the company and complexity of the material to cover. Larger companies usually fall into the rhythm of doing quarterly all-hands meetings sometime after the end of the quarter, usually around a Board meeting, with a quarterly recap and forecast for next quarter.

But for early stage companies, there’s no tried-and-true method. We struggled with that for a while at Bolster. Weekly felt too much. Quarterly felt like too little. It seemed weird for me or my co-founders to just have a meeting where we talked at everyone…and it also seemed weird to just host an “open mic night” type meeting. Then I saw DROdio’s video, and we adapted it. It’s working pretty well for us. Here’s what we do in what we’re calling our Open All-Hands Meeting:

  • We hold an all-hands meeting every Monday for :30
  • A different team member is responsible for being the host/chair/emcee for each meeting
  • We run the meeting off of a dedicated Trello board with specific columns of information. Everyone is invited to contribute to the Trello board in the days leading up to the meeting. The columns are:
    • Values-Kudos-Good News: Anyone can call out anyone for doing something that demonstrates one of the company’s values, that is just a big thank you, or that is some other piece of karmic goodness they want to share
    • Wins: All client wins are shown here with some detail, each in its own card with its owner highlighted
    • #MAD: This is where we trade items on which we Made A Decision during the prior week, big or small. We’ve always struggled with the best way to keep everyone informed on things like this…and this works really well for that purpose
    • Learnings/Product Ideas: Anyone can populate this with anything they want as they go about their work and either come across learnings or product ideas they want to share
    • Announcements: Pretty self-explanatory, any corporate announcement, new employee introductions, etc.
    • Swim Lane Updates: Each we, we ask one or two of our functional or project areas to do a deep dive update — Product, Finance, Sales, Marketing, Ops, etc. — and this is also where we’ll do product demos of newly released functionality
    • Permanent Items: this isn’t a column that’s read…it just warehouses things we want on the board like the schedule of hosts, schedule of swim lane updates, instructions for running the meeting, recordings of prior meetings
    • BOLSTER 2022: this isn’t a column that’s read…it contains our mission, values, strategy, and key strategic initiatives and metrics for the year
    • Archive: this isn’t a column that’s read…it just contains the prior week’s items
  • There’s a series of light integrations between Slack, Hubspot, and Trello to automatically populate Trello based on certain channels, keywords, and emojis. Every week, the board is automatically wiped clean after the meeting
  • The host moves the meeting from column to column and card to card, sometimes reading the cards, and sometimes asking the person who submitted the card to read it or give color commentary on it
  • I do jump in from time to time, as do some of my co-founders or our other leaders, to give extra commentary or amplify something or help connect the dots. But that’s about as formal as my role gets other than…
  • …when we do have a quarterly board book and board meeting, I host that one meeting and recap the meeting, ask other leaders to comment on specific topics, and facilitate Q&A on the materials we send out ahead of time. So I’m hosting 4 meetings per year
  • The host can add a personal touch to any meeting. Custom wallpaper for the Trello board. Asking everyone in the company who has a pet to send in a photo of the pet ahead of time and introducing their furry friends during the meeting. Playing intro or outro music to fit the occasion. Doing spot surveys or game show questions to keep things lively. Interviewing new team members. Asking everyone to do a one-sentence “here’s what I’m working on this week” at the end of the meeting
  • Finally, the host passes the baton from one person to the next each week. No one can escape this responsibility!

In addition to the Open All-Hands Meeting format, I send the company an email every Friday with some musings on the prior week. The content of these varies widely – from “what I did last week,” to “here’s something I saw that’s interesting,” to welcoming new team members with their bios, to customer testimonials. Sometimes other founders write these. They’re a good way to add a personal touch to the operating system of the company — and we also send these to our board and major shareholders every week so they, too, can keep a finger on the pulse.

These two things together are proving to be a good Operating System for keeping everyone informed, aligned, and connected on a weekly basis.

May 16 2011

Pret a Manager

Pret a Manager

My friend James is the GM of the Pret a Manger (a chain of about 250 “everyday luxury” quick service restaurants in the UK and US) at 36th and 5th in Manhattan.  James recently won the President’s Award at Pret for doing an outstanding job opening up a new restaurant.  As part of my ongoing effort to learn and grow as a manager, I thought it would be interesting to spend a day shadowing James and seeing what his operation and management style looked like for a team of two dozen colleagues in a completely different environment than Return Path.  That day was today.  I’ll try to write up the day as combination of observations and learnings applied to our business.  This will be a much longer post than usual.  The title of this post is not a typo – James is “ready to manage.”

1. Team meeting.  The day started at 6:45 a.m. pre-opening with a “team brief” meeting.  The meeting only included half a dozen colleagues who were on hand for the opening, it was a mix of fun and serious, and it ended with three succinct points to remember for the day.  I haven’t done a daily huddle with my team in years, but we do daily stand-ups all across the company in different teams.  The interesting learning, though, is that James leaves the meeting and writes the three points on a whiteboard downstairs near the staff room.  All staff members who come in after the meeting are expected to read the board and internalize the three points (even though they missed the meeting) and are quizzed on them spontaneously during the day.  Key learning:  missing a meeting doesn’t have to mean missing the content of the meeting.

2. Individual 1:1 meeting.  I saw one of these, and it was a mix of a performance review and a development planning session.  It was a little more one-way in communication than ours are, but it did end up having a bunch of back-and-forth.  James’s approach to management is a lot of informal feedback “in the moment,” so this formal check-in contained no surprises for the employee.  The environment was a little challenging for the meeting, since it was in the restaurant (there’s no closed office, and all meetings are done on-site).  The centerpiece of the meeting was a “Start-Stop-Continue” form.  Key learning:  Start-Stop-Continue is a good succinct check-in format.

3. Importance of values.  There were two forms of this that I saw today.  One was a list of 13 key behaviors with an explanation next to each of specific good and bad examples of the behavior.  The behaviors were very clear and were “escalating,” meaning Team Members were expected to practice the first 5-6 of them, Team Leads the first 7-8, Managers the first 10, Head Office staff the first 12, Executives all 13 (roughly).  The second was this “Pret Recipe,” as posted on the public message board (see picture below).  Note – just like our values at Return Path, it all starts with the employee.  One interesting nugget I got from speaking to a relatively new employee who had just joined at the entry level after being recruited from a prominent fast food chain where he had been a store general manager was “Pret really believes this stuff — no lip service.”

I saw the values in action in two different ways.  The first was on the message board, where each element of the Pret Recipe was broken out with a list of supporting documents below it, per the below photo.  Very visual, very clear.

The second was that in James’s team meeting and in his 1:1 meeting, he consistently referenced the behaviors.  Key learning:  having values is great, making them come to life and be relevant for a team day-in, day-out is a lot harder but quite powerful when you get it right.

4. Managing by checklist.  I wrote about this topic a while ago here, but there is nothing like food service retail to demand this kind of attention to detail.  Wow.  They have checklists and standards for everything.  Adherence to standards is what keeps the place humming.  Key learning:  it feels like we have ~1% of the documentation of job processes that Pret does, and I’m thinking that as we get bigger and have people in more and more locations doing the same job, a little more documentation is probably in order to ensure consistency of delivery.

5. Extreme team-based and individual incentive compensation.  Team members start at $9/hour (22% above minimum wage that most competitors offer).  However, any week in which any individual store passes a Mystery Shopper test, the entire staff receives an incremental $2/hour for the whole week.  Any particular employee who is called out for outstanding service during a Mystery Shop receives a $100 bonus, or a $200 bonus if the store also passes the test.  The way the math works out, an entry level employee who gets the maximum bonus earns a 100% bonus for that week.  But the extra $2/hour per team member for a week seemed to be a powerful incentive across the board.  Key learning: team-based incentive comp is something we use here for executives, but maybe it’s worth considering for other teams as well.

6. Integrated systems.  Pret has basically one single software system that runs the whole business from inventory to labor scheduling to finances.  All data flows through it directly from point of sale or via manager single-entry.  All reports are available on demand.  The system is pretty slick.  There doesn’t seem to be much use of side systems and side spreadsheets, though I’m sure there are some.  Key learning: there’s a lot to be said for having a little more information standardized across the business, though the flip side is that this system is a single point of failure and also much less flexible than what we have.

7. Think time.  I’ve written a little about working “on the business, not in the business,” or what I call OTB time, once before, and I have another post queued up for later this summer about the same.  Brad Feld also very kindly wrote about it in reference to Return Path last week.  Working in retail means that time to work on IMPORTANT BUT NOT URGENT issues is extremely hard to come by and fragmented.  I suspect that it comes more at the end of the day for James, and it probably comes a lot more when he doesn’t have someone like me observing him and asking him questions.  But his “office” (below), exposed to the loud music and sounds and smells of the kitchen, certainly doesn’t lend itself to think time!  Key learning:  of course customers come first, but boy is it critical to make space to work OTB, not just ITB.  Oh, and James needs a new chair that’s more ergonomically compatible with his high countertop desk.

Years ago, I spent a few weekends working in my cousin Michael’s wine store in Hudson, NY, and I wrote up the experience in two different posts on this blog, the first one about the similarities between running a 2-person company and a 200-person company, and the second one about how in a small business, you have to wear one of every kind of hat there is.  My conclusion then was that there are more similarities than differences when it comes to running businesses of different types.  My conclusion from today is exactly the same, though the focus on management made for a very different experience.

Thanks to James, Gustavo, Orlanda, Shawona, and the rest of the team at the 36th & 5th Pret for putting up with the distraction of me for the bulk of the day today — I learned a lot (and particularly enjoyed the NYC Meatball Hot Wrap) and now have to figure out how to return the favor to you!

Jun 19 2008

Run, Brad, Run!

Run, Brad, Run!

A few years ago we announced our support of a charity called the Accelerated Cure Project for Multiple Sclerosis (see the post about it here and learn more about Accelerated Cure here).  While we have a strong culture of giving back to the community at Return Path and do that in several ways, we chose this charity as the main beneficiary of our corporate philanthropy efforts for three reasons:

  1. We wanted to support research into finding a cure for MS to honor and support one of our earliest colleagues, Sophie Miller Audette who was diagnosed with MS about 5 years ago (and is still going strong as one of our key sales directors!) – and since then, two other members of the Return Path extended family have also been diagnosed with MS
  2. We wanted to support an organization with a focused mission and one where our contributions could really make a difference
  3. Accelerated Cure has a very entrepreneurial, innovative culture that’s consistent with our own – and a solution-oriented approach to their cause that resonates with our business philosophy

We got introduced to Accelerated Cure by Brad Feld, one of Return Path’s venture investors, who is a friend of Art Mellor, Accelerated Cure’s founder and CEO.  Brad’s an interesting guy for many reasons, but one reason is that he has a goal of running 50 marathons (one in each state) by the time he’s 50.  He has eight years and 40 marathons to go, and to make it a little more significant he decided to try and drum up some sponsorships for his quest and donate the money to Accelerated Cure. 

Return Path has decided to be one of Brad’s anchor tenant sponsors by pledging $1,000 for every race he completes.  This is half of Brad’s goal of $2,000 per race, and we hope it will inspire others to donate so he can beat his goal.  Of course, Brad wants to do more than just run these marathons – he wants to, well, accelerate his performance.  So, taking a page out of the VC handbook, we’re setting up an incentive program for Brad of an additional $500 donation for every race that he completes in less than four hours. 

Besides liking both Brad and Accelerated Cure, this particular vehicle for donating money is especially meaningful to us.  A good number of Return Path employees past and present have run marathons and even competed in triathlons and Ironman competitions (including yours truly, but in a way that certainly makes me want to keep my day job).  And Seth Matheson, Accelerated Cure’s new development director who has MS, is an avid marathoner who is contemplating an Ironman competition himself.  And as I always tell our team members, running a startup is a marathon, not a sprint!

You can follow Brad’s progress – and make a donation yourself – here.

Sep 29 2004

Comment on Political versus Corporate Leadership, Part II: Admitting Mistakes

Comment on Political versus Corporate Leadership, Part II: Admitting Mistakes

My colleague Mike Mayor writes:

So you’e only asking for politicians to be honest Matt? Is that all? 🙂

Couldn’t agree more on the CEO side. A CEO who cannot admit to failure is doomed to be surrounded by “yes men” and, therefore, must go it alone, whereas the CEO who admits to having the odd bad idea every now and then is more likely to get truthful and accuruate information from those around him/her. Which scenario would you prefer to base your next decision on?

However, I look more to Hollywood for fostering the faux CEO/Board Room stereotypes, not politics. Look no further than the highest ranked show among 18 to 46 year olds: The Apprentice. Trump is just one contemporary example of successfully perpetuating the “kill or be killed” mentality of the ideal CEO. In his book, “How to Get Rich” one of his lessons is to “never take the blame for anything” (meanwhile Trump gets rich by being a caricature of a CEO).

The ideal CEO needs to set the example for the behavior of his employees, and creates opportunities by building relationships not “squashing the competition.” And like it or not, the ideal Board Room is actually a Think Tank of great minds working toward a common goal rather than a place to play mind games and mental poker.

Unfortunately, both of these things make for a horrible TV show but do contribute to building truly great companies! On the other hand, watch too many TV shows (or follow the politician’s lead) and you’ll likely become a CEO whose success is comparable to the CEOs of Enron and Tyco.

Jul 6 2005

Book short: Blink

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.

Mar 20 2014

Secrets to Yawn-Free Board Meetings

Secrets to Yawn-Free Board Meetings

[This post first appeared as an article in Entrepreneur Magazine as part of a new series I’m publishing there in conjunction with my book, Startup CEO:  A Field Guide to Scaling Up Your Business]

The objective of board meetings should always be to have great conversations that help you and your executive team think clearly about the issues in front of you, as well as making sure your directors have a clear and transparent view of the state of the business. These conversations come from a team dynamic that encourages productive conflict. There’s no sure-fire formula for achieving this level of engagement, but here are three few guidelines you can follow to increase your chances.

Schedule board meetings in advance, and forge a schedule that works. Nothing is more disruptive – or more likely to drive low turnout – than last minute scheduling. Make sure you, or your executive assistant, knows board members’ general schedules and travel requirements, and whether they manage their own calendar or have their own executive assistant. Set your board meeting schedule for the year in the early fall, which is typically when people are mapping out most of their year’s major activities. If you know that one of your board members has to travel for your meetings, work with the CEOs of the other companies to coordinate meeting dates. Vary the location of meetings if you have directors in multiple geographies so travel is a shared sacrifice.

In the startup stage of our business at Return Path, we ran monthly meetings for an hour, mostly call-in. In the revenue stage, we moved to six to eight meetings per year, two hours in length, perhaps supplemented with two longer-form and in-person meetings. As a growth stage company, we run quarterly meetings. They’re all in-person, meaning every director is expected to travel to every meeting. We probably lose one director each time to a call-in or a no-show for some unavoidable conflict, but, for the most part, everyone is present. We leave four hours for every meeting (it’s almost impossible to get everything done in less time than that) and sometimes we need longer.

Many years, we also hold a board offsite, which is a meeting that runs across 24 hours, usually an afternoon, a dinner, and a morning, and is geared to recapping the prior year and planning out the next year together. It’s especially exhausting to do these meetings, and I’m sure it’s especially exhausting to attend them, but they’re well worth it. The intensity of the sessions, discussion, and even social time in between meetings is great for everyone to get on the same page and remember what’s working, what’s not, and what the world around us looks like as we dive into the deep end for another year.

Build a forward-looking agenda. The second step in having great board meetings is to set an agenda that will prompt the discussion that you want to have. With our current four-hour meetings, our time allocation is the following:

I. Welcomes and framing (5 minutes)

II. Official Business (no more than 15 minutes unless something big is going on)

III. Retrospective (45 minutes)

a. Target a short discussion on highlighted issues

b. Leave some time for Q&A

IV. On My Mind (2 hours)

a. You can spend this entire time on one topic, more than one, or all, as needed.

b. Format for discussions can vary—this is a good opportunity for breakout sessions, for example.

V. Executive Session (30 minutes)

This is your time with directors only, no observers or members of the management team (even if they are board members).

VI. Closed Session (30 minutes)

This is director-only time, without you or anyone else from the management team.

This agenda format focuses your meeting on the future, not the past. In the early years of the business, our board meetings were probably 75 percent “looking backwards” and 25 percent “looking forwards.” They were reporting meetings—reports which were largely in the hands of board members before the meetings anyway. They were dull as anything, and they were redundant: all of our board members were capable of processing historical information on their own. Today, our meetings are probably ten percent “looking backwards” and 90 percent “looking forwards”—and much more interesting as a result.

Separate background reading and presentation materials. Finally, focus on creating a more engaging dialogue during the meeting by separating background reading from presentation materials. In our early days, we created a huge Powerpoint deck as both a handout the week before the meeting and as the in-meeting deck. That didn’t create an engaging meeting.

There’s nothing more mind-numbing than a board meeting where the advance reading materials are lengthy Powerpoint presentations, than when the meeting itself is a series of team members standing up and going through the same slides, bullet by excruciating bullet—that attendees could read on their own.

When we separated the background and presentation materials, people were engaged by the Powerpoint—because it delivered fresh content. We started making the decks fun and engaging and colorful, as opposed to simple text and bullet slides. That was a step in the right direction, but the preparation consumed twice as much time for the management team, and we certainly didn’t get twice the value from it.

Now we send out a great set of comprehensive reading materials and reports ahead of the meeting, and then we have a completely Powerpoint-free meeting. No slides on the wall. This changes the paradigm away from a presentation—the whole concept of “management presenting to the board”—to an actual discussion. No checking email. No yawns. Nobody nodding off. Everyone—management and board—is highly engaged

Jan 18 2018

Book Short – Another Must-Read by Lencioni

Book Short – Another Must-Read by Lencioni

The Ideal Team Player: How to Recognize and Cultivate The Three Essential Virtues (hardcover,kindle is Patrick Lencioni’s latest and greatest.  It’s not my favorite of his, which is still The Advantage (post,buy ), but it’s pretty good and well worth a read.  It builds on his model for accountability in The Five Dysfunctions of a Team (post,buy)and brings it back to “how can you spot or develop and a good team player?”

The central thesis of the book is that great team players have three attributes – hungry, humble, and people-smart.  While I can’t disagree with those three things, as with all consultants’ frameworks, I sound two cautionary notes:  (1) they aren’t the absolute truth, just a truth, and (2) different organizations and different cultures sometimes thrive with different recipes.  That said, certainly for my company, this framework rings true, if not the only truth.

Some great nuggets from the book:

-The basketball coach who says he loves kids who want to come to practice and work as hard as they can at practice to avoid losing
-The concept of Addition by Addition and Addition by Subtraction in the same book – both are real and true.  The notion that three people can get more done than four if the fourth is a problem is VERY REAL
-When you’re desperate for people, you do stupid things – you bring people on who can get the job done but shouldn’t be in your environment.  I don’t know a single CEO who hasn’t made this mistake, even knowing sometimes that they’re in the process of making it

The framing of the “edge” people – people who have two of the three virtues, but not the third, is quite good:

-Hungry and Humble but not People-Smart – The Accidental Mess Maker
-Humble and People-Smart, but not Hungry – The Lovable Slacker
-Hungry and People-Smart, but not Humble – The Skillful Politician

In my experience, and Lencioni may say this in the book, too (I can’t remember and can’t find it), none of these is great…but the last one is by far the most problematic for a culture that values teamwork and collaboration.

Anyway, I realize this is a long summary for a short book, but it’s worth buying and reading and having on your (real or virtual) shelf.  In addition to the story, there are some REALLY GOOD interview guides/questions and team surveys in the back of the book.

Oct 1 2004

Political versus Corporate Leadership, Part III: The First Debate

Political versus Corporate Leadership, Part III: The First Debate

Well, there you have it. Both of my first two postings on this subject — Realism vs. Idealism and Admitting Mistakes — came up in last night’s debate.

At one point, in response to Kerry’s attempted criticism of him for expressing two different views on the situation in Iraq, Bush responded that he thought he could — and had to — be simultaneously a realist and an optimist. And a few minutes later, Kerry admitted a mistake and brilliantly turned the tables on Bush by saying something to the effect of “I made a mistake in how I talked about Iraq, and he made a mistake by taking us to war with Iraq — you decide which is worse.”

So each candidate exhibited at least one of the traits of good corporate leadership, but on this front anyway, I think Kerry did a better job last night in turning one of his mistakes into a zinger against his opponent.

Jul 9 2010

Book Short: Multiplying Your Team’s Productivity

Book Short:  Multiplying Your Team’s Productivity

No matter how frustrated a kids’ soccer coach gets, he never, ever runs onto the field in the middle of a game to step in and play.  It’s not just against the rules, it isn’t his or her role.

Multipliers: How the Best Leaders Make Everyone Smarter by Liz Wiseman and Greg McKeown (book, Kindle) takes this concept and drives it home.  The book was a great read, one of the better business books I’ve read in a long time.  I read a preview of it via an article in a recent Harvard Business Review (walled garden alert – you can only get the first page of the article without buying it), then my colleague George Bilbrey got the book and suggested I read it.  George also has a good post up on his blog about it.

One of the things I love about the book is that unlike a lot of business books, it applies to big companies and small companies with equal relevance.  The book echoes a lot of other contemporary literature on leadership (Collins, Charan, Welch) but pulls it into a more accessible framework based on a more direct form of impact:  not long-term shareholder value, but staff productivity and intelligence.  The book’s thesis is that the best managers get more than 2x out of their people than the average – some of that comes from having people more motivated and stretching, but some comes from literally making people more intelligent by challenging them, investing in them, and leaving them room to grow and learn.

The thesis has similar roots to many successful sales philosophies – that asking value-based questions is more effective than presenting features and benefits (that’s probably a good subject for a whole other post sometime).  The method of selling we use at Return Path which I’ve written about before, SPIN Selling, based on the book by Neil Rackham, gets into that in good detail.  One colorful quote in the book around this came from someone who met two famous 19th century British Prime Ministers and noted that when he came back from a meeting with Gladstone, he was convinced that Gladstone was the smartest person in the world, but when he came back from a meeting with Disraeli, he was convinced that he (not Disraeli) was the smartest person in the world.

Anyway, the book creates archetypal good and bad leaders, called Multipliers and Diminishers, and discusses five traits of both:

  • Talent Magnet vs. Empire Builder (find people’s native genius and amplify it)
  • Liberator vs. Tyrant (create space, demand the best work, delineate your “hard opinions” from your “soft opinions”)
  • Challenger vs. Know-It-All (lay down challenges, ask hard questions)
  • Debate Maker vs. Decision Maker (ask for data, ask each person, limit your own participation in debates)
  • Investor vs. Micromanager (delegate, teach and coach, practice public accountability)

This was a great read.  Any manager who is trying to get more done with less (and who isn’t these days) can benefit from figuring out how to multiply the performance of his or her team by more than 2x.

Feb 16 2012

Book Short: Steve Jobs and Lessons for CEOs and Founders

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.

Nov 18 2007

In Search of Automated Relevance

In Search of Automated Relevance

A bunch of us had a free form meeting last week that started out as an Email Summit focused on protocols and ended up, as Brad put it, with us rolling around in the mud of a much broader and amorphous Messaging Summit.  The participants (and some of their posts on the subject) in addition to me were Fred Wilson (pre, post), Brad FeldPhil Hollows, Tom Evslin (pre, post), and Jeff Pulver (pre, post).  And the discussion to some extent was inspired by and commented on Saul Hansell’s article in the New York Times about “Inbox 2.0” and how Yahoo, Google, and others are trying to make email a more relevant application in today’s world; and Chad Lorenz’s article in Slate called “The Death of Email” (this must be the 923rd article with that headline in the last 36 months) which talks about how email is transitioning to a key part of the online communications mix instead of the epicenter of online communications.

Ok, phew, that’s all the background. 

With everyone else’s commentary on this subject already logged, most of which I agree with, I’ll add a different $0.02.  The buzzword of the day in email marketing is “relevance.”  So why can’t anyone figure out how to make an email client, or any messaging platform for that matter, that starts with that as the premise, even for 1:1 communications?  I think about messaging relevance from two perspectives:  the content, and the channel.

Content.
  In terms of the content of a message, I think of relevance as the combination of Relationship and Context.  The relationship is all about my connection to you.  Are you a friend, a friend of a friend, or someone I don’t know that’s trying to burrow your way onto my agenda for the day?  Are you a business that I know and trust, are you a carefully screened and targeted offer coming from an affiliate of a business I trust, or are you a spammer? 

But as important as the relationship is to the relevance of your message to me, the context is equally important.  Let’s take Brad as an example.  I know him in two distinct contexts:  as one of my venture investors, and as an occasional running partner.  A message from Brad (a trusted relationship) means very different things to me depending on its context.  One might be much more relevant than the other at any moment in my life.

Channel.  The channel through which I send or receive a message has an increasing amount to do with relevance as well.  As with content, I think of channel relevance as the combination of two things –  device, and technology.  For me, the device is limited to three things, two with heavy overlap.  The first is a fixed phone line – work or home (I still think cell service in this country leaves a lot to be desired).  The second is a mobile device, which could mean voice but could also mean data.  The third is a computer, whether desktop or laptop.  In terms of technology, the list is growing by the day.  Voice call, email, IM, Skype, text message, social network messaging, and on and on.

So what  do I mean about channel relevance?  Sometimes, I want to send a message by email from my smartphone.  Sometimes I want to send a text message.  Sometimes I want to make a phone call or just leave a voicemail.  Sometimes I even want to blog or Twitter.  I have yet to desire to send a message in Facebook, but I do sometimes via LinkedIn, so I’m sure I’ll get there.  Same goes for the receiving side.  Sometimes I want to read an email on my handheld.  Sometimes a text message does the job, etc.  Which channel and device I am interested in depends to some extent on the content of the message, per above, but sometimes it depends on what I’m doing and where I am.

So what?  Starting to feel complex?  It should be.  It is.  We all adjusted nicely when we added email to our lives 10 years ago.  It added some communication overhead, but it took the place of some long form paper letters and some phone calls as well.  Now that we seem to be adding new messaging channels every couple weeks, it’s becoming increasingly difficult to get the relevance right.  Overlaying Content (Relationship and Context) with Channel (Device and Technology) creates a matrix that’s very difficult to navigate.

How do we get to a better place?  Technology has to step in and save the day here.  One of the big conclusions from our meeting was that no users care about or even know about the protocol – they just care about the client they interact with.  Where’s the ultra flexible client that allows me to combine all these different channels, on different devices?  Not a one-size-fits-all unified messaging service, but something that I can direct as I see fit?  There are glimmers of hope out there – Gmail integrating IM and email…Simulscribe letting me read my voicemail as an email…Twitter allowing me to input via email, SMS, or web…even good old eFax emailing me a fax – but these just deal with two or three cells in an n-dimensional matrix.

As our CTO Andy Sautins says, software can do anything if it’s designed thoughtfully and if you have enough talent and time to write and test it.  So I believe this “messaging client panacea” could exist if someone put his or her mind to it.  One of the big questions I have about this software is whether or not relevance can be automated, to borrow a phrase from Stephanie Miller, our head of consulting.  Sure, there is a ton of data to mine – but is there ever enough?  Can a piece of software figure out on its own that I want to get a message from Brad about “running” (whatever channel it comes in on) as a text message on my smartphone if we’re talking about running together the next day, but otherwise as an RSS feed in the same folder as the posts from his running blog, but a voicemail from Brad about “running the company” (again, regardless of how he sends it) as an email automatically sorted to the top of my inbox?  Or do I have to undertake an unmanageable amount of preference setting to get the software to behave the way I want it to behave?  And oh by the way, should Brad have any say over how I receive the message, or do I have all the control?  And does the latter question depend on whether Brad is a person or a company?

What does this mean for marketers?  That’s the $64,000 question.  I’m not sure if truly Automated Relevance is even an option today, but marketers can do their best to optimize all four components of my relevance equation:  content via relationship and context, and channel via device and technology.  A cocktail of permission, deep behavioral analysis, segmentation, smart targeting, and a simple but robust preference center probably gets you close enough.  Better software that works across channels with built-in analytics – and a properly sized and whip smart marketing team – should get you the rest of the way there.  But technology and practices are both a ways off from truly automated relevance today.

I hope this hasn’t been too much rolling around in the mud for you.  All thoughts and comments (into my fancy new commenting system, Intense Debate) are welcome!