The Gift of Feedback, Part IV
The Gift of Feedback, Part IV
I wrote a few weeks ago about my live 360 – the first time I’ve ever been in the room for my own review discussion. I now have a development plan drafted coming out of the session, and having cycled it through the contributors to the review, I’m ready to go with it. As I did in 2008, 2009, and 2011, I’m posting it here publicly. This time around, there are three development items:
- Continue to spend enough time in-market. In particular, look for opportunities to spend more time with direct clients. There was a lot of discussion about this at my review. One director suggested I should spend at least 20% of my time in-market, thinking I was spending less than that. We track my time to the minute each quarter, and I spend roughly 1/3 of my time in-market. The problem is the definition of in-market. We have a lot of large partners (ESPs, ISPs, etc.) with whom I spend a lot of time at senior levels. Where I spend very little time is with direct clients, either as prospects or as existing clients. Even though, given our ASP, there isn’t as much leverage in any individual client relationship, I will work harder to engage with both our sales team and a couple of larger accounts to more deeply understand our individual client experience.
- Strengthen the Executive Committee as a team as well as using the EC as the primary platform for driving accountability throughout the organization. On the surface, this sounds like “duh,” isn’t that the CEO’s job in the first place? But there are some important tactical items underneath this, especially given that we’ve changed over half of our executive team in the last 12 months. I need to keep my foot on the accelerator in a few specific ways: using our new goals and metrics process and our system of record (7Geese) rigorously with each team member every week or two; being more authoritative about the goals that end up in the system in the first place to make sure my top priorities for the organization are being met; finishing our new team development plan, which will have an emphasis on organizational accountability; and finding the next opportiunity for our EC to go through a management training program as a team.
- Help stakeholders connect with the inherent complexity of the business. This is an interesting one. It started out as “make the business less complex,” until I realized that much of the competitive advantage and inherent value from our business comes fom the fact that we’ve built a series of overlapping, complex, data machines that drive unique insights for clients. So reducing complexity may not make sense. But helping everyone in and around the business connect with, and understand the complexity, is key. To execute this item, there are specifics for each major stakeholder. For the Board, I am going to experiment with a radically simpler format of our Board Book. For Investors, Customers, and Partners, we are hard at work revising our corporate positioning and messaging. Internally, there are few things to work on — speaking at more team/department meetings, looking for other opportunities to streamline the organization, and contemplating a single theme or priority for 2015 instead of our usual 3-5 major priorities.
Again, I want to thank everyone who participated in my 360 this year – my board, my team, a few “lucky” skip-levels, and my coach Marc Maltz. The feedback was rich, the experience of observing the conversation was very powerful, and I hope you like where the development plan came out!
The Evolution of Feedback in Our Organizations
Across 22 years and two companies now, our system of giving performance feedback has evolved significantly. I thought I’d take a pass at chronicling it here and seeing if I had any learnings from looking at the evolution. Here’s how things evolved over the years:
- Written performance reviews. The first year of Return Path, we had a pretty standard process for reviews. They were more or less “one-way” (meaning managers wrote reviews for their direct reports), and they only happened annually.
- Written 360 reviews. We pretty quickly moved from one-way reviews to 360s. I wrote about this here, but we always felt that being able to give/receive feedback in all directions was critical to getting a full picture of your strengths and weaknesses.
- Live 360 reviews. In addition to the above post/link, I wrote about this a bit further here and here. The short of it is that we evolved written 360s for senior leaders into facilitated live conversations among all the reviewers in order to resolve conflicting feedback and prioritize action items.
- Live 360 reviews with the subject in the room. I wrote about this here…the addition of the subject of the review into an observer/clarifying role present for the facilitated live conversation.
- Peer feedback. At some point, we started doing team-based reviews on a regular cadence (usually quarterly) where everyone on a team reviews everyone on a team round-robin style in a live meeting.
The evolution follows an interesting pattern of increasing utility combined with increasing transparency. The more data that is available to more people, the more actionable the feedback has gotten.
The pluses of this model are clear. A steady diet of feedback is much better than getting something once a year. Having the opportunity to prioritize and clarify conflicts in feedback is key. Hearing it firsthand is better than having it filtered.
The biggest minuses of this model are less clear. One could be that in round robin feedback, unless you spend several hours at it, it’s possible that some detail and nuance get lost in the name of prioritization. Another could be that so much transparency means that important feedback is hidden because the people giving the feedback are nervous to give it. One thing to note as a mitigating factor on this last point is that the feedback we’re talking about coming in a peer feedback session is all what I’d call “in bounds” feedback. When there is very serious feedback (e.g., performance or behavioral issues that could lead to a PIP or termination), it doesn’t always surface in peer feedback sessions – it takes a direct back channel line to the person’s manager or to HR.
The main conclusion I draw from studying this evolution is that feedback processes by design vary with culture. The more our culture at Return Path got deeper and deeper into transparency and into training people on giving/receiving feedback and training on the Difficult Conversations and Action/Design methodologies, the more we were able to make it safe to give tough feedback directly to someone’s face, even in a group setting. That does not mean that all companies could handle that kind of radical transparency, especially without a journey that includes increasing the level of transparency of feedback one step at a time. At Bolster, where the culture is rooted in transparency from the get go, we have been able to start the feedback journey at the Peer Feedback level, although now that I lay it out, I’m worried we may not be doing enough to make sure that the peer feedback format is meaningful enough especially around depth of feedback!
Book Shorts: Summer Reading
I read a ton of books. Â I usually blog about business books, at least the good ones. Â I almost never blog about fiction or non-business/non-fiction books, but I had a good “what did you read this summer” conversation the other night with my CEO Forum, so I thought I’d post super quick snippets about my summer reading list, none of which was business-related.
If you have kids, don’t read Sheryl Sandberg and Adam Grant’s Option B:  Facing Adversity, Building Resilience, and Finding Joy unless you’re prepared to cry or at least be choked up.  A lot.  It is a tough story to read, even if you already know the story.  But it does have a number of VERY good themes and thoughts about what creates resilience (spoiler alert – my favorite key to resilience is having hope) that are wonderful for personal as well as professional lives.
Underground Airlines, by Ben Winters, is a member of a genre I love – alternative historical fiction. Â This book is set in contemporary America – except that its version of America never had a Civil War and therefore still has four slave states. Â It’s a solid caper in its own right, but it’s a chillingly realistic portrayal of what slavery and slave states would be like today and what America would be like with them.
Hillbilly Elegy, by J.D. Vance, is the story of Appalachia and white working class Americans as told by someone who “escaped” from there and became a marine, then a Yale-educated lawyer.  It explains a lot about the struggles of millions of Americans that are easy for so many of us to ignore or have a cartoonish view of.  It explains, indirectly, a lot about the 2016 presidential election.
Everybody Lies:Â Big Data, New Data, and What the Internet Can Tell Us About Who We Really Are, written by Seth Stephens-Davidowitz, was like a cross between Nate Silver’s The Signal and The Noise and Levitt & Dubner’s Freakonomics. Â It’s full of interesting factoids derived from internet data. Â Probably the most interesting thing about it is how even the most basic data (common search terms) are proving to be great grist for the big data mill.
P.J. O’Rourke’s How the Hell Did This Happen? was a lot like the rest of P.J. O’Rourke’s books, but this time his crusty sarcasm is pointed at the last election in a compilation of articles written at various points during the campaign and after.  It didn’t feel to me as funny as his older books.  But that could also be because the subject was so depressing.  The final chapter was much less funny and much more insightful, not that it provides us with a roadmap out of the mess we’re in.
Sapiens: A Brief History of Humankind, by Noah Harari, is a bit of a rambling history of our species.  It was a good read and lots of interesting nuggets about biology, evolution, and history, though it had a tendency to meander a bit.  It reminded me a bit of various Richard Dawkins books (I blogged a list of them and one related business topic here), so if you’re into that genre, this wouldn’t be bad to pick up…although it’s probably higher level and less scientific than Dawkins if that’s what you’re used to.
Finally, I finished up the fourth book in the massive Robert Caro quadrilogy biography of Lyndon Johnson (full series here). Â I have written a couple times over the years about my long-term reading project on American presidential biographies, probably now in its 12th or 13th year. Â I’m working my way forward from George Washington, and I usually read a couple on each president, as well as occasional other related books along the way. Â I’ve probably read well over 100 meaty tomes as part of this journey, but none as meaty as what must have been 3000+ pages on LBJ. Â The good news: Â What a fascinating read. Â LBJ was probably (with the possible exception of Jefferson) the most complex character to ever hold the office. Â Also, I’d say that both Volumes 3 and 4 stand alone as interesting books on their own – Volume 3 as a braoder history of the Senate and Civil Rights; Volume 4 as a slice of time around Kennedy’s assassination and Johnson’s assumption of power. Â The bad news: Â I got to the end of Vol 4 and realized that there’s a Vol 5 that isn’t even published yet.
That’s it for summer reading…now back to school!
Agile Everywhere, Part II
Over the years, I’ve written a lot about the Agile methodology on this blog. For those of you who are regular readers, you may remember a post I wrote about our Agile Everywhere initiative— where all Return Path teams were tasked with implementing agile practices. A little over a year later, I want to update you on our agile journey–where we are now and how we got there.  My colleague Cathy Hawley (our head of People) will write a more detailed series of guest posts  for those of you who want to get more details of our transformation process.
Before we started our Agile Everywhere initiative, only our product and engineering teams were using agile. The rest of the organization (a few hundred people!) weren’t at all familiar with agile practices. Despite this, there were a few things that helped accelerate our transformation:
- Strong executive buy-in
- A clear vision
- Agile-friendly company culture and values
- A passionate project team
- Resident agile experts
These 5 initial ingredients proved to be essential and enabled us to hit the ground running in Q1 2016. We started out by experimenting with non-technical pilot teams from all different offices, functions, and levels. After a couple months of experimentation, early qualitative results from pilot team members suggested that implementing agile principles was enhancing team communication and productivity. So we embarked on our next step, implementing agile practices across all non-technical teams at Return Path.
We are now 18 months into our transformation and the data shows us that the transformation is helping with our productivity:  we track a  metric that is comprised of many different measures of business performance that fall into 3 main themes–operating efficiency, planning effectiveness, and business success. So far we have already seen a 51% increase in the metric from Q4 2015 (before our Agile Everywhere initiative) to Q1 2017. We are emboldened by these promising results, but still have a lot of work to do to ensure that all teams at RP are taking full advantage of agile and reaping its benefits. Keep an eye out for Cathy Hawley’s posts for more information about our agile adventure, soon to be published the RP blog.
When the series is over, I’ll publish a summary with all the specific post links here as well.
The Gift of Feedback, Part III
The Gift of Feedback, Part III
I’ve written about our 360 Review process at Return Path a few times in the past:
- overall process
- process for my review in particular
- update on a process change and unintended consequences of that process change)
- learnings from this year’s process about my staff
And the last two times around, I’ve also posted the output of my own review publicly here in the form of my development plan:
So here we are again. I have my new development plan all spruced up and ready to go. Many thanks to my team and Board for this valuable input, and to Angela Baldonero (my fantastic SVP People and in-house coach), and Marc Maltz of Triad Consulting for helping me interpret the data and draft this plan. Here at a high level is what I’m going to be working on for the next 1-2 years:
- Institutionalize impatience and lessen the dependency dynamic on me. What does this mean? Basically it means that I want to make others in the organization and on my team in particular as impatient as I am for progress, success, reinvention, streamlining and overcoming/minimizing operational realities. I’ll talk more about something I’ve taken to calling “productive disruption” in a future blog post
- Focus on making every staff interaction at all levels a coaching session. Despite some efforts over the years, I still feel like I talk too much when I interact with people in the organization on a 1:1 or small group basis. I should be asking many more questions and teaching people to fish, not fishing for them
- Continue to foster deep and sustained engagement at all levels. We’ve done a lot of this, really well, over the years. But at nearly 250 people now and growing rapidly, it’s getting harder and harder. I want to focus some real time and energy in the months to come on making sure we keep this critical element of our culture vibrant at our new size and stage
- I have some other more tactical goals as well like improving at public speaking and getting more involved with leadership recruiting and management training, but the above items are more or less the nub of it
One thing I know I’ll have to do with some of these items and some of the tactical ones in particular is engage in some form of deliberate practice, as defined by Geoffrey Colvin in his book Talent is Overrated (blog post on the book here). That will be interesting to figure out.
But that’s the story. Everyone at Return Path and on my Board – please help me meet these important goals for my development over the next couple of years!
Onboarding vs. Waterboarding
Onboarding vs. Waterboarding
One of our new senior hires just said to me the other day that he has been enjoying his Onboarding process during his first 90 days at Return Path and that at other companies he’s worked at in the past, the first few months were more like Waterboarding.
At Return Path, we place a lot of emphasis on onboarding – the way we ask employees to spend their first 90 days on the job. I’ve often said that the hiring process doesn’t end on the employee’s first day. I think about the employee’s first day as the mid-point of the hiring process. The things that come after the first day — orientation (where’s the bathroom?), context-setting (here’s our mission, here’s how your job furthers it), goal setting (what’s your 90-day plan?), and a formal check-in 90 days later — are all make-or-break in terms of integrating a new employee into the organization, making sure they’re a good hire, and making them as productive as possible.
Nothing has a greater impact on a hire’s long-term viability than a thorough Onboarding. Sure, you have to get the right people in the door. But if you don’t onboard them properly, they may never work out. This is where all companies, big and small, fail most consistently. Remember your first day of work? Did you (or anyone at the company) know where you were supposed to sit? Did you (or anyone at the company) know if your computer was set up? Did you (or anyone at the company) have a project ready for you to start on? Did you (or anyone at the company) know when you’d be able to meet your manager? Probably not.
Take onboarding much more seriously, and you’ll be astounded by the results. We have a Manager of Onboarding whose only job is to manage the first 90 days of every employee’s experience. You don’t need to go that far (and won’t be able to until you’ve scaled well past 100 employees), but here are some things you can, and must, do to assure a successful onboarding process:
1. Start onboarding before Day 1. Just as recruitment doesn’t end until Day 90, onboarding starts before Day 1. At Return Path, we ask people to create a “Wall Bio” – a one-page collage of words and images that introduces them to the team – before their first day. It’s a quick introduction to our company culture, and something the rest of our team looks forward to seeing as new people join. Your project can be different, but it’s important to get new hires engaged even before their first day.
2. Set up your new hire’s desk in advance. There is nothing more dispiriting than spending your first day at new job chasing down keyboards and trying to figure out your phone extension. We go to the opposite extreme. When a new hire walks in the door at Return Path, their desk is done. Their computer, monitor and telephone are set up. There’s a nameplate on their office or cube. They’ve got a full set of company gear (T-shirt, tote, etc.). To show how excited we are, we even include a bottle of champagne and a handwritten note from me welcoming them to the company. In the early days of the business, we even had the champagne delivered to the employee’s home after they accepted the offer. (That didn’t scale well, particularly outside of New York City.)
3. Prepare an orientation deck for Day 1. There are certain things about your company that new hires will learn as they go along: nuances of culture, pacing, etc. But there are some things that should be made explicit right away. What is the company’s mission? What are its values? How is the organization structured? What is the current strategic plan? These details are common to every employee, and all new hires should hear them—preferably from the CEO. You can present these details one-on-one to your direct reports, or do larger in-office sessions to groups of new hires over breakfast or lunch.
4. Clearly set 90-day objectives and goals. Other details are going to be specific to an employee’s position. What’s their job description (again)? What are the first steps they should take? Resources they should know about? People they should meet? Training courses to enroll in? Materials to read and subscribe to? Finally, and most importantly, what are the major objectives for their first 90 days? They shouldn’t spend their first quarter “feeling around.” They should spend it actively and intentionally working toward a clear goal.
5. Run a review process at the end of 90 days. Whether you do a 360 review or a one-way performance review, the 90-day mark is a really good point to pull up and assess whether the new hire is working out and fitting culturally as well. It’s much easier to admit a mistake at this point and part ways while the recruiting process is still somewhat fresh than it is months down the road after you’ve invested more and more in the new hire.
With that, the hiring process is done. Now, repeat.
[Note:Â this post contains some passages excerpted from my book, Startup CEO:Â A Field Guide to Scaling Up Your Business, published by Wiley & Sons earlier this fall.]
Collaboration is Hard, Part I
Collaboration is Hard, Part I
Every year when we do 360 reviews, a whole bunch of people at all levels in the organization have “collaboration” identified as a development item. I’ve been thinking a lot about this topic lately and will do a two-part post on this. So, first things first…what is collaboration and why is it so important?
Let’s start with the definition of collaboration from our friends at Wikipedia:
Collaboration is a process defined by the recursive interaction of knowledge and mutual learning between two or more people who are working together, in an intellectual endeavor, toward a common goal which is typically creative in nature. Collaboration does not necessarily require leadership and can even bring better results through decentralization and egalitarianism.
What does that mean in a business setting? It means partnering with a colleague (either inside or outside of the company) on a project, and through the partnering, sharing knowledge that produces a better outcome than either party could produce on his or her own. Interestingly, the last sentence of the definition implies that collaboration can happen across levels in an organization but is generally more effective when the parties who are collaborating are on somewhat equal footing.
Why is collaboration important? There are probably a zillion reasons. Let me take a stab at what I think are three important ones:
- It’s not about hard assets any more. In a knowledge economy/company, sharing information and learnings is critical. And that’s what’s at the heart of the collaborative process. Each person in the organization does a different job; even those who are in the same role have different experiences with their role and different interactions both internally and externally as a result. A collaborative process that by definition involves learning drives the organization forward and to a better place. An example…if you have a deep working knowledge of your product, and your counterpart in marketing has a deep working knowledge of public relations, collaborating on a PR strategy to launch the product’s latest feature means that you will learn more about public relations and your colleague will learn more about your product. In the end, you both get smarter, and the collective intellect of your organization grows — so your company gains incremental advantage over the competition as a result.
- No man is an island. Most functions and business units are in some way interdependent. Think back to the example of product and PR above. Both parties learn through collaboration and make things better for the future. Here’s the rub, though — the collaboration in that example is the only way to produce the right outcome. So the prior point illustrates offense, but this one illustrates defense. Failure to collaborate in this simple case would lead to a misguided PR launch strategy for the new product feature. Either product would dictate the release strategy and text — missing some important subtleties about what reporters will/won’t pick up or without thinking through how different constituencies will react to the messaging — or PR would dictate the release strategy and timing — missing important but subtle points of competitive differentiation in the product features or botching a market-specific window for the announcement.
- Leverage is king. If the first point illustrates offense (collaboration moves the organization forward) and the second one illustrates defense (failure to collaborate suboptimizes the quality of results), this one illustrates productivity (perhaps a subset of offense). Collaboration gives leverage, which in turn gives productivity.  Let’s not pick on our poor product and PR people this time, though. Let’s think about one of the most difficult things to do, which is to hire good people. As I wrote a few years ago in The Hiring Challenge, the three things to do when hiring (which are all hard) are defining the job properly, finding the time to do it right, and remembering that the process doesn’t stop on the person’s first day on the job. So where does collaboration come in? Once your company is big enough to have a good HR person or team, the collaborative approach to having them help you with recruiting is the best option. Sure, you can “throw it over the wall” to HR — give them a job title and location and comp range and see what happens. And you will get some candidates, some of which might be ok. Or you can forget about HR and try to do it yourself and not have time to get it right. Or you can collaborate, bring HR into the discussion about the need for the position, the skills required, and the fit with your organization, even write a job description with HR and discuss which companies or types of companies you want to see on candidates’ resumes — and voila! HR can go off and do 10x the work at 10x the quality. For a little more up-front effort than the “throw it over the wall” approach, you leveraged yourself tremendously through what can be a very time consuming process.
Although my examples are by nature from my own industry for the past 12+ years, it’s hard to think of too many organizations or industries where collaboration isn’t critical to success. Even in companies like investment banks or strategy consulting firms, which traditionally are very hierarchical, command-and-control organizations filled with brilliant individual contributors, the most successful companies (think Goldman Sachs, McKinsey) are the ones that seem to foster more collaboration than others in the development of their people and the development of shared intellectual capital that helps drive the organization forward and ahead of its competition.
In Part II, I’ll answer the title question here…why is collaboration hard? Stay tuned!
More Good Inc.
More Good Inc.
Last year I was pleased and proud to write about our debut on the Inc. 500 list of America’s fastest growing companies. At that time I wrote that “Now our challenge, of course, is STAYING on the list, and hopefully upping our ranking next year!” Well, I am again please and proud to announce that we, in fact, stayed on the list. (You can read all the Inc. coverage here and see our press release about the ranking here.)
Unfortunately, we didn’t make the second part of our goal to up our rank. But, we did up our growth – our three-year revenue growth rate was 18% higher than last year. This is a testament to the hard work of our team (now 150 strong!) and wouldn’t be possible without the support of our many great clients (now 1,500 strong!). Most importantly, we see no end in sight. In fact, 2008 promises to be an even bigger year for us as we poise for continued growth. By the way, would you like to be part of a team that has now ranked as one of America’s fastest growing companies two years in a row? Check out our Careers page and join the team that is advancing email marketing, one company at a time.
Email Intelligence and the new Return Path
Welcome to the new Return Path.
For a tech company to grow and thrive in the 21st century it must be in a state of constant adaptation. We have been the global market leaders in email deliverability since my co-founder George Bilbrey coined that term back in 2002. In fact, back in 2008 we announced a major corporate reorganization, divesting ourselves of some legacy businesses in order to focus on deliverability as our core business. Â
 Since then Return Path has grown tremendously thanks to that focus, but we have grown to the point where it’s time for us to redefine ourselves once again. Now we’re launching a new chapter in the company’s history to meet evolving needs in our marketplace. We’re establishing ourselves as the global market leaders in email intelligence. Read on and I’ll explain what that means and why it’s important.
What Return Path Released Today
We launched three new products today to improve inbox placement rate (the new Inbox Monitor,  now including subscriber-level data), identify phishing attacks (Email Brand Monitor), and make it easier to understand subscriber engagement and benchmark your program against your competition (Inbox Insight, a groundbreaking new solution). We’ve also released an important research study conducted by David Daniels at The Relevancy Group.
The report’s findings parallel what we’ve been hearing more and more recently. Email marketers are struggling with two core problems that complicate their decision making: They have access to so much data, they can’t possibly analyze it fast enough or thoroughly enough to benefit from it; and too often they don’t have access to the data they really need.
Meanwhile they face new challenges in addition to the ones email marketers have been battling for years. It’s still hard to get to the inbox, and even to monitor how much mail isn’t getting there. It’s still hard to protect brands and their customers from phishing and spoofing, and even to see when mail streams are under attack. And it’s still hard to see engagement measurements, even as they become more important to marketing performance.
Email Intelligence is the Answer
Our solution to these problems is Email Intelligence. Email intelligence is the combination of data from across the email ecosystem, analytics that make it accessible and manageable, and insight that makes it actionable. Marketers need all of these to understand their email performance beyond deliverability. They need it to benchmark themselves against competitors, to gain a complete understanding of their subscribers’ experience, and to accurately track and report the full impact of their email programs. In fact, we have redefined our company’s mission statement to align with our shift from being the global leader in Email Deliverability to being the global leader in Email Intelligence:
We analyze email data and build solutions that generate insights for senders, mailbox providers, and users to ensure that inboxes contain only messages that users want
The products we are launching today, in combination with the rest of our Email Intelligence Solution for Marketers that’s been serving clients for a decade, will help meet these market needs, but we continue to look ahead to find solutions to bigger problems. I see our evolution into an Email Intelligence company as an opportunity to change the entire ecosystem, to make email better, more welcome, more effective, and more secure.
David’s researchoffers a unique view of marketers’ place in the ecosystem, where they want to get to, how much progress they’ve made, and how big a lead the top competitors have opened up against the rest. (It can also give you a sense of where your efforts stack up vs. the rest of the industry.) There are definitely some surprises, but for me the biggest takeaway was no surprise at all: The factors that separate the leaders are essentially the core components of what we define as Email Intelligence.
Return Path Core Values, Part II
Return Path Core Values, Part II
As I said at the beginning of this series, I was excited to share the values that have made us successful with the world and to also articulate more for the company some of the thinking behind the statements.
You can click on the tag for all the posts on the 13 Return Path’s core values, but the full list of the values is below, with links to each individual post, for reference:
- We believe that people come first
- We believe in doing the right thing
- We solve problems together and always present problems with potential solutions or paths to solutions
- We believe in keeping the commitments we make, and communicate obsessively when we can’t
- We don’t want you to be embarrassed if you make a mistake; communicate about it and learn from it
- We believe in being transparent and direct
- We challenge complacency, mediocrity, and decisions that don’t make sense
- We believe that results and effort are both critical components of execution
- We are serious and passionate about our job and positive and light-hearted about our day
- We are obsessively kind to and respectful of each other
- We realize that people work to live, not live to work
- We are all owners in the business and think of our employment at the company as a two-way street
- We believe inboxes should only contain messages that are relevant, trusted, and safe
As I noted in my initial post, every employee as of August 2008 was involved in the drafting of these statements. That’s a long post for another time, but it’s an important part of the equation here. These were not top-down statements written by me or other executives or by our People team. Some are more aspirational than others, but they are the aspirations of the company, not of management!
What a View, Part III
What a View, Part III
We are in the middle of our not-quite-annual senior team 360 review process this week at Return Path. It’s particularly grueling for me and Angela, our SVP of People, to sit in, facilitate, and participate in 15 of them in such a short period of time, but boy is it worth it! I’ve written about this process before — here are two of the main posts (overall process, process for my review in particular, and a later year’s update on a process change and unintended consequences of that process change). I’ve also posted my development plans publicly, which I’ll do next month when I finalize it.
This year, I’ve noticed two consistent themes in my direct reports’ review sessions (we do the live 360 format for any VP, not just people who report directly to me), which I think both speak very well of our team overall, and the culture we have here at Return Path.
First, almost every review of an executive had multiple people saying the phrase, “Person X is not your typical head of X department, she really is as much of a general business person and great business partner and leader as she is a great head of X.” To me, that’s the hallmark of a great executive team. You want people who are functional experts, but you also need to field the best overall team and a team that puts the business first with understandings of people, the market, internal dependencies, and the broader implications of any and all decisions. Go Team!
Second, almost every review featured one or more of my staff member’s direct reports saying something like “Maybe this should be in my own development plan, but…” This mentality of “It’s not you, it’s me,” or in the language of Jim Collins, looking into the mirror and not out the window to solve a problem, is a great part of any company’s operating system. Love that as well.
Ok. Ten down, five to go. Off to the next one…