Only Once

• Share
• 12 comments

How to Wow Your Employees

How to Wow Your Employees

Here at Return Path we like to promote a culture of WOW and a culture of hospitality.  Some of you may be asking, Why Wow your employees?   The answer is, there is nothing more inspirational than showing an employee that you care about him or her as an individual.  The impact a WOW has is tremendous.  Being a manger is like being in a fishbowl.  Everything you do is scrutinized by your team.  You lead by example whether you want to or not and showing your own vulnerability/humanity has an amazing bonding effect.

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 and better.

Here are 15 ways to Wow your employees

1. Take them or her to lunch/breakfast/drinks/dinner quarterly individually, one nice one per year
2. Learn their hobbies and special interests; when you have a spiff to give, give one that is in line with these
3. Remember the names of their spouse/significant other/kids/pets
4. Share your development plan with them and ask for input against it at least quarterly
5. Respond to every email from your staff by the end of the day; sooner if you are on the TO line
6. Ask them what they think of a piece of work you’re doing
7. Ask them what they think of the direction the company is going, or a specific project
8. Periodically take something off each one’s plate, even if it’s clearly theirs to do
9. Periodically tell them to take a day off to recharge, ideally around something important in their lives
10. End every meaningful interaction by asking how they are doing and feeling about work
11. End every interaction by asking what you can be doing to help them do a better job and advance their career
12. Read all job openings and highlight ones that match their interests for future positions
13. Read the weekly award list and call out those FROM and TO your team in staff meetings
14. Send a handwritten note to their home when you have a moment of appreciation for them
15. (If your employee has a team he/she manages) Ask for input before every skip-level interaction and summarize each one after the fact in an email or in person

I try to have Wow moments regularly with people at all levels in the organization.  Here’s one that sticks with me.  At the Colorado summer party several years ago, I went up to someone who was a few layers down in the organization and said hi to her husband and dog by name.  I had met them before, and I work at remembering these things.  The husband was blown away – I hadn’t talked to him in probably two years.  In front of the employee, he gushed – “this is exactly why my wife loves working here – we are totally committed to being part of the RP family.”

There are as many ways to be a great manager and WOW your employees as there are stars in the sky…hopefully these ideas give you a framework to make these your own!

• Share
• 2 comments

Book Short: Entrepreneurial Lessons

Book Short:  Entrepreneurial Lessons

The Startup Playbook: Secrets of the Fastest-Growing Startups from 42 Founders, by David Kidder, is the ultimate coffee table book for entrepreneurs and people who are interested in how they think about running their businesses.

David is the author of the Intellectual Devotional series (here’s a link to one of the five or six books in the series), he’s a good friend of mine and a member of a CEO Forum that I’m in, and my major disclosure about this blog post is that I’m one of the 42 entrepreneurs David interviewed for and profiles in the book.

The Startup Playbook is very different from my own book (in progress) on being a Startup CEO.  Where my book is going to go deep on different topics – think of it as a bit of a field guide – David’s book is extremely broad in its coverage of different entrepreneurs and their stories.  Taken together, the book paints a great picture of how CEOs think about the most important parts of the job.  It’s also a nice change of pace (for me, anyway) that David profiles some entrepreneurs who aren’t in the Internet/tech space.

It was an honor to be included in The Startup Playbook next to entrepreneurs like Reid Hoffman and Elon Musk.

• Share
• 5 comments

Taking Stock, Part II

Taking Stock, Part II

Last year, I wrote about the three questions I ask myself at the beginning of every year to make sure my career is still on track. [http://www.onlyonceblog.com/2012/01/taking-stock]   The questions are:

1. Am I having fun at work?
2. Am I learning and growing as a professional?
3. Is my work financially rewarding enough, either in the short term or in the long term?

This year, I am adding a fourth suggestion following a great conversation I had a bunch of months back with Jerry Colonna, a great CEO coach, former VC, and all around great person.  Question four is:

Am I having the impact I want to have on the world?

This last question was probably always implicit in my first two questions – but I like calling it out separately.  All of us have purpose in our lives and impact on others, whether it’s family, friends, colleagues, clients, or some slice of broader humanity.  Asking whether that impact is present and enough is just another check and balance on my own operating system to make sure that I’m still on track with my own goals and values.

Happy New Year!

• Share
• 10 comments

Startup CEO (OnlyOnce- the book!), Part II – Crowdsourcing the Outline

Startup CEO (OnlyOnce- the book!), Part II – Crowdsourcing the Outline

As I mentioned a few weeks ago here, I’m excited to be writing a book called Startup CEO:  A Field Guide to Building and Running Your Company, to be published by Wiley & Sons next summer.  Since many readers of OnlyOnce are my target audience for the book, I thought I’d post my current outline and ask for input and feedback on it.  So here it is, still a bit of a work in progress.  Please comment away and let me know what you think, what’s missing, what’s not interesting!

1           Part One: Vision and Strategy (Defining the Company)
1.1          Setting the Company’s Agenda
1.2          NIHITO! (or, “Nothing Interesting Happens in the Office”)
1.3          Setting the Business Direction
1.4          Strategic Planning, Part I: Turning Concepts Into Strategy
1.5          Strategic Planning, Part II: Creating the Plan
1.6          Defining Mission, Vision and Values
1.7          Communicating Vision and Strategy
1.8          The Role of M&A
1.9          The Art of the Pivot
1.10       How Vision and Strategy Change over Time

2           Part Two: Talent (Building the Company’s Human Capital)
2.1          Building a Team
2.2          Scaling the Team
2.3          Culture
2.4          Interviewing
2.5          Recruiting
2.6          Onboarding
2.7          Setting Goals
2.8          Feedback
2.9          Development
2.10       Compensation
2.11       Promoting
2.12       Rewarding
2.13       Managing Remote Offices and Employees
2.14       Firing: When It’s Not Working
2.15       How Talent Changes over Time

3           Part Three: Execution (Aligning Resources with Strategy)
3.1          Making Sure There’s Enough Money in the Bank
3.2          Types of Financing
3.3          Fundraising Basics
3.4          Negotiating Deals
3.5          Pros and Cons of Outside Financing
3.6          Forecasting and Budgeting
3.7          Creating a Company Operating System
3.8          Meeting Routines
3.9          Driving Alignment
3.10       A Metrics-Driven Approach to Running a Business
3.11       Learning
3.12       Post-Mortems
3.13       Thinking About Exits
3.14       How Execution Changes over Time
3.14.1      Finance
3.14.2      Execution

4           Part Four: Management And Leadership (The How of Being a CEO)
4.1          Leading an Executive Team
4.2          Critical Personal Traits
4.3          Being Collaborative
4.4          Being Decisive: Balancing Authority and Consensus
4.5          The Value of Symbolism
4.6          Getting the Most out of People
4.7          Diving Deep without Being Disruptive
4.8          Articulating Purpose
4.9          Collecting Data from the Organization
4.10       Managing in an Economic Downturn
4.11       Managing in Good Times vs. Bad Times
4.12       Communication
4.12.1      Macro (to Your Company and Customers)
4.12.2      Micro (One-on-One)
4.13       How Management and Leadership Change over Time

5           Part Five: Boards (A Unique Aspect of the CEO’s Job)
5.1          Building Your Board
5.2          Meeting Materials
5.3          Meetings
5.4          Between Meetings
5.5          Making Decisions and Maximizing Effectiveness
5.6          The Social Aspects of Running a Board
5.7          Working with the Board on Compensation
5.8          Evaluating the Board
5.9          Serving on Other Boards
5.10       How Boards Change over Time

6           Part Six: Managing Yourself So You Can Manage Others
6.1          Creating a Personal Operating System
6.2          Working with an Executive Assistant
6.3          Working with a Coach
6.4          Finding Your Voice
6.5          The Importance of Peer Groups
6.6          Your Family
6.7          Taking Stock
6.8          Staying Fresh
6.9          Staying Healthy
6.10       Traveling

• Share
• 2 comments

A New VC Ready to Go!

A New VC Ready to Go!

One of the interesting things about being in business for 13 years (as of last week!) at Return Path is that we have been around longer than two of our Venture Capital funds.  Fortunately for us, Fred led an investment in the company with his new fund, Union Square Ventures, even though his initial investment was via his first fund, Flatiron Partners.  And even though Brad hasn’t invested out of his new fund, Foundry Group, he remains a really active member of our group as a Board Advisory through his Mobius Venture Capital investment.

Although our third and largest VC shareholder, Sutter Hill Ventures, is very much still in business, our Board member Greg Sands just announced today that he has left Sutter and started his own firm, Costanoa Venture Capital, sponsored in part by Sutter.  The firm was able to buy portions of some of Greg’s portfolio companies from Sutter as part of its founding capital commitment, so Return Path is now part of both funds, and Greg, like Fred, will continue to serve as a director for us and manage both firms’ stakes in Return Path.

The descriptions of the firm in Greg’s first blog post are great – and they point to companies like Return Path being in his sweet spot:  cloud-based services solving real world problems for businesses, Applied Big Data, consumer interfaces and distribution strategies for Enterprise companies.

I give Greg a lot of credit for going out on his own with a strong vision, something that’s unusual in the VC world.  We’re proud to be part of his new portfolio, and I’m sure he’ll be incredibly successful.  Like Fred and Brad and their new firms, Greg understands the value of being able to write smaller initial checks and back them up over time, he is a disciplined investor, and he is a fantastic Board member and mentor.

• Share
• 0 comments

Book Short: Culture is King

Book Short:  Culture is King

Tony Hsieh’s story, Delivering Happiness (book, Kindle), is more than just the story of his life or the story of Zappos. It’s a great window into the soul of a very successful company and one that in many ways has become a model for great culture and a great customer service model.  It’s a relatively quick and breezy read, and it contains a handful of legendary anecdotes from Zappos’ history to demonstrate those two things — culture and customer service — in action.

As Hsieh himself says in the book, you can’t copy this stuff and believe it will work in your company’s environment as it does in Zappos’.  You have to come up with these things on your own, or better yet, you have to create an environment where the company develops its own culture and operating system along the broad lines you lay out.  I think Return Path has many similarities with Zappos in how we seek out WOW experiences and in our Core Values, as well as the evolutionary path we took to get to those places.  But as much as I enjoyed reading about a like-minded company, I also recognized the specific things that were different and had a good visceral understanding as to WHY the differences exist.

It is the rare company that gets to $1 billion in revenue ever – let alone within a decade.  For that reason alone, this is a worthwhile read.  But if you are a student of organizational culture and believe in the power of values-driven organizations, this is good affirmation and full of good examples.  And if you’re a doubter of the power of those things, this might just convince you to think twice about that!

• Share
• 4 comments

The Value of Paying Down Technical Debt

The Value of Paying Down Technical Debt

Our Engineering team has a great term called Technical Debt, which is the accumulation of coding shortcuts and operational inefficiencies over the years in the name of getting product out the door faster that weighs on the company’s code base like debt weighs on a balance sheet.  Like debt, it’s there, you can live with it, but it is a drag on the health of the technology organization and has hard servicing costs.  It’s never fun to pay down technical debt, which takes time away from developing new products and new features and is not really appreciated by anyone outside the engineering organization.

That last point is a mistake, and I can’t encourage CEOs or any leaders within a business strongly enough to view it the opposite way.  Debt may not be fun to pay off, but boy do you feel better after it’s done.  I attended an Engineering all-hands recently where one team presented its work for the past quarter.  For one of our more debt-laden features, this team quietly worked away at code revisions for a few months and drove down operational alerts by over 50% — and more important, drove down application support costs by almost 90%, and all this at a time when usage probably doubled.  Wow. 

I’m not sure how you can successfully scale a company rapidly without inefficiencies in technology.  But on the other side of this particular project, I’m not sure how you can afford NOT to work those ineffiencies out of your system as you grow.  Just as most Americans (political affiliation aside) are wringing their hands over the size and growth of our national debt now because they’re worried about the impact on future generations, engineering organizations of high growth companies need to pay attention to their technical debt and keep it in check relative to the size of their business and code base.

And for CEOs, celebrate the payment of technical debt as if Congress did the unthinkable and put our country back on a sustainable fiscal path, one way or another!

As a long Post Script to this, I asked our CTO Andy and VP Engineering David what they thought of this post before I put it up.  David’s answer was very thoughtful and worth reprinting in full:

 I’d like to share a couple of additional insight as to how Andy and I manage Tech Debt in the org: we insist that it be intentional. What do I mean by “intentional”

•  There is evidence that we should pay it
• There is a pay off at the end

 What are examples of “evidence?”

•  Capacity plans show that we’ll run out of capacity for increased users/usage of a system in a quarter or two
• Performance/stability trends are steadily (or rapidly) moving in the wrong direction
• Alerts/warnings coming off of systems are steadily or rapidly increasing

 What are examples of “pay off?”

•  Increased system capacity
• Improved performance/stability
• Decreased support due to a reduction in alerts/warnings

 We ask the engineers to apply “engineering rigor” to show evidence and pay-offs (i.e. measure, analyze, forecast).

 I bring this up because some engineers like to include “refactoring code” under the umbrella of Tech Debt solely because they don’t like the way the code is written even though there is no evidence that it’s running out of capacity, performance/stability is moving in the wrong direction, etc. This is a “job satisfaction” issue for some engineers. So, it’s important for morale reasons, and the Engineering Directors allocate _some_ time for engineers to do this type of refactoring.  But, it’s also important to help the engineer distinguish between “real” Tech Debt and refactoring for job satisfaction.

• Share
• 0 comments

Not Just About Us

Not Just About Us

When we updated our values this year, we felt there were a couple critical business elements missing from this otherwise “how” series of statements.  One thing missing was our clients and users!  So we added this value to our list:

Not Just About Us:  We know we’re successful when our clients are successful and our users are happy.

This may be one of the most straightforward statements of all our values, so this will be a short post.  We serve lots of constituencies at Return Path.  And we always talk about how we’re a “People First” organization and what that means.  I suppose that inherently means we are a “Client Second” organization, though I’m not sure we’d ever come out and say that.  We do believe that by being People First, we will ultimately do the best job for our customers. 

 That said, we aren’t in business just to build a great company or to have an impact on our community.  Or even our shareholders.  We are also in it for our customers.  Whether we are producing a product for mailers, for ESPs, for ISPs, for security companies, for agencies, or for end users, we can’t forget that as an important element of our success every day.

• Share
• 6 comments

Book Short: The Challenger Sale

Book Short: The Challenger Sale

I’ve written a couple times in the past about how we sell at Return Path.  I’ve written about our principle sales methodology for the past decade, SPIN Selling, by Neil Rackham (and Major Account Strategy, also by Rackham, which is basically SPIN Selling for Account Managers), which focuses on a specific technique for solution selling by using questioning to get the prospective client to identify his or her own needs, as well as Jeffrey Gitomer’s two short books, the Little Red Book of Selling and Little Red Book of Sales Answers, which are long on sales questioning techniques.  And I also wrote this post about another book called Why People Don’t Buy Things, by Kim Wallace and Harry Washburn.  The great thing about this book is that it dives into the need for variation in sales communication strategies based on BUYER personae, such as The Commander, The Thinker, and The Visualizer.

While both these principles are good – asking questions and tailoring communication styles based on the buyer – anyone who has ever tried to run a whole sales call by asking questions knows that it’s REALLY HARD and can sometimes just outright flop.  There’s a new movement that I’ve been reading articles about for a few months now called The Challenger Sale, and I finally finished the book about it this past week.

If you run a company or a sales team that has any kind of complex sale or a hybrid software/service model, then you should read The Challenger Sale: Taking Control of the Customer Conversation, by Matthew Dixon and Brent Adamson.  Whether you adopt the methodology or not, there are a few really great insights in the book that will help you recruit and manage a sales team.  Some of the insights include:

• Understanding the five types of sales reps and why/when they’re successful/not successful.  The labels are telling in and of themselves:  the Lone Wolf, the Hard Worker, the Relationship Building, the Reactive Problem Solver, and the Challenger
• Why sales reps can be trained as Challengers, and how important it is to rally an entire organization around this sales model, not just train sales reps on it (that’s probably a good reminder for any sales methodology)
• The ingredients of the Challenger sale – Commercial Teaching for Differentiation, Tailoring for Resonance, Taking Control of the Conversation.  I found the section on Commercial Teaching the most enlightening, particularly in our business, where we’re not selling an established category with established budget line items

The Challenger Sale feels like the beginning of a wave that will take over a lot of selling organizations in the next decade, either directly as written or as it inspires ancillary works and related techniques.  For that reason alone, it’s worth a read.

• Share
• 2 comments

Two Ears, One Mouth

Two Ears, One Mouth

Brace yourself for a post full of pithy quotes from others.  I’m not sure how we missed this one when drafted our original values statements at Return Path years ago, because it’s always been central to the way we operate.  We aren’t just the world’s biggest data-driven email intelligence company – we are a data-driven organization.  So another one of our newly written Core Values is:

Two Ears, One Mouth:  We ask, listen, learn, and collect data.  We engage in constructive debate to reach conclusions and move forward together.

I’m not sure which of my colleagues first said this to me, but I’m going to give credit to Anita, our long-time head of sales (almost a decade!), for saying “There’s a reason God gave you two ears and one mouth.”  The meaning?  Listen (and look, I suppose) more than you speak.

This value really has two distinct components to it, though they’re closely related.  First, we always look to collect data when we need to understand a situation or make a decision.  To quote our long-time investor, Board member, and friend Brad Feld, “the plural of anecdote is not data.”  That means we are always looking far and wide for facts, numbers, and multiple perspectives.  Some of us are better than others at relying on second-hand data and observations from trusted colleagues, which means often times, many of us are collecting data ourselves to inform a situation.  But regardless, we always start with the data.

Second, we use data as the foundation of our decision-making process.  I heard another great quote about this once, which is something like, “If we are going to make a decision based on data, the data will make the decision for us.  If we’re going to use opinion, let’s use mine.”  And while I’m at it, I’ll throw in another great quote from Winston Churchill who famously said “Facts are stubborn things.”  While we do have constructive debates all across our organization, those debates are driven by facts, not emotion.

Finally, when this value says that “we move forward together,” that is the combination of the points in the two prior paragraphs.  People may have different opinions entering a debate.  Even with a lot of data behind a decision, they may still have different opinions after a decision has been made.  But we work very deliberately to all support a decision, even one we may disagree with, and we are able to do that, move forward together, and explain the decision to the organization, because the decision is data-driven.