It’s election season, the GOP convention is literally in my backyard, and while this is not a political blog, I can’t help myself. As we as Americans grapple with the question of who we want to be our next leader (or at least those people who live in the 11 annointed swing states do), I have had a lot of thoughts lately about the question of what makes a good leader, and what the differences are between successful leadership in politics and successful leadership in business.

James O’Toole’s article on President Bush on page 31 of the September issue of Fast Company (no link available yet) brings up a really interesting point in comparing Bush to former president Ronald Reagan. He asserts that “what made Reagan effective and respected was that his actions followed consistently from a positive worldview.” (I’d also argue that the positive worldview as a starting point had something to do with it, but that’s beside the point.) He goes on to say that Bush has an “implementation problem” in that he “has vacillated between contradictory approaches to leadership: realism and idealism.” His central thesis is stated very clearly that

“Realists and idealists can both be effective leaders. But one cannot be both at once…The leadership lesson for GW – and for any leader – is simple: Followers don’t much care if leaders are realists or idealists, but they distrust inconsistency.”

This may or may not be true in the political arena, but I know it’s not true in business. Jim Collins’ watershed books Built to Last and Good to Great — both must reads! — describe the ideal CEO as someone who can simultaneously be optimistic and idealistic about the future of the company while simultaneously recognizing and dealing with the realities of the short-term situation. Ironically for this posting, Collins calls this the Stockdale paradox, after retired Admiral James Stockdale, a military leader and erstwhile vice presidential candidate of Ross Perot in the 1992 election.

As CEO, I have to constantly be selling the vision of the company — what we’re trying to become and how we’re going to get there — in broad strokes to my investors, board, management team, employees, and even customers. It’s that vision that keeps the whole machine running and keeps everyone focused and excited and working hard towards our long-term goals. But I have to be equally vigilant about the mundane realities of the current quarter, making our numbers, containing costs, and running the machine. If I did either one without the other, I think the whole system would break down.

Is Bush’s problem, as O’Toole asserts, that he articulated two different types of reasons for the war in Iraq — one rooted in Realism (WMD) and one rooted in Idealism (freedom and democracy)? Same goes for his states reasons for the tax cut — Realism on the one hand (to stimulate the economy) and Idealism on the other hand (shrink government). I agree that the Bush Administration has occasional implementation problems and doesn’t have nearly the “following” that Reagan and other more successful leaders in the past have, but I don’t think they’re caused by combining Realism and Idealism in the President’s leadership style. I think the leader of the free world has to do both well, each at its appropriate time, in order to be effective at his job.

Next up in this series: Admitting Mistakes.

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

This is a topic we write about obsessively in Startup CXO: A Field Guide to Scaling Up Your Company’s Critical Functions and Teams — in fact, it’s basically the whole point of the book! I’ll write some more specific posts here in the coming weeks that take some excerpts from the book, but Bolster is putting on three free and open webinars we’re calling our “Bolster-up Series” over the coming weeks that I want to share with everyone who reads StartupCEO.com.

In this series, I’ll be doing short interviews with CEOs who we work with at Bolster on the different aspects of scaling specific functions, how they diagnosed those problems, and how they leveraged on-demand executive talent to solve those problems. The three events are:

• 7/20 2:00-2:30pm EST: Signs your Finance function isn’t scaling and what to do about it with MediaWallah founder and CEO Nancy Marzouk.
• 8/12 2:00-2:30pm EST: Signs your Revenue function isn’t scaling and what to do about it with Ozcode CEO Shimon Hason.
• 9/15 2:00-2:30pm EST: Signs your Marketing function isn’t scaling and what to do about it with Drip CEO John Tedesco.

You can sign up for the first one on Finance by clicking here.

As I stared at a dugout of dispirited 14 year old boys Saturday afternoon in our tournament championship game, I found myself talking to my fellow coach Mitch about a book I’d read a few years ago (turns out 14) called Confidence: How Winning Streaks and Losing Streaks Begin and End, written by HBS professor Rosabeth Moss Kantor. While that original blog post is pretty specific to something that was going on at that point in time in my prior company, the thinking in the book about momentum and the role it plays in our psychology, about sports, about business, and about life in general, is timeless.

Watching this team of teens go through ups and downs within an hour was incredibly stark and clear. In the first inning, we made three errors (just jitters from being in the championship…the Bulldogs are better than that!). Those opened the door for our opponent to post a few runs and take a quick lead. It was as if the wind had been taken out of our sails, as if all 11 kids just took a punch to the gut. They were shocked and pretty listless in the dugout, and nothing the coaches could do or say shook them out of it. They just *knew* they were going to lose, so why try? Their confidence was gone. It wasn’t until we staged our own big rally, later in the game, where all of a sudden, one, then two, then three base hits and the kids were going bananas, up at the fence of the dugout and screaming, cheering each other on and feeling all of a sudden like we could win the game.

The swing in momentum took about 5 minutes in each direction. And all that was involved was a couple quick negative/positive indicators/actions.

The bottom line is that we still lost the game 10-5. But the energy that came from a couple positive developments that stopped a downward spiral and started an upward one was palpable and instructive. As one of my other fellow coaches Jay said to the boys after the game, “Boys, the lesson from today is that Everything Matters. We lost 10-5, but when we were only down by 5 runs with the bases loaded, how much did we regret those couple of errors in the first inning? Without those, we would have been down by 2 runs with victory in reach.”

It’s the same in startups.

When you run a startup, you regularly take three punches to the gut in a row — a client cancels on you, you have a web site outage, an employee quits — and all of a sudden, you view the world through a dark lens of, as my long-time friend and Board member Scott Weiss used to say, WFIO, short for We’re F#%ked, It’s Over (pronounced whiff-ee-oh).

And then, the opposite happens, and it’s like the heavens part and the angels start singing a hallelujah chorus. You win a big new deal. You get unexpected positive press or a key blogger or tweet creates massive buzz for you. Your CFO pings you with the news that revenue is surprisingly high this month. WFIO is suddenly replaced with what I’ll call WGTWIA — We’re Going to Win It All (let’s pronounce it wig-twee-uh).

And what’s the difference? Probably nothing big. Probably a couple small things that just happened to break in the right or wrong direction at the right time. That call or email you decided not to return for a couple days until it was too late. That presentation you could have spent an extra 45 minutes perfecting instead of half-assing. That extra run through a new module of code you wrote to make sure it’s fully debugged. Just like a few silly errors in 14-year old baseball because you had the jitters early in a big game.

Everything Matters. In sports, in business, in life. Anything you think is a “throw away” can turn out in retrospect to have made the difference between winning and losing, between success and failure.

Playing To Win

This weekend’s reading included Hardball, by George Stalk and Rob Lachenauer, which started as an article in Harvard Business Review sometime last year.  The book is a fleshed out version of the article, so don’t expect meaningful new revelations if you’ve already read it, but it is an incredibly valuable read, with lots more and more detailed case studies.

As with most business books, it’s not really geared towards small, entrepreneurial companies, but that doesn’t matter.  Most of the principles of competition — and how to win — are timeless.  The basic principles, each of which gets a chapter, are on Unleashing Massive Force, Exploiting Anomalies (perfect for the data junkie within), Threatening the Competition’s Profit Zones, Plagiarizing with Pride, Breaking Compromises, and M&A.

Breaking Compromises is my favorite, because it deals with a facet of human nature that I think can be devastating to business: the “that’s the way it’s always worked” conundrum, otherwise known as “baggage.”  Why does XYZ happen in our business, illogical as it may seem?  Because that’s how we’ve always done it!

We have a (new) mechanism for dealing with the problem of baggage at Return Path, which is meant to be disarming, a bit funny, but dead serious at the same time.  Any time anyone spots someone answering a question or a challenge with the “that’s the way it works” response, they’re strongly encouraged to pull themselves out of the situation and respond with a catchphrase like “baggage alert,” or “boy, that duffle bag must be heavy,” or “hey, nice napsack – is that new or have you had it for a while?”  While it may be a little embarrassing to the recipient, it’s meant to challenge norms and bring about creative thought at all levels of the business.

Breaking Compromises has led to Southwest and Jet Blue, to Saturn (the car, not the planet), and to automobile leasing.  Just think about what it — and the other tactics espoused in Hardball — can do for your company or industry.

Counter Cliche:  How Much Paranoia is Too Much Paranoia?, Part II

After the original posting, one of my readers wrote in with the following question:

I was one of the first employees at a pre-funding enterprise social networking company, after having consulted on doing their business plan for them (not coming up with it; mainly turning the CEO and CTO’s engineer-speak into English). 

So with all that background, when you say “open book” to your employees, can you break that out some more?  I have an idea of what I think that means, and what it doesn’t, but I’d love to hear your thoughts on it too.

My thoughts on this are quite simple.  We are willing to share everything internally other than compensation.  We publish detailed monthly financials and reporting to the team, and we ask that they treat the information as extremely confidential.  We have had only good things come from this level of openness with our team.  Good ideas, good esprit de corps, and a radical reduction in fear of the unknown (the old "Looks like we had a bad quarter, does that mean I need to look for a job now?  Are we running out of money?"). 

In fact, I know one other CEO who goes so far as to publish an only-slightly modified version of his Board books to the entire company.

Transparency is a good thing.

Political versus Corporate Leadership, Part II: Admitting Mistakes

The press conference this past spring where President Bush embarrassingly refused to admit that he had ever made any big mistakes, other than to reiterate his gaffe at trading Sammy Sosa when he owned the Texas Rangers, brings up another issue in this series: is it good for leaders, both political and corporate, to admit mistakes?

On the corporate side, I think the ability to admit a mistake is a must. Again, I’ll refer back to Jim Collins’ books Good to Great and Built to Last, both of which talk about humility and the ability to admit mistakes as a critical component of emotional intelligence, the cornerstone of solid leadership. And in another great work on corporate leadership, The Fifth Discipline, writer Peter Senge talks about “learning systems” and the “learning organization” as far superior companies. My experience echoes this. Publicly admitting a mistake, along with a careful distillation of lessons learned, can go a long way inside a company to strengthening the bond between leader and team, regardless of the size of the company.

But in politics, the stakes are higher and weirder — and the organization is a nation, not a company. Publicly admitting a single mistake can be a leader’s downfall. It’s too easy these days for political opponents to seize on a mistake as a “flip flop” and turn a candidate’s own admission into a highly-charge negative ad.

There was a fantastic op-ed in The Wall Street Journal back on April 15 on this topic, which unfortunately doesn’t have an available link at the moment, entitled “Bush Enters a Political Quandary As He Faces Calls for an Apology.” I’ll try to both quote from and summarize the article here since it’s central to this topic:

“For a politician, is an apology a sign of weakness or strength? That is the debate now swirling around President Bush after a prime-time news conference in which he refused reporters’ invitations to acknowledge any specific mistakes in handling the issue of terrorism or offer an apology to Sept. 11 victims’ families. Mr. Bush deflected the invitation, saying, ‘Here’s what I feel about that: The person responsible for the attacks was Osama bin Laden.’ Mr. Bush’s quandary is a time-honored struggle for politicians. While some have found a public apology helps them out of a tough spot, others discovered it can fuel more criticism. So far, there isn’t a definitive answer.”

The article goes on to say that while Harry Truman’s “the buck stops here” mentality was de rigeur in the Beltway for a while (through Kennedy’s Bay of Pigs fiasco and Reagan’s poor handling of Beirut), nowadays, apologies are a dreaded last resort. The reason? The rise of partisanship and the use of ethics and congressional or special counsel investigations used to humiliate or defeat political opponents by raising the spectre of corruption. The examples? Gingrich’s struggles in 1996 over his book; Clinton’s ridiculous linguistics machinations (“it depends what the definition of ‘is’ is”) around the Lewinsky scandal; and Lott’s downfall over segregationist comments.

The piece wraps up by saying that “Mr. Bush was backed into the apology quandary by one of his administration’s toughest critics, former White House terrorism expert Richard Clarke…Since then, White House officials have been pressured to do likewise [apologize to victims’ families about the government’s failings on 9/11] — or explain why they won’t…[but] aides are convinced that admitting error would only embolden Mr. Bush’s critics in the Democratic Party and the news media.”

So the question is: would Bush be better off by saying “Sorry, folks, we thought there were WMD in Iraq, but it turns out we were wrong. And we miscalculated how difficult it would be to win the war, how many troops it would take, and how many lives would be lost. I still feel like it was right for us to go to war there for the following four reasons…”?

I’m not sure about that. He’d certainly be more intellectually honest, and a number of people in intellectual circles would feel better about him as a leader, but my guess is that he thinks it would cost him the election in today’s environment. My conclusion is that today’s system is discouraging politicians from admitting mistakes, and that it will take an exceptionally courageous leader (neither Bush nor Kerry as far as I can tell) to do so.

In the end, while humility appeals to many people in a leader, it’s not for everyone. Fortunately for us, CEOs don’t have to run for office and most CEOs don’t have to face some the same level of public, personally competitive, and media scrutiny that politicians do. Now that’s an interesting conclusion that I didn’t intend at the beginning of the post — being a good political leader and being a good politician are sometimes deeply at odds with each other.

Next up in the series: Not sure! Any ideas? Please comment on the blog site or by emailing me.

How to Wow Your Manager

Last week, I talked about how to Wow your employees.  Now I am going to discuss the converse of that – How to Wow your Manager.  Why Wow your manager?  Even if you are senior leader in an organization, the Wow factor is still important.

What impact does a Wow have?  It sends the signal that you are on top of things.  Symbolism is important.  It also advances the cause further and faster.  Why do you want to foster Wow moments with your team?  High performing teams have a lot of Wow going on.  If all members of a team see Wow regularly, they are all inspired to do more sooner, better.

Here are my top 10 examples on how to WOW your manager, along with the intended impact:

1. Show up for every check-in with the full agenda – send it a day or more ahead (Give your manager time and space to prepare)
2.  When you are asking your manager to communicate something (an email to the team, a reference letter, etc.), draft it for him or her (Editing is much easier than creating)
3.  Do a start-stop-continue analysis once a year on all of your key activities (Make yourself as efficient and effective as possible – that’s your responsibility as much as your manager’s)
4.  Own your own development plan and check in on it at least quarterly (Those who own their own career paths progress more quickly down them)
5. Read a relevant business book and ask your manager to discuss insights with you (Staying current with best practices in your field – books, articles, blog posts, videos, mentors, lectures –  is key in a learning organization)
6.  Dress for success – even casual can be neat and “client ready” (Your presence has an impact on those around you.  There’s no reason anyone should ever have to comment on your clothes, your hair, or any aspect of your personal hygiene)
7. Respond to every email where you are on the TO line within a day, even if it’s to say you will respond longer form later (At Return Path,  you have to be in the jet stream of communications. Otherwise, you find yourself in the exhaust of the jet stream)
8. End every meaningful interaction by asking for informal feedback on how you’re doing and what else you can be doing (Again, part of being in a learning organization…and taking more tasks on is always a sign that you are ready for more responsibility)
9. Do something that’s not required but that you feel is a best practice (This shows you’re on top of your game.  One example:  I send the Board a summary, the details, and the YoY trending of all of my expenses every year.  I don’t have to, but enough CEOs out there have high profile expense problems that I decided it’s a good practice.  They all LOVE it)
10.  (If you have staff reporting into you) Show up for every check-in with  your manager with a list of all staff issues and highlights (You need to bubble things up, both good and bad, so your manager is on top of his or her overall team and (a) is never surprised by events, (b) knows how best to handle skip-level communications, and (c) can think more broadly about resource deployment across the organization)

As part of the new section on Exits in the Second Edition of the book (order here), there’s a specific chapter around the sale process itself.  There are some interesting things in it — the arc and timeline of a deal, working with and through advisors vs. principals dealing with each other directly, optimizing for different stakeholders, and a wonderful long sidebar by my friends and advisors Brian Andersen and Mark Greenbaum from Luma Partners on how to think strategically about an exit and how buyers think.  It’s probably worth buying the whole book just for that.

But what I want to write about here is coping with a failed deal – something my team and I unfortunately had to do a couple years before we actually sold the company and something I’ve never written about or discussed publicly.

In 2017, we almost sold Return Path.  You hear people talk about that from time to time, and frequently it just means “we had a good offer but decided not to take it.”  But in this case, I meant it.  We had a good offer.  We talked to a couple other potential buyers in the industry and ended up getting a great offer.  From a great buyer.  We decided to pull the trigger.  It was time.  We got through the entire deal process, I mean EVERYTHING.  Diligence was painful, thorough – and completed.  Both sides had signed off on things many times along the way.  Documents were done, lawyers had signed off on them, our Board had signed off on them, they had been posted to DocuSign, and our signatures were in escrow.  The press release was written and scheduled to go out in less than 48 hours.  Our all-hands meeting was scheduled.  The acquirer had already sent us their swag to hand out.  About 80 people out of 400+ employees at the company knew about it.  In the football analogy, we weren’t inside the red zone.  We were on the 1-yard line.  

Then the call came.  “I can’t believe we have to tell you this, but our CEO just decided to pull the plug on this at the last minute.”  Buh.  Bye.  To say this was a disappointment is the understatement of a career.  

That evening, I was staying over at a friend’s apartment in Manhattan while Mariquita and the kids were away at the beach with her parents.  After the call came in, I grabbed the two other execs who were still in the office, and we went immediately to a bar.  That calmed me down a little bit.  Then I wandered through Central Park up to the apartment and spent about 4 hours on the phone in a series of cathartic phone calls with the rest of the executive team, some of my closest friends and advisors, and Board members.  

The next couple of days were awful.  We had to tell a huge number of employees “Uh sorry, just kidding.  You know all those stock options that were just about to turn into cash?  Sorry.  The new company we were all excited to join?  Psych!”  The worst part was scrambling to turn the already-scheduled all-hands meeting to announce the deal into just another quarterly update.  Everyone in the room for that meeting who knew about the failed deal just looked at each other with disbelief. We were still in shock.

Eventually of course, we bounced back.  I am now an even more ardent believer in the expression, “What doesn’t kill you makes you stronger.”  The company ended up recovering from this and doing a number of things to make us even better in the years that followed, leading to our eventual sale.  But I will say, it was just terrible, and nothing about the recovery was easy.  I talk about some of the specific steps we took in the book.  But mostly, I hope no one ever has to go through anything like this again.  This was too big, too close to the end, and too well known.  Our team will have deep scar tissue from it for a long time.

I was honored this week to be in a small group “fireside chat” with Angela Duckworth, author of the book Grit: The Power of Passion and Perseverance, and to meet her and ask a question.

I want to hit on one theme here from the book and dialog, but I’ll start by sharing a 2×2 matrix (remember, I’m an ex-consultant, I think in frameworks) that we’ve used at home with our kids periodically. For the most part, we use it to talk to them about why they should work harder on math homework, but it’s had other use cases as well. Hopefully it makes sense on the face of it…

…but essentially the framework teaches that if you are talented AND work hard at something, you can achieve great things. If you have talent and slack off, you can get by perfectly fine. If you have no talent but work your butt off, you can get there…but it’s hard. And if there’s an area of life where you have no talent and don’t work at it, so be it, but you’re punting on that whole thing.

In the book, Duckworth takes this to a whole new level by adding a simultaneous second equation:

• Talent x Effort = Skill
• Skill x Effort = Achievement

This makes the statement that “your first bit of talent, combined with effort increases your skill level. Your increasing skill, multiplied by effort, leads to achievement. That means effort counts twice. Once for skill and once for achievement. But that doesn’t mean it’s twice as important. If you substitute the skill equation into the achievement equation, you end up with

• Talent x Effort x Effort = Achievement, which means that 
• Talent x Effort² = Achievement.

Or in other words, “Your effort is exponentially more important than how talented you are.”

All I have to say is that while I won’t create a second graphical explanation of this and probably won’t go back and amend my 2×2 for my kids, I think Duckworth is right, with one caveat. If you don’t have a certain baseline of talent in a certain area, it just doesn’t matter how much effort you apply – your achievement has some kind of natural governor to it. When I was a kid, I would dearly have loved to be the shortstop for the San Diego Padres, but between being a lefty, a kid, and not what you would call overly athletic, it wouldn’t have mattered if I spent every waking hour of a decade working at it…I never would have gotten there. Having said that, those cases may be edge cases, and again, I find that the emphasis on effort on top of my framework is a very worth application.

But go read Grit. It’s much better and more detailed than this blog post!

Several years ago, I blogged about the training program we created for entry-level employees at Return Path, including an embedded presentation that we used to use (which I hope still works on the blog after all these years).

My brother Michael, who is an experienced manager and leader in the digital marketing space, recently sent me this email that I thought I’d share along the same lines to colleagues who are new to the working world. Enjoy!

I signed up to give advice on LinkedIn, and had someone just starting her first job reach out to me asking for general advice. I came up with the attached, and thought it might make for a good blog post on Only Once. If you decide not to publish it, I’m totally cool with that, but thought I would share it. After all, you’re only a brand new employee once too 🙂

1) Listen as much as possible. One of my mentors was fond of reminding me, “God gave you two ears and one mouth!” You should listen at least twice as much as you talk. Get to know your environment and the people around you. Take notes. Observe as much as possible. Learn how others are able to provide value to the organization. Start to anticipate little things that need to be done, and then do them before your manager asks you to. Then bit by bit, use your creativity to start to develop bigger hypotheses about how you can provide even greater value. 

2) “In business, the best story wins.” That’s another quote from a former manager of mine that I have found to be universally true. People in business respond to many things: numbers, bullet points, graphs and visualizations. But they respond to all of those things better when they are wrapped in stories. A great book you can read about storytelling is not about business at all. It’s called “Story” by Robert McKee, and it’s about screenwriting. Despite its apparent lack of applicability, I assure you it will help you think about characters, goals, antagonists, drama, obstacles, and structure — all the elements that go into a good story. When you can present your hypotheses in the context of a story, about your business, your customers, what you want to achieve, how you will do it, and why it matters, you will build consensus and show leadership. Another great book you can read here, again, not about business at all, is “Sapiens” by Yuval Noah Harari. It really opened my eyes about how so much of human history and behavior is really just based on stories. 

3) Be lean. There is another book you should read, called “The Lean Startup”, by Eric Ries. This one is actually about business :). As you think about your hypotheses, think of them in the context of how you can get to market quickly and inexpensively. How you can easily perform experiments that will test your hypotheses. Some of your experiments will not achieve your desired result, but it’s not a failure if you can learn something that helps you pivot towards success. Learnings enable you to adjust and refine your hypotheses as you try to find more value for your organization. 

4) “Objections are requirements” and a corollary “ask questions, don’t make statements.” These two gems are from that first mentor in item number one. Even if you can tell great stories, and even if you can devise and execute lean experiments that achieve business results or provide validated learnings, sometimes “haters gonna hate.” There will always be inhibitors to your bold ideas, with reasons not to proceed with your experiments. Inertia is part of human nature. But don’t fear! When an inhibitor comes along, the first thing you do is start to ask questions. “Why do you object to x?” “Oh,” they’ll say, “because of y and z.” Then ask another question “So if we can resolve y and z, then can we proceed with x?” Rather than repeating yourself and making more statements, by asking questions you’ve just turned their objections into requirements. That inhibitor no longer has their reasons not to proceed with your bold idea. You’ve turned them from antagonists into allies. This kind of creative problem solving is critical to getting your experiments into market, and building consensus and showing your leadership without alienating anyone. 

5) Ok I know I said four, but this one is optional (albeit important). Have fun! Do not take yourself or your role too seriously. Show your personality. Be yourself. That sort of general approach to work and life will draw people to you. They will be relaxed and comfortable around you. They will look forward to meetings with you. You will be successful if you are a good listener, a creative thinker with bold ideas, a fantastic storyteller, an agile experiment developer, and a leader who can build consensus and drive value. But if you are all those things, and you’re fun to be around? Then you will be unstoppable.

Thank you, Michael, for the contribution!