Archive for the ‘Failure’ Category

What I’ve Learned Over a Career

September 19, 2019

By Peter Zaballos

Reflections Upon Retiring

I have officially “stopped working,” which is a way of avoiding saying I have retired. I’m still active on two technology company boards. Still very much on a number of near-vertical learning curves.

But leaving my professional role has caused me to look back. And looking back, it’s easy to see and feel what was meaningful — and what wasn’t — in 30+ years of building high-growth technology companies. Let’s start with what wasn’t.

What wasn’t meaningful were the financial and business milestones I had a hand in achieving,  because business metrics are outcomes — of strategy, execution, and culture — but they aren’t the end in themselves. They’re the means to an end. I helped three companies change the very shape of computing, and only one of these companies — LSI Logic — had the winning trifecta of brilliant strategy, incredible execution, and a culture of compassion and performance. C-Cube Microsystems and RealNetworks failed miserably on culture.

And along the way I met some incredible, incredible people. People with staggering intellect and, most importantly, people with huge hearts and abundant generosity. But I also met a lot of people with none of those qualities. And who seemed to become quite successful as well. That was puzzling and frustrating.

And the long hours I put into my different roles? Not a lot of meaning there. As a matter of fact, the further into my career I got, and the higher I rose in the executive ranks, the more jaded I became at the devotion to long hours. 

I wish I could have told this to my younger self, especially when my wife and I were in the thick of raising four children born over a span of five years. A few years ago, when I was at SPS Commerce, I heard a sales rep tell a group of people they had cut their honeymoon short by two days, at the insistence of their manager, to attend a meeting. As I sat there I thought — with the benefit of hindsight — that no meeting would be worth cutting your honeymoon short.

[And it told me about the real culture at that company. Not the one written down. More on this topic further down.]

And on a related note, I also grew weary of the need to always being “hard core” about competing, about winning, almost for winning’s sake, of what in the end were ephemeral competitions.

But when I think back to what was meaningful, it really came down to this: being in a position of power and authority to create the conditions where the people that worked for me could do their best work and discover their best selves. To set the tone, to shape the culture. To be able to actively work to achieve equality in the departments I led. And to be a voice on an exec team pushing for equality across the companies I worked at.

Equality created lasting effects for the people on my teams, and is the polar opposite of a business metric. The people on my teams were able to achieve and exceed business metrics/targets because they could be valued for their contributions. 

The first time I noticed inequity in a specific case was when I was at RealNetworks in 1999 — having joined through their acquisition of Vivo Software — and I inherited a department to run. The first homework I gave myself was to look at compensation across my teams, by role and by gender. I discovered one woman was paid substantially less than her male counterparts. 

It took almost a year of fighting process and bureaucracy to “true-up” this woman’s compensation. And it started me doing a similar analysis in every leadership role I had after that. But that was super tactical, from ground level looking skyward.

I think the first time I realized the impact I could have on equality and culture from the top down was when I wrote my first user manual when I was an exec at SPS Commerce. This simple document simply outlined what I expected of myself, my peers, and the people on my teams. 

Feel free to check out my User Manual

It was the act of writing this document where it dawned on me that not only did I have the ability to set a tone of equality in the orgs I led, but that I had an obligation to my teams and to myself to do so. I was literally kind of giddy over the next few months.

The flip side is that it was sobering to realize how much opportunity I took for granted as a man that women had to work for, fight for, or just resign themselves to never having. And I discovered this because once it became clear for my teams that our values and culture were real, the results were shocking:

  • That the  woman on my team (quote is above, sent to me and her manager) thanked me for making her feel comfortable and empowered to take time off to attend her kindergartner’s graduation.
  • I have had a woman tell me I was the first executive to tell her that taking care of her health in her very stressful role is more important than her job.
  • I have had a male boss ask me, every single time a woman on my team was pregnant, “Do you think she’s going to come back after maternity leave?” He never once asked me that question about any of the men on my team whose wives were pregnant.
  • On the day when we finally (after weeks and months of proposing this) had “equality” on the exec staff agenda, I had our male CEO open the discussion with “Well, I assume if we had an all-female leadership team that would be sexist.”
  • I have seen women on my teams treated like servants by men who were their peers — asked to literally get coffee for the men or rebook their hotels with better rooms when they were traveling as a group.

I have also seen people make amazing contributions and incredible achievements in their roles, when provided the conditions to be their best.

  • I witnessed a shy, unsure of-herself customer service rep make the huge leap into product management and then, over a period of 18 months, turn into a bad-ass, decisive, confident product manager responsible for more than half the company’s revenue.
  • I witnessed a woman who had previously sold cell phones at a Verizon store become a master of marketing and digital demand gen and, as a result, was headhunted to be a marketing executive at another high-growth technology company today.
  • I had the good fortune to hire two phenomenally talented product designers, one in his first role designing software. And by giving these people the freedom to follow their creative instincts, create a culture of design excellence that produced truly delighted users of their products.
  • I witnessed a two-member team apply record-breaking amounts of curiosity to become masters at digital marketing through constant reinvention and data-driven refinement. 
  • I hired a brilliant person from a shoe company into his first full role in marketing. He left a year later to go back to the shoe industry and has so far reinvented two blockbuster, multi-billion dollar international footwear brands.
  • My partners at Frazier Technology Ventures – Len Jordan, Scott Darling, Paul Bialek, and Gary Gigot – discovered that when we stripped away our egos we could have direct, blunt conversations about decisions we were making. This set the standard for me valuing the lack of ego as a chief hiring criteria.

What have I regretted? Well, I mentioned above, working long hours in the end just took time away from my family, and I really can’t point to a meaningful source of business satisfaction that makes up for that. Other regrets:

  • That I did not listen to that little voice inside me when I had to fire people — or ask them to leave — because they were not performing or were not able or willing to live up to the expectations for conduct I had for them. That little voice said to go the extra mile, to fight with HR and in some cases the CEO, to get these people a package that would let them leave gracefully.
  • That I did not listen to that little voice inside me and instead followed the advice of others in letting people go with the bare legal minimum in notice, disclosure, and dialogue. I expect those people left my departments feeling they were not treated with the respect they deserved, and earned, through trying as hard as they could.
  • That I did not put my own job at risk more often pushing for more equality as a company, pushing the CEO and leadership team to take a more difficult but right path. This is where hindsight really stings — when I can see I was right but was afraid or buckled under pressure.

What else I’ve learned along the way:

  • Your brand – personally and as a business – is built on how well you say “no.” You say no 10 time more than you say yes. Doing a good job saying no means you are creating 10 times as many positive word-of-mouth evangelists. It also means you keep your focus on empathy and humility.
  • And since you say no much more than you say yes, you’ll spend time with people who you won’t say yes to. Learn to give more than you take when you do this. Help them some other way. Introduce them to someone else who can help. Offer wisdom and experience.
  • Treating people well on the way out the door is as important as it is rare. Being generous to people you fire, who decide to leave to advance their career, or who are just not a good fit matters. A lot. It is shocking how rarely I have been supported by HR leaders and CEOs on this topic.
  • How a company treats the behavior of their salespeople and developers defines the culture, not the “values” that are written down. I have seen sales people lie (to customers, to me, to other employees) but suffer no consequences because they “deliver.” Same for developers. That corrodes the culture and causes the high-value talent to leave.
  • How a company handles equality defines the culture, again regardless of what “values” are written down. It takes real bravery to foster equality in a culture. It is always easier to let fear cause a company to tolerate harassment. We need more bold, brave leaders. We absolutely need more women leaders. And leaders of color. And leaders from other cultures.

So at the end of this phase of my professional life, I would say that what mattered, what was meaningful, what was important was creating conditions for people to be their best selves. And that how you treat people matters, enormously.

What’s next for me? I’m on the board of two tech companies in Boston and am for sure going to continue stay on steep learning curves there. 

And my wife and I are launching a program at Diablo Valley College (the community college I attended)  to help under-performing, high-potential students find their path (more on that in an upcoming blog post). 

I’m attending community college myself to learn Spanish. 

And I am learning to drive race cars

But most of all, I am going to keep learning to be better. At everything I do and am. If I learned anything from 30+ years building high-growth tech companies, it’s that you can always be better. You can always learn.

Looking through the turn

June 24, 2019

By Peter Zaballos

I recently started learning to drive a race car, something I’ve always dreamed of doing. 

With the encouragement and support of my wife and all four children, I began taking high-performance driving classes at one of the best driving schools in the country, in Kent, Washington. And I wanted to share what I am learning there, because I’ve discovered that driving a car fast on a race course is a lot like making your way through a career or through life.

When you’re driving a race car, one of the first skills you learn is to “look through the turn.” It’s the habit of having your eyes focused on where you want the car to go, not where it is right now. And it’s super pragmatic. 

When you’re driving a car at high speed, whatever is in front of you is coming at you so fast that if a correction is needed, that correction needed to take place seconds earlier. You literally can’t fix the problem at that point. When your eyes are focused on what’s directly in front of you, it’s called “driving from the hood of the car.” Best case, you’re going to exit that turn slowly, poorly positioned for the next turn. Worst case — you’re going to drive off the track.

So you’re instructed to split your field of view, with the majority of your vision focused far down the road and only your peripheral vision tracking the close-up things. Sometimes that turn ends over your shoulder, so you go into the turn literally looking out the side window while the car is barreling forward through the turn.

And it gets harder still because you really do need to keep track of close-up things coming at you. There is a point where you need to start the turn — called the “turn-in-point” — where you stop going straight down the track and you turn the wheel. You need to do your braking before this point because you can’t brake hard and turn at the same time (and you need to brake hard to get your speed down).

When you turn in, you need to arc the curve of your path to hit the part of the corner that will produce the largest radius turn you can trace — a larger radius means higher speed — so you are also tracking for that critical spot that ensures you are carrying the maximum speed through the turn. You need a telltale mark for this “apex” point.

Finally, as you exit the turn you need to aim for a spot that finishes that largest radius turn you initiated way back at the turn-in-point. This is called the “track-out” point.

And this is not just about that one turn you just negotiated. It’s about considering the entire track and all of its turns and how you think about what will produce the lowest overall time through the course. It could very well hurt your overall lap time to go through a particular turn super fast, because it could send you into the next turn poorly positioned.

At driving school, there’s a traffic cone conveniently placed at the turn-in, apex, and track-out points. But in racing — as in life, of course — there are no cones at these telltale points.

So for every turn on a track, you need to memorize some physical object — a visible patch of dirt, a tree on the horizon, even a porta-potty off to the side of the track — to help you know when to turn in, where the apex is, and where to end your turn. The chief instructor of the school, Don Kitch, has raced in the 24 Hours of LeMans, and said it took him and his two co-drivers a year to prepare for it. They took hundreds of photos so they would know the key telltales of every turn on the track.

Everything I just described about learning to drive a car on a racetrack is also true of navigating your career and living your life. Keep your vision fixed on the long term, but be intentional and precisely aware of the tell-tales along the way.

From a career perspective, every turn on the track is like each job or role you have. The goal is to decide when to take that job, how to maximize your “radius” through it so that you construct the most impactful and rewarding career, and when to “track out” for your next opportunity. 

It’s not about maximizing the results from any one role, but being very intentional about how your progression of roles link and make sense together. It’s why focusing just on compensation or a title for that next job may not, in fact, set you up for the role you really want, two or three career moves later.

So, on the track and in your career, look through the turn.

Unthinking Power and Authority

September 4, 2018

by Peter Zaballos

This past week my wife and I moved our youngest of four children to college – totally fun and a momentous occasion for the three of us, and the family as a whole. And it was an awkward, even painful learning moment for me in how easy it is for men to assume positional authority and ignore better input from women.

Image result for not being listened to

In this case, we were moving our son into a college outside New York, and wisely chose to fly there instead of doing the 14+ hour drive (which we have done one too many times with one of his older brothers and older sister). We landed at JFK and I picked up a rental car and headed to campus. I grew up in California and am definitely a product of that state’s car culture – I don’t mind driving at all, I kind of like it. And having spent 10 years living in Boston, I also have gotten completely comfortable in driving amidst the aggressive chaos that is northeast urban auto jostling.

I now travel with a phone case that plugs into the dashboard, so am good about getting our coordinates in Google and letting that take the load of getting us from starting point to destination. Early on Google had a disclaimer on their directions that said something like “do a reality check before following these instructions” and that is precisely where I ran afoul of getting us from where we started to where we needed to go.

My wife on the other hand is confidently old school. When we travel the first thing she grabs is a printed map. She is as awesome at orienting herself with a map as she is adept at using it to explore and get to the destination. We’ve taken some wonderful vacations where her annotated and highlighted paper map of where we went and what we explored is such a rich record of time well spent.

What made this drop off at college different from the other three is that my wife and son had been to the campus earlier in the year and spent a fair amount of time exploring it and getting to know it. And there was me with Google and at the wheel of the car striving to get us to where we needed to go from Google’s perspective. And that’s where the humbling learning moment for me started to take its slow motion trajectory.

As we got closer to the campus I was following Google and my wife was following her experience and astute sense of memory and direction. As we got to the campus I was trying to find what Google was telling me to look for, and my wife was telling me what she knew from experience and her sense of direction. I effectively ignored her until it was too late. And I can try and explain why “ignore” was not really ignore, but this is where it doesn’t matter what I feel or think, but what she does, because she is on the receiving end.

The analogy I will use here is as spot-on as it is uncomfortable. If a woman feels she has been harassed, it really doesn’t matter what the harasser feels or how they interpret the circumstances. The sole “owner” of that perspective is the one on the receiving end.

But what ended up happening was a fairly tense exchange that shut us both down in the moment. Her lingering frustration later caused her to have to speak up and effectively justify why she should have been listened to and considered. And me trying to justify my behavior around being focused on getting to the “destination.” – which in hindsight is ridiculous.

From her perspective she was put in the position of (a) having better information and (b) having her better information ignored and dismissed. Sound familiar women?

But at the time I had both position (I was the driver) and authority (google maps) – and we were conditioned that when we drove places it was my position and authority that made the final decisions. Nothing malicious here, but over time, it put me in the position of being the decider. And in this case, I sure was deciding. And my wife was sure feeling not listened to or considered.

At the time neither of us realized any of this. We both just shut down and simmered. Until we found the right parking lot, and our attention conveniently shifted to this wonderful day and our son’s new adventure at college. We avoided the fact that if I had been listening to her we would have been where we were supposed to be sooner, with less stress, and more focus on our son’s first day at college – which for she, me, and him was such a wonderful, wonderful moment to savor.

It wasn’t until much later that night, after we had flown back home and were on our way (with me driving) from the airport to our house. It was then my wife brought up the whole experience. And it was through the process of unpacking the issue that we both reached a point where we able to focus on how each of us felt, which is where the real conversation happened.

We talked about how we became conditioned to me being the driver over time and that there were a few ways to address this. One might be her driving more when we are together, especially when she knows the terrain more. Which is a good alternative, but to me feels a bit “brute force.” Switching the position and the authority. To me the real solution is creating the conditions where I listened to hear and she could feel heard. That’s the harder solution.

I take women’s equality seriously. Yet here I was, repeating a pattern of male behavior and causing my wife to repeat a pattern of feeling ignored or dismissed. It was pretty easy to respond so unthinkingly – isn’t that the opposite of thoughtfully?

And it made me consider how hard it is to create the conditions where these kind of conversations can take place. In most workplaces women don’t get that safe place to share their thoughts like this and be vulnerable. They just learn to deal with being dismissed and not heard. We have to be able to do better than this.

Because in those moments, the focus needs to be on how to get to the destination as efficiently as we can – whether a marketing campaign or an algorithm – and savor the moment of why we are all together, working on a common goal.

 

There is no “career path,” just a network of relationships

March 30, 2018

And how you get from one adventure to the next

A few weeks ago I was asked to give a talk at the University of Wisconsin-Whitewater College of Business and Economics, on the subject of career paths. And the title of my talk was “There Is No Career Path.”

I wasn’t all that that creative. Steve Jobs made this point in his Stanford Commencement speech in 2011, six years before he died. His point was that a career path is only visible in hindsight. The “path” is produced by following your interests and talents. But I want to take that a step further.

My observation is that your career is a product of the relationships you develop along the way in your job along with following your interests and your talents. Notice I didn’t say college alumni networks. One of the points I made to the UWW students was I attended two of the top five universities in the world (Berkeley and MIT), and my alumni networks have produced zero jobs for me.

Networking

But the relationships I developed at LSI Logic, at C-Cube Microsystems, at RealNetworks, and as a venture capitalist at Frazier Technology Ventures have produced six incredible jobs, and have formed the foundation of my career.

When you unpack “relationships” there’s a lot to examine. For me, relationships are formed by establishing trust and credibility with the people you work with and for. And you do that by doing what you said you would do. By speaking your mind. By being honest. By acting with integrity. By being in a culture that aligns with your values.

Your network of relationships is fundamentally about about your personal brand.

That’s right, your personal brand is made up of the people you work with. How well you communicate to them. How well you support others. And that all involves . How you treat them. Those experiences, those memories persist. They’re your personal brand.

Finding the next adventure

And here I am, at another juncture where I am about to move to my next adventure. I left my role as CMO at SPS Commerce in early January, to return to Seattle. Family reasons draw us there, and I really wanted to get back to my roots – building category-creating technology companies.

And it’s this network of relationships that is guiding me. Which made me think of another set of conversations I’ve been having with folks I know – about how instrumental these relationships are to discovering your next adventure.

I’ve been employing the method that has propelled me to where I am now, and which I know will get me to where I want to be next. It involves four activities:

Hone your story – What this means is having clarity about what it is you want to do and what you’ve done to prepare you for this, and it’s being sober and humble about what you’re really good at. And finally, it’s about being compelling about why this next adventure is right for the role and for you – and for whoever it is you will work for.

“Your story” is what you say after you meet someone, you exchange pleasantries, and there’s a pause. You then tell the story. Why you’re there with them, why there is context, and you paint a picture of your future that they might be able to help you with.

Lots of conversations – This is the foundation of the process. This is where you start speaking to lots of people who might be able to help sharpen your focus, sharpen your story (you’ll be telling that to them), and who might know someone else who you might meet. But fundamentally you are asking someone to spend time with you. To help you.

It’s awesome your contact will meet with you, so be considerate of their time. Thank them. And make sure you see if there’s anything you can do to help them. It will make you feel less bashful about asking for feedback, or to be connected to someone else.

Considerate networking – Expect and insist on “double opt-in introductions” – this means the person connecting you someone needs to check with that person to confirm they’re interested BEFORE making the introduction . Only after that person agrees to be introduced, then expect the introduction. This means there’s mutual interest in the conversation.

This also introduces an obligation to responsiveness on your part. That means as soon as you see that email connecting you to the other party, respond promptly – before the other party has to. Your contact is doing you a favor, so demonstrate grace by making it easy for them for them to find a time and place to meet. And while you’re at it, be considerate of the person who made the introduction. In your reply, move that person to the bcc line of the email. That way they will see that the connection has been made, but they are not burdened with seeing the 7+ email exchanges that went into finding a date and place to meet.

Let go of the outcome – This is the hardest part. The only part of this process you can control is your ability to meet with people, tell your story, and explore where this all takes you. What it won’t do is provide a linear path to an awesome next role for you. But enough of these sincere conversations, where you’ve been considerate and forthcoming, will produce a conversation, at some point, that will point to a person or a role, that is exactly what you’re looking for.

It’s that simple. I can tell you every one of the awesome opportunities I am exploring right now have followed these four steps. And it has had nothing to do with where I went to school.

And like with you career – there is no deterministic path you can see stretching forward. Just a network of relationships guiding you down the road.

 

I’m done with Uber – The moral cost is too high

November 29, 2014

I was one one of Uber’s best fans – I must have recruited a dozen friends and colleagues to the service, because it fundamentally is just so much better than taxis or car services. Wonderfully inspired idea, and at the street level, brilliantly executed. I loved it.

And I use the past tense because I did love it. But not anymore. The trickle of moral lapses by Uber’s CEO, Travis Kalanick, have become a roaring torrent. Uber has an ethics problem, but most importantly it has an ethical leadership problem.

Peter Thiel summed it up succinctly: “Uber is the most ethically challenged company in Silicon Valley.”

Which is why the details of the plan to smear journalists who create unflattering views of the service pushed me to the point of being all done with the service.  So, on November 25 I sent my request to Uber to cancel my account, as “the moral cost to me of doing business with your firm is more than I can afford, and I have happily created my first accounts at Lyft and Curb.”

And in efficient Uber fashion, I received this confirmation of my account cancellation, which is sad. The service and drivers are great. But that’s not enough today. You have to believe in and trust the people at the top. And I can do neither with Uber the way it is being run right now. Travis – until you show some leadership and I won’t be back.Uber Cancellation

Personal Heroes

October 21, 2013

I have personal heroes – folks who have lived their lives in ways that give me inspiration and a vocabulary to name my own ambitions. People who are unafraid to say what they believe, regardless of what it will cost them.

David Walsh is one of my personal heroes

Few people outside of professional cycling know who this man is, but he’s the journalist who first suspected Lance Armstrong of cheating, and spent 13 years doing the difficult work of uncovering the evidence and speaking the truth. And he became the target of all Armstrong could throw at him.

This Sunday Times article says it all:

When Lance Armstrong won his first Tour de France in 1999, David Walsh wrote in The Sunday Times that he watched the race in sadness. Armstrong’s astonishing exploits, just three years after his successful battle with cancer, did not make sense to him. Rather than joining the unquestioning journalists who lauded the American’s achievements, Walsh called for an inquiry into the Tour de France in July 1999,….”

CTWThink about the context. In 1999 – the first year of Armstrong’s comeback – Walsh calls this out. And for the next 13 years  pretty much everyone else tells him he’s wrong. It costs him his job, professional and personal relationships. How lonely it must have been for him.

I’m not going to re-hash the whole Armstrong crime, but if you want to dig in, look here, and here, and here for a start. David’s books are “Seven Deadly Sins” and “From Lance to Landis”.

I am a huge cycling fan, and my family and I spent five  vacations in the French Alps to watch the race in person. In 2006 through a journalist friend, we struck up a dialogue with David to encourage him to write what became “From Lance to Landis” – his first english language book that laid out the evidence Armstrong was cheating.

David flew to France and spent the weekend with us. I was awestruck at the simplicity of his motivation: to expose a lie. It wasn’t personal, it was about values. This was a man of principle outraged at the crime he clearly saw but was incredibly inconvenient and unpopular to expose.

Over dinner long into the night, and then again at breakfast the next morning, the talk centered on the crime that was happening in plain sight. Incredibly we were sitting with him at that dinner when his phone rang – another journalist  calling him with the news that Floyd Landis had tested positive at the just completed Tour de France. Talk about being at ground-zero at a pivotal moment.

Looking back I can’t believe that weekend actually happened. What brought us together? I would like to think a sense of shared values.

This is a man whose humility, values, and sense of purpose we can all learn from. A true hero. I’ve got a few other people who serve this kind of inspiration, I’ll write about them later. For now, thank you, David.

My User Manual

October 12, 2013

A little over a year ago I started a new job, and a big component of my role was to help the company bring a lot of scale to their marketing, and bring a higher tempo and user focus to the company’s product development. This meant taking three groups of already high performing teams, and leading them into territories unfamiliar to them, while also helping them develop skills and capabilities new to many.

This is the kind of job that comes around in your career rarely. Tremendous, tremendous fun, and the best part is it’s only just beginning. We’re growing like crazy, and are about to enter that phase of the market where we have the right offering at the right time, and are about to see some pretty breathtaking expansion.

transparency

And I found myself explaining how I work, how I manage, and many of my core values as a manager, but also as a person. A lot.

So much of creating the opportunity for the rapid experimentation, fast failure, “iterate to excellence” team performance is based on how you work as a team, not what you work on as a team.

I mentioned this to my wife in a text message while on a train headed to work, and she pointed me to an interview with a CEO about his “user manual” – a one page document that lays out how anyone in the company can easily understand how to work with him. I LOVED it. A combination of approaches, philosophy, and personal values.

By the time I got off the train I had a complete draft of my User Manual. Check it out, I’m on v4.0

By the time I’d plugged in at the office I published it to  everyone on my teams via Chatter, as well as my counterparts on the exec team and a bunch of others I work with frequently.

Folks on my team appreciated the transparency, and it’s made it so much easier to engage with other teams and get to a place of trust and performance that much more quickly.

But the best part was for me. Any time you have to be intentional about something, and write it down, you learn something about yourself.

Dealing with equality, invisibility

November 10, 2009

In the past two weeks I’ve had a series of conversations with friends and colleagues about women in the technology workforce, provoked by of all things, water pollution.  The commonality being we’ve moved past the point where the problem is what is visible, and where we’re now facing the challenge of what you can’t see.

Here’s the water pollution angle:  A week or so ago I heard an interview with Charles Duhigg of the NY Times about how the cleanliness of the nation’s water supply is perhaps at greater risk than it’s ever been.  More so than back in the ‘70s, where the pollution was severe: rivers that caught fire, bore multi-colored hues of industrial waste, had detritus floating in them.

Today’s water pollution is microscopic, requiring sophisticated filtering that’s too expensive for water utilities to install.  Charles suggested the most practicable solution is for people to filter their own water, and take personal responsibility to ensure it’s clean and safe. 

So here’s where women in the technology workforce comes in.  Much visible change has happened.  Women are in the workforce, and are increasingly taking leadership positions.  Just not enough.  And what is the right number?  I have no idea, I’d like to think it’s the number that exists when everyone selected for a job is done so on the basis of merit.  The whole point is that it’s the product of an ongoing balancing act. 

I have faith that women’s pay will increase as more and more compensation and performance review processes are made transparent.  But unless they are listened to as equals, then all the process in the world still won’t address this fundamental form of discrimination, affecting the information that feeds performance reviews.  Will women ever get to parity unless their ideas are considered on an equal basis as men’s?

In the technology sector, ideas are what fuels business, so unless women’s ideas are given the same consideration as men’s, they will suffer when it comes time for reviews, and that will affect their compensation.  It won’t address why the women make $0.77 compared to every $1 their male counterparts make, but it won’t hurt.

So, who’s responsible to fix this?   We all are, and we fix it in the moment, calling it out and challenging it in the moment, when it happens. 

I was involved as a member of the board of a public-private entity where we were trying to determine the site of a new facility.  We’d spent weeks and weeks trying to figure out how to secure a really great site, and were running into all sorts of problems.  It was getting frustrating, and I made a suggestion about putting it in a less attractive, but more pragmatic location, which we quickly agreed to do. 

A female staff member pulled me aside after the meeting to thank me, saying she’d been making the same suggestion for weeks, but her superiors hadn’t listened to her.  I can tell you my suggestion was not all that insightful or magnificently made, but I was the male and it was listened to.

Rather than call this out, I spoke to her separately.  I was concerned about creating conflict between her and her superior.  So I let her know I realized how frustrated she must have been to not be listened to, and that at least I saw this.  How will the other male members of this board know how to listen differently if they aren’t shown where they haven’t done so?  I didn’t correct this in the moment, and in doing so I failed the woman who thanked me. 

And this is where the water analogy comes back.  The way to deal with this is to take personal responsibility, and to make what is invisible, visible. 

It is as much women’s responsibility to be louder and less convenient as it is men’s responsibilities to listen more actively.  In either case, everyone has an obligation to call out inequality when they see it.  And it won’t be convenient. 

That’s where I screwed up, and won’t do that again.

A sizable share of the readers of my blog are women.  What’s your experience?

Startup advice brilliance

October 21, 2009

A friend pointed me to a superb summary of advice for startups, specifically calling out the ways that advice can be flawed, along with some perceptive insights into how to identify advice that’s actionable and useful.  The post is by Eric Reis, and is appropriately titled The 10 Ways Startup Advice is Flawed

Eric’s pov is appropriately snarky, and at a macro level he calls out various ways that being lucky and being smart are frequently confused with each other.  Snarkiness aside, the really valuable point he makes is how important it is to be a critical thinker, in general.  The value of making your own assessment of the information you’re consuming, and not just accepting it.

I especially liked his point #6: Maybe the thing they did used to work, but it doesn’t anymore

I think about that a lot in my own context.  I was at RealNetworks back when it truly was pioneering this new phenomena of sending audio and video over the internet, and we owned that market.  In public we said we had 85%+ share of the market, but in reality it was closer to 95% for a good long time.

We called the shots, named the prices, dictated terms.  We muscled into and out of markets we cared about, aligned ourselves with titans of the technology landscape.

And then Microsoft showed up and we fought them tooth and nail.  It was a hard and ugly fight, which they eventually won (once they started paying attention).

Well, they won, sort of.  It was epic, and in a start-up kind of way, it was epic fun.  I remember picking a big fight with the Windows Media team on an internet media list-serve, where I’d just published some user research showing how people preferred our new video to Windows Media’s.

And Microsoft’s head of a/v technology posted to the list, accusing us of fluffing up the research, and he included a three page outline of the ways you could falsify/skew consumer surveys.  And it was so much fun to respond to the list , asking “how was it that Microsoft knew of so many ways to distort research?”

But I digress.

We each became so obsessed with each other we quit paying attention to what Macromedia was doing with Flash and what Apple was doing with the tight coupling of iTunes and the iPod.  So, while we were both wrestling in the mud pit, Apple and Macromedia left the building and started more interesting and lucrative businesses elsewhere.  And until that point the thing we did at RealNetworks really did used to work.

Eric’s “ten ways” are simple and insightful.  The hard part is putting them into action, in the moment.  My experience at RealNetworks is valuable to the startups I work with and talk to if and only if both of us are cognizant of its context.  And it takes discipline and a good dose of humility to walk the talk Eric is alluding to.

I know there’s a ton of stuff I did that was a product of luck and timing, and a lot that was a result of deliberate hard work and applied intelligence.  The hard part is being honest enough with myself to examine where those boundary lines are, to strip out the specific circumstantial knowledge from the generalized, truly durable knowledge.

So, let’s all get a good laugh out of Eric’s list, but also remember how hard it is to actually do what he’s suggesting.

Performance and an opportunity to explore it

October 2, 2009

The underpinning principle of this blog is “meaningful failure”, and what you can learn when you examine this critical juncture of where you fail and embrace what you can learn through that failure.

I’ve been seeking out others who share this interest, and last year I discovered Ross Bentley who runs a consulting business, Bentley Performance Systems, that focuses on improving performance for executives and interestingly, professional race car drivers.  That latter constituency intrigued me.  Failure on a race track has specific tangible implications that failure in business does not:  bent metal, physical harm, or worse.

Ross spends his time working with his clients on very personal elements of improving performance, along with more straightforward tools and techniques of planning and analysis.  His focus on who you are as a person I find interesting, the examination about what emotionally or psychologically may be holding someone back from achieving their potential is an area like failure where people are less comfortable speaking plainly and openly.

In the case of the racers and the executives the conversation goes in the same direction:  how can you best prepare yourself to be constantly improving, learning from success and failure?  He engages them in relevant and specific conversations focused on getting them to do to what they do differently and better.

And after this discussion, examination, and hard work the racers go to the track and the CEOs go to their offices.  In both cases they’re in environments where the information is flowing by, fast, and they need to make decisions and situation assessments rapidly.  And each ends up with a quantifiable data set telling them how well they performed: lap times & finish order, income statements & balance sheets.

Ross and I got together yesterday so he could share a research project he’s starting called Performance in the Workplace. He wants to to better understand how executives assess their own performance, and what affects their performance over time.

The research is nice and simple:  he’s asking them to fill out a short survey, once a week, and tell him how well they feel they’ve performed, and why.  You can participate in the project by signing up here.

What I like about his approach is that he’s not defining “performance” for the participants.  He’s letting them define it for themselves.  When he first told me about this my reaction was “that’s pretty subjective, why not quantify performance with metrics”?”.  But then I realized, that really misses the point.  When you’re trying to help people do better every day, metrics are the product of your performance, not the measure of it.

We run businesses based on a set of milestones, KPIs (key performance indicators) – “dashboards” – and these are important measures of the recent past.  And they’re critical – I’ve written about why a well documented operating plan and the corresponding assumptions are essential to managing your business.

But executives spend their days making decisions, asking questions, analyzing and assessing – and of course this results in metric-based results.  But not in the moment.  How do you assess the effectiveness of your performance while you’re making those decisions, asking those questions, digging into those numbers?

I think Ross is onto an interesting topic here.  What causes you to feel you’re performing well one day, and not so well the next?  Will the act of self-assessing performance help you, in and of itself, to become more effective and cause you to be closer to the top of your game?

I’m going to participate, because in my business, at best I get monthly or quarterly metrics from my companies in terms of valuations I can apply to rates of return – on paper – and it takes years to get to the point where you can convert the paper value to cash or stock you can sell for cash.  Daily performance is not at all quantifiable with metrics, but matters oh so much.

I’m sure I can learn something from this, and am eager to see how what he finds.