We have a little more than two weeks of The Daily Bolster podcast under our belts now, and we’re off to a great start! I announced it here, and I thought I’d post links to the first bunch of episodes…I don’t think I’ll do this regularly, though. You can listen to all episodes here (or on your favorite podcast platform), and never miss an episode when you sign up for daily email notifications.

Episode 1: 3 Tips to Scale Your Culture with Nick Mehta

Our very first guest on The Daily Bolster was Nick Mehta, CEO of Gainsight. As an early-stage startup or a small business, you have significant influence over the culture—but what happens when you’re one of many? Nick and I discussed what happens to company culture when you achieve your scaling and growth goals.

Episode 2: Managing Up with Cristina Miller

Executives are often caught in the middle of the leadership dynamic, managing both up and down the organization. Cristina Miller—a seasoned, results-driven executive and board member (including on Bolster’s board!) with a strong track record—shared what it looks like to set expectations and build a strong relationship with your CEO.

Episode 3: Common Mistakes Founders Make with Fred Wilson

Fred Wilson has been a venture capitalist since 1987 and has worked with me for over 20 years now—so it’s fair to say he’s witnessed a few founders and become familiar with their most common mistakes. Listen to this episode to learn how to recognize and avoid those mistakes for yourself.

Episode 4: Cultivating Talent to Promote Internally with Nick Francis

In this episode, Nick Francis—co-founder and CEO of Help Scout—joins me to discuss what it takes to cultivate in-house talent and embody organizational values. I talk about my playbook for building effective teams and developing leaders with a growth mentality as part of this.

Episode 5: Deep Dive with Jeff Epstein

Career shifts are more common now than ever, even for senior executives. Experienced CFO and operator (and one of my former board members) Jeff Epstein joined me for an extended episode about the ins and outs of career transitions and the surprises that come with them, from role changes to new industries to vastly different organizational structures. Tune in to follow the shifts in Jeff’s career journey, hear about the lessons he learned firsthand, and get his advice for founders looking to scale. “I always wanted to develop a circle of competence and then over time expand the circle,” Jeff says. “You just learn more.”

Episode 6: Hallmarks of Successful Founders with David Cohen

David Cohen, Founder and Chairman at Techstars, shares the top three signs he looks for that differentiate successful founders—things that are nearly impossible to fake. Either you have them, or you don’t. This one is awesome.

Episode 7: Success as a Fractional Exec with Courtney Graeber

If you know anything about Bolster, you know we’re a champion for fractional executives. As an Interim Chief People Officer, HR Executive Consultant, and trusted mentor to executive teams, Courtney Graeber provides feedback and recommendations that enhance organizational culture and attract, develop, and retain top talent. Many of her clients are navigating transitional periods—and that’s where Courtney’s expertise comes in. Listen in to learn what it’s like to be (or work with) a fractional head of people.

Episode 8: 3 Ways VCs Say “No” Without Saying “No” with Jenny Fielding

It’s important for founders to be able to hear what’s left unsaid in conversations with VCs. Sometimes, says one of NYC’s top pre-seed investors Jenny Fielding, VCs aren’t ready to invest in a startup, but they’re not ready to say no, either.  Here, Jenny shares three signs a VC may be saying “no” without saying the words—and what founders should do next.

Episode 9: Building a Strong Culture with Jailany Thiaw

Jailany Thiaw, founder and CEO of UPskill, a future-of-work startup automating feedback in entry-level hiring pipelines, joins me to discuss the best ways to get company buy-in as you build and maintain a strong and welcoming culture—especially in an early stage or remote environment.

Episode 10: Deep Dive with Brad Feld

Brad Feld is partner and co-founder of Foundry, and a long time early stage investor and entrepreneur who I’ve also worked with for more than two decades. In this episode, he and I take a deep dive into how startups and venture capital have changed over the past 25 years—and what has stayed the same.  They also discuss the dynamics of startup boards, along with common characteristics that make founders or companies successful at scale.

Episode 11: The Value of Podcasting with Lindsay Tjepkema

This episode is all about podcasting. Meta, right? Lindsay Tjepkema is the CEO and co-founder of Casted, the podcasting solution for B2B marketers.  She and I dive into the reasons why podcasts are such a great way to get your voice—literally—out into the world. Tune in to hear Lindsay’s tips for starting a podcast as a CEO, setting expectations, asking meaningful questions, and creating human connection. We’ve loved partnering with Lindsay and her team so far on The Daily Bolster!

Episode 12: Interviewing for “Culture Fit” with Rory Verrett

What does it mean to interview for culture fit? How should CEOs and leaders go about doing it—and is there a better way? Rory Verrett is the founder and managing partner of Protégé Search, the leading retained search and leadership advisory firm focused on diverse talent, and is also on Bolster’s Board of Directors. He and I discuss why CEOs are not always the best arbiters of company culture, then we dive into what it means to look for specific values throughout the interview process, rather than the vague concept of a culture fit.

The Daily Bolster is for people in the startup world want to hear from industry experts of all backgrounds, but don’t always have the time to listen to full length interviews, even at 2x speed. Instead, we’re getting straight to the point with mostly 5-minute episodes. Any and all feedback welcome!

I’ve gotten to know a number of Bolster members over the last few years, and one who I have come to appreciate quite a bit is Tim Porthouse. I’m on Tim’s email list, and with his permission, I’m reprinting something he wrote in his newsletter this month on the topic of CEO engagement in politics and current events. As you may know, I’ve written a bunch on this topic lately, with two posts with the same title as this one, Should CEOs wade into Politics (part I here, part II here). Thanks to Tim for having such an articulate framework on this important subject.

Your Leadership Game: “No Comment.”

Should you speak up about news events/ politics?

Most of the time, I say, no!

Startup CEOs feel pressure to speak up on news events: Black Lives Matter, Abortion, LBGTQ+ rights, the conflict in Israel/Palestine, Trump vs. Biden. Many tell me they feel pressured to say something, but are deeply conflicted.

Like you, I am deeply distressed by wars, murder, restrictions on human rights, bias, and hate. But if we feel something, should we say something?

Before you speak up, ask the following questions:

1.      Mission relevance. Is your startup’s success or mission on the line? Are customers or employees directly impacted? Example: It makes sense for Airbnb to advocate when a city tries to ban short-term rentals. It makes sense to advocate for your LBGTQ+ employees when a state tries to restrict their rights.

2.      Moving the needle. Will speaking out change anything? If you “denounce” something or “take a stand,” what really happens? Example: If you have employees in a state banning abortion and you tell them your startup will support them as much as the law allows, this could create great peace of mind for employees. But if your startup does not operate in Ukraine or Russia, then denouncing Russia does little (and Russia does not care!)

3.      Expertise. Do you have a deep understanding of the situation? It’s usually more complicated than it appears, especially at first. Once you speak out, you have painted yourself into a corner you will be forced to defend.

4.      Precedence and equivalence. If you issue a statement about today’s news event, will you react to tomorrow’s event? Why not? Where do you draw the line?Someone will be offended that you spoke up about X but not Y.

5.      Backlash. Are you ready to spend significant time engaging with those who disagree with you?It can get ugly quickly, and mistakes can be costly. Plus, the American public is tiring of business leaders commenting on the news.

6.      Vicarious liability. Who are you speaking for? When you say, “Our startup denounces X”?Does the whole company denounce it? You don’t know, and probably not. Does the Leadership Team? They may feel pressured to support you. What you are really saying is, “I denounce X!” OK, great, then say it to your friends and family. Leave your startup to talk about business.

If your answers are “yes,” – then speak out.

If not, I recommend keeping quiet.

In my opinion, our job is to build great companies, not debate current events.

By not speaking out, you can say, “We don’t talk politics here.” You can shut down any two-sided arguments at work and say, “Let’s get back to work,”removing a big distraction. Remember when employees protested because Google was bidding for Pentagon contracts?

I realize that you will be challenged to make a statement, that, “Saying nothing is unacceptable/ complicit.” But whoever challenges you will only be satisfied if you support their view.

If you still want to speak out, I respect your choice. Some of you will be angry with me for writing this, and I accept that. I’m asking you to think carefully before you make a statement.

I’m thrilled to announce that we created mini-books (about 80 pages long and only $9-10 on Amazon) out of five of the major functional areas covered in Startup CXO: A Field Guide to Scaling Up Your Company’s Critical Functions and Teams, part of our series along with Startup CEO: A Field Guide to Scaling Up Your Business and Startup Boards: A Field Guide to Building and Leading an Effective Board of Directors.

I’ve always said that while I love all three books, in some ways Startup CXO is the best because it’s a “book of books.” While I’d still encourage all CEOs and senior executives (CXOs) to read the full manuscript, my friends and co-authors and I are happy to present these five books, now available on Amazon, for functional specialists:

• Startup CFO: A Field Guide to Scaling Up Your Company’s Finance Function
• Startup CRO: A Field Guide to Scaling Up Your Company’s Sales Function
• Startup CMO: A Field Guide to Scaling up Your Company’s Marketing Function
• Startup CPO: A Field Guide to Scaling Up Your Company’s HR/People Function
• Startup CTO: A Field Guide to Scaling Up Your Company’s Technology/Product Function

Each book has several topics in common – chapters on the nature of an executive’s role, how a fractional person works in that role, how the role works with the leadership team, how to hire that role, how the role works in the beginning of a startup’s life, how the role scales over time, and CEO:CEO advice about managing the role.

In Startup CFO, the role-specific topics Jack Sinclair talks about are Laying the CFO Foundation, Fundraising, Size of Opportunity, Financial Plan, Unit Economics and KPIs, Investor Ecosystem Research, Pricing and Valuation, Due Diligence and Corporate Documentation, Using External Counsel, Operational Accounting, Treasury and Cash Management, Building an In-House Accounting Team, International Operations, Strategic Finance, High Impact Areas for the Startup CFO as Partner, Board and Shareholder Management, Equity, and M&A.

In Startup CRO, the role-specific topics Anita Absey talks about are Hiring the Right People, Profile of Successful Sales People, Compensation, Pipeline, Scaling the Sales Organization, Sales Culture, Sales Process and Methodology, Sales Operating System, Marketing Alignment, Market Assessment & Alignment, Channels, Geographic Expansion, and Packaging & Pricing.

In Startup CMO, the role-specific topics Nick Badgett and Holly Enneking talk about are Generating Demand for Sales, Supporting the Company’s Culture, Breaking Down Marketing’s Functions, Events, Content & Communication, Product Marketing, Marketing Operations, Sales Development, and Building a Marketing Machine.

In Startup CPO (HR/People), the role-specific topics Cathy Hawley talks about are Values and Culture, Diversity Equity and Inclusion, Building Your Team, Organizational Design and Operating Systems, Team Development, Leadership Development, Talent and Performance Management, Career Pathing, Role Specific Learning and Development, Employee Engagement, Rewards and Recognition, Reductions in Force, Recruiting, Onboarding, Compensation, People Operations, and Systems.

In Startup CTO (Technology and Product), the role-specific topics Shawn Nussbaum talks about are The Product Development Leaders, Product Development Culture, Technical Strategy, Proportional Engineering Investment and Managing Technical Debt, Shifting to a New Development Culture, Starting Things, Hiring Product Development Team Members, Increasing the Funnel and Building Diverse Teams, Retaining and Career Pathing People, Hiring and Growing Leaders, Organizing Collaborating with and Motivating Effective Teams, Due Diligence and Lessons Learned from a Sale Process, Selling Your Company, Preparation, and Selling Your Company/Telling the Story.

Each of these executives is a true subject matter expert, not to mention a great friend and someone who is a lot of fun to hang out with on an executive team. I’m proud of these books and hope they’re a useful addition to the startup canon.

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

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!

Most psychologists, and lots of executive coaches, end up talking to their clients about their “Family of Origin” as a means of more deeply understanding the origins of their clients’ motivations, fears, hopes, and dreams.  Presumably they do this in service of helping their clients gain self-awareness around those things to be more effective in their personal or professional lives.

A smattering of highly-ranked search results on the term yields snippets like these for its definition:

• One’s family of origin—the family one grew up in, as opposed to the people one currently lives with—is the place that people typically learn to become who they are
• From the family of origin a person learns how to communicate, process emotions, and get needs met
• People also learn many of their values and beliefs from their families

…and these for its impact:

• As a worker, your experiences in your family of origin are likely to impact on the way you work
• Families always involve negative and positive dynamics, which may lead to members gaining strengths and abilities or experiencing difficulties
• Differentiation from family is a significant concept. Well-differentiated people function better
• Greater awareness of the impact of your family of origin on you will benefit your work

I’m no shrink, nor am I an executive coach, but this makes sense to me, and I’ve seen it in action many times in both my personal and professional life.

The concept I want to introduce today is a related and in some ways parallel one, and one that I think may be equally if not more important to how someone behaves professionally.  That concept is the Company of Origin.  I’ll define one’s Company of Origin is the first place or places one has meaningful work experience.  For most working professionals, that is probably the first full-time job we held for at least a couple of years after college or graduate school.  For others, it may be a couple of long-held part-time jobs during school.  There are probably other cases, but hopefully you get the point.  A couple of my trusted colleagues in the HR/OD profession suggested that this could also be labeled Profession of Origin or Manager of Origin or “When I came into my own as a professional.”  I think the same concepts apply.

Going back to the definition above of Family of Origin and modifying it (only slightly) to define Company of Origin would look something like this:

• One’s Company of Origin – the first place or places one has a meaningful work experience, as opposed to the place one currently works – is the place that people typically learn to become who they are professionally
• From one’s Company of Origin, a person learns how to communicate at work, how to experience success and failure, what accountability means, what reward and recognition mean, what good and bad management and leadership look like, etc. etc.
• People also learn many of their professionals values and beliefs from their Companies of Origin

I know this rings true for me in my own life.  My first job as a management consultant still has a profound influence over my work today.  My first few jobs before I started Return Path all had a profound influence over how I decided to set a culture and make decisions (and still do, though a bit less with each passing year).  Some of those influences were positive – “let’s do more of that!” – and some were negative – “if I ever become the boss, I’ll never…” – but you’d expect that from a Company of Origin, just as you would a Family of Origin.

It also rings true for countless other people I’ve worked with over the years.  Think about people you’ve worked with.  Have you ever said or thought anything like this before?

• Bob used to work at GE.  That’s why he has such strong leadership skills
• Why is Jane so concerned with expenses?  Her first job was at a family-run business where every dollar spent was a dollar out of the CEO’s pocket
• Wow is Harry political at work.  I guess it’s because he used to work at XYZ Corp where people stab each other in the back to get promoted
• Oh, Sally is ex-military.  That’s why she’s so hierarchical
• Doesn’t Doug understand that part of being an employee here is doing XYZ?  That’s not how he was conditioned to think at work when he worked at PDQ Corp.  He’s just hard wired that way
• Frank just loves standing up in front of a room and drawing things on a whiteboard.  I guess that’s because he started his career as a teacher

Of course, unlike a Family of Origin, you don’t have to live in some way with your Company of Origin forever, and unlike family configurations, where the average person will have a few in a lifetime, the average person will have many places of work.  All of those workplaces will shape one’s behaviors in the workplace.  But there’s something about the Company of Origin that sticks with professionals more than other workplaces.

Again, going back to those “impact” comments about Family of Origin and modifying them only slightly for Company of Origin, you get this:

• As a worker, your experiences in your Company of Origin are likely to impact on the way you work
• Companies always involve negative and positive dynamics, which may lead to employees gaining different strengths and abilities or experiencing difficulties or experiencing the workplace differently
• Differentiation from Company of Origin is a significant concept. Well-differentiated people function better as they move from job to job
• Greater awareness of the impact of your Company of Origin on you will benefit your work

As I wrote several years ago, People Should Come with an Instruction Manual.  Understanding your potential employees’ and actual employees’ Companies of Origin would go a LONG way towards fleshing out their strengths, weaknesses, likely behaviors, likely fits with your culture and organization, and on and on.  Whether during the interview process for candidates or the development planning/360 process for employees, I hope this concept is something useful to consider.

Book Short:  You’d Never Run Your Business This Way…

I am an unabashed conservative, so you might wonder what I was doing reading  A Country That Works, by union chief Andy Stern, the President of SEIU (Service Workers International Union) this weekend.  Well, part of it is that my mother-in-law Carmen works for him.  Part was that he was quite inspiring during his recent appearance on the Colbert Report a week or two ago.  And part was that I always like reading about different points of view, especially with the current, somewhat dismal state of the Republican leadership in Washington.

The book was very short and a worthwhile read.  I may not agree with Stern on some of his illustrations of the problems — his statistical presentations were a bit apples-to-oranges at times — and some of his solutions, which were a bit high on the big-government-tax-and-spend side for me, but the book was very plain-speak, apolitical, and solution-oriented, all of which I found refreshing.

He certainly had at least one underlying premise about “labor as electricity ” (compete on something else other than forcing wages to go lower) that is making me think hard about my long-standing philosophical opposition to federally-mandated minimum wages.  His notion of the importance of a global labor movement to act as a check/balance on corporate globalization both make sense.  Actually, now that I think about it, those two things put together start working well as one plank in a solution to global poverty.

But the best part of the book was the fact that Stern is clear that, like his ideas or hate them,  he is at least proposing that we DEAL with them.  America is missing serious debate about some critical issues facing our society.  Anyone who doesn’t think we have serious problems facing our future around retirement savings, education, and health care is not facing reality.  The debate happening in Washington today is weak at best, and over-politicized.

The bottom line is that I think we’re in danger as a country of boiling the frog when it comes to some major structural issues in our society, and, most important to me, You’d Never Run Your Business This Way.  Any good entrepreneur knows that when danger lurks around the corner, you have to reinvent yourself, and we as a country aren’t doing that at this moment when we’d benefit from it greatly for the long term.  Stern displays that mix of optimism for the future and serious reality check today known as the Stockdale Paradox and revered by Jim Collins in his two books on corporate leadership, Good to Great and Built to Last.

My biggest criticism of the book was that it was too short.  It was basically 1/3 Andy’s story, 1/3 SEIU’s story, and 1/3 labor’s story — and it could have been at least twice as long and gone into more detail on Stern’s points, especially in the last chapter where he starts spelling out his plan to get America back on track.  But presumably when Stern runs for national office or gets a cabinet appointment someday (no inside knowledge here, but the book certainly reads that way), he’ll flesh things out a bit!

I was the head coach of my two older kids’ little league team this past spring.  The whole thing was a little bit of an accident – I vaguely volunteered for something and ended up in charge.  The commitment was a little daunting, but I was ok with it since the season was only a couple months long, it was both Casey and Wilson, and both kids, especially Wilson, are really into baseball.  Other than helping out a bit here and there, I’d never coached a sports team before.

What started off as an unclear assignment ended up as one of the most fun and fulfilling things I’ve done in years.  I loved every minute of it, looked forward to our practices and games, was hugely bummed out when we got rained out, and never had a moment where I couldn’t make the time for it (though clearly the hours had to come from somewhere!).  Given some of the overlap between leading a sports team and leading a company, I thought I’d reflect on the experience a bit here.  There are some common themes between this post and something I wrote years ago, Parenting and Corporate Leadership, with the same caveat that no, I don’t think employees are children or children are employees.  But here are some things I take away from the experience and apply or compare to work.

We established a clear philosophy and stuck to it.  That’s a step that lots of coaches – and managers in the workplace – miss.  The other coaches and I discussed this before the first practice, agreed on it, and shared it directly with the kids.  For this age group in particular, we felt that we were there first and foremost to have fun; second to learn the game; and third, to play hard and fair.  Note there was nothing in this about winning, and that we were really specific about the order of the three objectives.  Even 7 and 8 year olds know the difference between “win at all costs” and “have fun and play ball.”  We reinforced this at every practice and at every game.  Being intentional about a philosophy and communicating it (and of course sticking to it) are key for any leadership situation.

We got lucky.  As I repeatedly said to the parents on the team, we had a group of awesome kids – happy and generally paying attention, and not one troublemaker in the bunch; and we had a group of awesome parents – responsive, supportive, and not a single complaint about what position a kid was playing or where someone was in the batting order.  I’d heard horror stories about both kids and parents from other coaches ahead of time.  It’s possible that the other coaches and I did such a good job that both kids and parents were great all the time…but I think you have to chalk most of that up to the luck of the draw.  Work isn’t all that different.  Having stakeholders who are consistently positive forces is something that sometimes you can shape (you can fire problematic employees) but often you can’t, in the case of customers or even Board members.  Luck matters.

Stakeholder alignment was a critical success factor.  Having said that, I do think the coaches and I did a good job of keeping our stakeholders aligned and focusing on their needs, not ours.  We put extra effort into a regular cadence of communication with the parents in the form of weekly emails and a current web site.  We used those emails to highlight kids’ performance and also let parents know what we’d be working on in practice that week.  We made sure that we rotated kids in the batting order so that everyone got to bad leadoff once and cleanup once.  We rotated kids so that almost every kid played half of each game in the infield and half in the outfield.  We took any and all requests from kids who wanted to play a specific position for a few innings.  Many of these basic principles – communicating well, a clear operating system, listening to stakeholders, a People First approach – are lessons learned from work as a CEO.

Proper expectations and a large dose of patience helped.  After the first couple games, we were 0-2, and I was very frustrated.  But I reminded myself that 7 and 8 year olds are just kids, and my frustration wasn’t going to help us achieve our objectives of having fun and learning the game.  So I recalibrated my expectations and took much more of a laid-back attitude.  For example, any time I saw one kid goofing off a little bit in practice, I gently got him or her back in line.  But when I saw multiple kids’ attention fading, I took it as a sign that whatever I was doing as a coach wasn’t working, called a break, and did something else.  This kind of “look in the mirror” approach is always helpful at work, too.

Reward and recognition were key.  We definitely adopted a Whale Done! approach with the kids.  We got the kids in the dugout fired up to cheer on batters.  First base coaches did big high fives, smiles, and literal pats on the back for every hit.  Post-game huddles and emails to parents focused on highlights and what went right for the kids.  One of my favorite moments of the season was when one player, who only had one hit all year and struck out almost every time at bat, had two hits, an RBI, and a run scored in our final game.  Not just the coaches, but the other kids and all the parents went absolutely BANANAS cheering for this player, and it brought huge smiles to all our faces.  I am 100% certain that the focus on the positive encouraged the kids to try their hardest all season, much as I believe that same philosophy encourages people to take risks and work hard at the office.

The biggest thing I take back to the workplace with me from the experience.  I was reminded about how powerful achieving a state of “flow,” or “relaxed concentration” is.  I recounted these principles in this blog post from a couple different books I’ve read over the years – Mihaly Csikszentmihalyi’s Flow and Tim Gallway’s Inner Game books – Golf, Tennis, and Work.  The gist of achieving a state of flow is to set clear goals that are stretch but achievable, become immersed in the activity, pay attention to what’s happening, and learn to enjoy immediate experience.  All leaders – in sports, business, or any walk of life – can benefit from this way of living and leading.

I loved every minute of coaching.  It helped that we ended up with a really strong record.  But more than that, building relationships with a bunch of great kids and great parents was fun and fulfilling and incredibly thankful and rewarding.  The “thank you ball” that all the kids autographed for me is now a cherished possession.  Working and getting extra time with my own two kids was the icing on the cake.  All I want to know is…is it time for next season yet?  I am ready!

This post is really for Coaches Mike, Paul, and Oliver; and players Emily, Casey, Lauryn, Mike, Josh, Holden, Hudson, Wilson, Drew, Kevin, Matthew, and Christian.

Scaling Frustrations

Two things have come up in spades lately for me that are frustrations for me as a CEO of a high growth company.  These are both people related — an area that's always been the cornerstone of my leadership patterns.  That probably makes them even more frustrating.

Frustration 1:  Worrying that I don't get completely candid feedback from deep in the organization.  I've always relied on direct interactions with junior staff and personal observation and data collection in order to get a feel for what's going on.  But a couple times lately, people had been warning me (for the first time) when I've relayed feedback with comments like, "Of course you heard that — you're the CEO.  People will tell you what they think you want to hear." 

So now the paranoid Matt kicks in a bit.  Can I actually trust the feedback I'm getting?  I think I can.  I always have.  I think I'm a good judge of character and am able to read between the lines and filter comments and input and responses to questions I ask.  But maybe this gets harder as the organization grows and as personal connections to me are necessarily fewer and farther between. I probably need to start recognizing that as the CEO, people may feel uncomfortable being totally open…and it is my job to figure out how to be sure people understand that I do want to hear their voices…unplugged and constructive.

Frustration 2:  Needing to be increasingly careful with what I say and how I say it.  This comes up in two different ways.  First, I want to make sure that while I'm still providing as transparent leadership as I can, that I'm not saying something that's going to freak out a more junior staff member because they're missing context or might misinterpret what I'm saying.  Ok, this one I can manage.

But the tougher angle on this is having unintended impact on people.  Throwing out a casual idea in a conversation with someone in the company can easily lead to a chain reaction of "Matt said" and "I need to redo my goals" conversations that aren't what I meant.  So I'm doing some work to formalize feedback and communication loops when I have skip-level check-ins, but it's creating more process and thought overhead for me than I'm used to.

Nothing is bad here – just signs of a growing organization – but some definite changes in how I need to behave in order to keep being a strong and successful leader.

Book Short: A Marketing-Led Turnaround

Generally, I love books by practitioners even more than those by academics.  That’s why Steve McKee’s first (I assume) book, When Growth Stalls:  How it Happens, Why You’re Stuck, and What to do About It (book, Kindle edition) appealed to me right out of the gate.  The author is CEO of a mid-size agency and a prior Inc. 500 winner who has experienced the problem firsthand – then went out, researched it, and wrote about it.  As a two-time Inc. 500 winner ourselves, Return Path has also struggled with keeping the growth flames burning over the years, so I was eager to dig into the research.  The title also grabbed my attention, as there are few if any business books really geared at growth stage companies.

I’d say the book was “solid” in the end, not spectacular.  Overall, it felt very consistent with a lot of other business books I’ve read over the years, from Trout & Reis to Lencioni to Collins, which is good. The first half of the book, describing the reasons why growth stalls, was quite good and very multi-faceted.  His labeling description of “market tectonics” is vivid and well done.  He gets into management and leadership failings around both focus and consensus, all true.  Perhaps his most poignant cause of stalls in growth is what he calls “loss of nerve,” which is a brilliant way of capturing the tendence of weak leadership when times get tough to play defense instead of offense.

The problem with the book in the end is that the second section, which is the “how to reverse the stall” section, is way too focused on marketing.  That can be the problem with a specialty practitioner writing a general business book.  What’s in the books makes a lot of sense about going back to ground zero on positioning, market and target customer definition and understanding, and the like.  But reversing the stall of company can and usually must involve lots of the other same facets that are documented in the first half of the book — and some other things as well, like aggressive change management and internal communication, systems and process changes, financial work, etc.

At any rate, if you are in a company where growth is stalling, it’s certainly a good read and worth your time, as what’s in it is good (it’s what’s missing that tempers my enthusiasm for it).  In this same category, I’d also strongly recommend Confidence:  How Winning Streaks and Losing Streaks Begin and End, by Rosabeth Moss Kanter, as well.

Please, Let There Be Another Explanation

One of the things I was most excited about with an Obama presidency was that it finally seemed as if we had a real leader in the hot seat.  Someone who might actually be able to run an effective government instead of a bureaucracy paralyzed by partisanship.  I still have this hope.

But I also hope what we’re seeing around the stimulus bill is not what we’re in for the next four years.  What I’m seeing is a complete absence of leadership around the problem.  Seems to me, taking lessons from the corporate world, that Obama should have done two things that would have gotten the program passed in a bipartisan way much more quickly:

1. Build true consensus ahead of time and make the congressional leaders do the sales job in a bipartisan way.  It’s great that Obama went up to the Republican caucus to talk to them and get their point of view, but shouldn’t he have gathered the top 2-3 leaders of each party and each house of congress in his office (or in theirs) to whiteboard this whole thing out ahead of time, so that those people could be bought in and then go on to convince others?  Few successful major corporate initiatives are launched without a careful eye to how all major stakeholders will react so that the majority will be on board.

2. Link the plan to the election in an obvious way.  Obama can credibly claim that the election was a decisive call for change.  He can also credibly claim a small number of priority items that clearly emerged as points of change — reducing/eliminating our dependence on foreign oil, vastly expanded access to health care, reducing taxes on the middle class, and fixing the problem of the revolving door between lobbyists and government as the relevant ones here (there are others around foreign policy and the wars, of course).  Why isn’t the stimulus package pumping money in the economy to the specific ends that were articulated during the campaign, at least for 60-80% of the money, anyway? Seems to me like that’s the best way not just to sell the program to Congress and the American people, but to actually have it stand for something other than 535 people’s pet local projects.  Again, in corporate America, once everyone has agreed on a strategy and goals, it’s much easier to define a path forward around how to execute the details.

I hope something else is going on here — perhaps Obama just wants to make Congress look like a bunch of idiots, so they self destruct and ultimately yield more power to the White House — but my fear is that our new leader needs some lessons in leadership.