Political versus Corporate Leadership, Part I: Realist or Idealist?
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.
Corporate Sniglets
Corporate Sniglets
This might be showing my age, but those who may have watched Not Necessarily the News in the 80s might remember the Sniglets segment that Rich Hall pioneered which spawned a series of short, fun books. Sniglets are words which are not in the dictionary, but which should be. I can remember a couple of examples from years ago that make the point — aquadexterity is the ability to operate bathtub dials with one’s feet; cheedle is the orange residue left on one’s fingers after eating a bag of Cheetos.
As is the case with many companies, we have made up some of our own words over the years at Return Path – think of them as Corporate Sniglets. I’m sure we have more than these, but here are a few that we use internally:
- Underlap is the opposite of Overlap. My colleague Tom Bartel coined this gem years ago when he was leading the integration work on an acquisition we did, as in “let’s look for areas of Overlap as well as areas of Underlap (things that neither companies does, but which we should as a combined company).”
- Pre-Mortem or Mid-Mortem are the timing opposites of Post-Mortem. We do Post-Mortems religiously, but sometimes you want to do one ahead of a project to think about what COULD go wrong and how to head those things off at the pass, or in the middle of a project to course-correct on it. I believe my colleague George Bilbrey gets credit for the Pre-Mortem, and I think I might have come up with Mid-Mortem.
- Frontfill is the opposite of Backfill. While you Backfill a position after an employee leaves, you can Frontfill it if you know someone is going to leave to get ahead of the curve and make sure you don’t have a big gap without a role being filled. Credit to Mike Mills for this one
RPers, are there others I’m missing? Anyone else have any other gems from other companies?
A Culture of Appreciation
A Culture of Appreciation
As I mentioned in my last post in the Collaboration is Hard series, we’ve tried to create a culture of appreciation at Return Path that lowers barriers to collaboration and rewards mutual successes. We developed a system that’s modeled somewhat after a couple of those short Ken Blanchard books, Whale Done and Gung Ho! It may seem a little hokey, and it doesn’t work 100% of the time, but in general, it’s a great way to make it easy for people to say a public “thanks” to a colleague for a job well done.
The idea is simple. We have an “award request” form on our company Intranet that any employee can use to request one of five awards for one or more of their colleagues, and the list evolves over time. The awards are:
ABCD – for going Above and Beyond the Call of Duty
Double E – for “everyday excellence”
Crowbar – for helping someone in sales “pry our way in” to a new customer
Damn, I Wish I’d Thought of That – for coming up with a great insight for the business (credit for the name of course goes to our former colleague Andy Sernovitz)
WOOT – for Working Out Of Title and helping a colleague
Our HR coordinator Lisa does a quick review of award submissions to make sure they are true to their definitions and make sure that people aren’t abusing the system, and the awards are announced and posted on the home page of the Intranet every week and via RSS feed in near-real time.
Each award carries a token monetary value of $25-$200 paid with American Express gift checks, which are basically like cash. We send out the checks with mini-statements to employees every quarter.
It’s not a perfect system. The biggest shortcoming is that it’s not used evenly by different people or different groups. But it’s the best thing we’ve come up with so far to allow everyone in the company to give a colleague a virtual pat on the back, which encourages great teamwork!
What Does a CEO Do, Anyway?
What Does a CEO Do, Anyway?
Fred has a great post up last week in his MBA Mondays series caled “What a CEO Does.” His three things (worth reading his whole post anyway) are set vision/strategy and communicate broadly, recruit/hire/retain top talent, and make sure there’s enough cash in the bank.
It’s great advice. These three are core job responsibilities of any CEO, probably of any company, any size. I’d like to build on that premise by adding two other dimensions to the list. Fred was kind enough to offer me a “guest blogger” spot, so this post also appears today on his blog as well.
First, three corollaries – one for each of the three responsibilities Fred outlines.
- Setting vision and strategy are key…but in order to do that, the CEO must remember the principle of NIHITO (Nothing Interesting Happens in the Office) and must spend time in-market. Get to know competitors well. Spend time with customers and channel partners. Actively work industry associations. Walk the floor at conferences. Understand what the substitute products are (not just direct competition).
- Recruiting and retaining top talent are pay-to-play…but you have to go well beyond the standards and basics here. You have to be personally involved in as much of the process as you can – it’s not about delegating it to HR. I find that fostering all-hands engagement is a CEO-led initiative. Regularly conduct random roundtables of 6-10 employees. Send your Board reports to ALL (redact what you must) and make your all-hands meetings Q&A instead of status updates. Hold a CEO Council every time you have a tough decision to make and want a cross-section of opinions.
- Making sure there’s enough cash in the bank keeps the lights on…but managing a handful of financial metrics on concert with each other is what really makes the engine hum. A lot of cash with a lot of debt is a poor position to be in. Looking at recognized revenue when you really need to focus on bookings is shortsighted. Managing operating losses as your burn/runway proxy when you have huge looming CapEx needs is a problem.
Second, three behaviors a CEO has to embody in order to be successful – this goes beyond the job description into key competencies.
- Don’t be a bottleneck. You don’t have to be an Inbox-Zero nut, but you do need to make sure you don’t have people in the company chronically waiting on you before they can take their next actions on projects. Otherwise, you lose all the leverage you have in hiring a team.
- Run great meetings. Meetings are a company’s most expensive endeavors. 10 people around a table for an hour is a lot of salary expense! Make sure your meetings are as short as possible, as actionable as possible, and as interesting as possible. Don’t hold a meeting when an email or 5-minute recorded message will suffice. Don’t hold a weekly standing meeting when it can be biweekly. Vary the tempo of your meetings to match their purpose – the same staff group can have a weekly with one agenda, a monthly with a different agenda, and a quarterly with a different agenda.
- Keep yourself fresh…Join a CEO peer group. Work with an executive coach. Read business literature (blogs, books, magazines) like mad and apply your learnings. Exercise regularly. Don’t neglect your family or your hobbies. Keep the bulk of your weekends, and at least one two-week vacation each year, sacrosanct and unplugged.
There are a million other things to do, or that you need to do well…but this is a good starting point for success.
Signs your critical functions aren’t scaling – three webinars
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.
Momentum and Confidence: Everything Matters
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.
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…
Counter Cliche: How Much Paranoia is Too Much Paranoia?, Part II
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).
After being asked to participate more fully in the marketing and biz dev aspects of the company, I quickly found myself stymied by the level of secrecy the CEO maintained. Now, I understand that you wouldn’t want important information getting out to competitors, but that can be handled by making that clear to team members. I found it frustrating and that it encumbered the kind of “team spirit” that a good startup should have; it prevented the sharing of how someone moved the ball forward, and having others weigh in on how incremental moves based on this new information could make non-linear gains.
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.
Playing To Win
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.
Political versus Corporate Leadership, Part II: Admitting Mistakes
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
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:
- 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)
- Â 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)
-  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)
- Â 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)
- 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)
-  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)
- 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)
- 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)
- 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)
-  (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)



