On “My Vote Doesn’t Matter” and “Voting Your Conscience”

The other day I was listening to talk radio, where the host was encouraging people to vote regardless if they felt that their vote mattered or not. If you’re in a state that regularly votes one political party (Democrat or Republican) you may feel that your single vote will not contribute to the final outcome.

I can understand that line of reasoning and the feeling.

So I propose that you think differently about how a vote “matters”.

Think of your vote as part of a team, your political party’s team. Now forget that you are in a different physical location and figuratively put yourself on the same playing field as your team. In a team competition, every position matters and everyone has a job to do. And the strength of a team is defined by the size of the group that shows up to play.

Now that you are on the same playing field with a team, you don’t have the luxury of saying your vote doesn’t matter. Be committed to your team, show some empathy and put yourself in their cleats. Think about how you would vote now that your vote does matter!

If you think your vote doesn’t matter, then rethink. Your vote matters to your teammates, and you would have the same expectation of them if the situation was reversed.

Some may suggest that if their vote “doesn’t matter” (meaning it won’t alter the outcome) that they can instead “vote their conscience”.

If you would vote one way when your vote “matters” by living in a swing state and vote another way when you don’t live in a swing state, then this is equivalent to putting on a different jersey just because you have some sort of liberty to do so. If you really are giving up on your old team then admit it to yourself. But you don’t have the liberty of “voting your conscience” and staying on the same team.

How will you make your vote count? Is there a difference between voting your conscience and making your vote count?

I submit that your vote always “matters” and says more than you may think.


A Lesson from Jon Lester and the World Series Champion Chicago Cubs about Focusing on Strengths

Honestly, I thought Jon Lester was strange when I saw him pitch during the World Series.

What is peculiar about Lester is that he will not throw to a base if he doesn’t have to. He’d even throw his entire glove and ball instead of just the ball if he must (see above). And his definition of “have to” was way different than my definition until today because I learned again the value of focus.

Lester won’t check the runner at first nor second and rarely gets off the mound to field a ball unless it practically hits him. Lester isn’t particularly bad at fielding, and in fact he’s just as good or better than ever.

But Jon Lester is his best when he is pitching. During the post season this year he pitched nearly his best of all time. He helped his team be more successful when he was doing what he had strengths to do.

I yearned for Lester to check the runner at first because 20 million people watching the game knew the runner was going to steal second. But when Lester decided to NOT check a runner at first during the World Series, it made me pause.

By examining how peculiar Lester is on the mound, we learn a valuable lesson. Lester focuses his energy where he has strengths, and that is pitching, not fielding.

When runners do get on base, they more easily steal on him because they get such a good jump on his pitch. And if Lester allows the runners to distract him or get him nervous it impacts his throwing.

What seemed alien to me when compared to my expectation of a pitcher’s behavior, was familiar, permitted, and even agreed upon by his team and management. Those who depend on him know his strengths and expect him to play where the numbers give them the best odds.

Likewise, what expectations should you have of each person on your team, of yourself? Are you playing to your strengths that give you the best chance of success, or are you playing to someone else’s expectations?

You Keep Using That Word. I Don’t Think it Means What you Think it Means.

What we say and what we do can be very different. By looking at our operational execution, we can be enlightened about what we actually do well. As we see how we engineer and operate, we can determine if we are executing for the customer we intend to have.

For example:

A popular web host who specializes in “WordPress” hosting describes themselves this way in their sales content:

[Company name] is the industry leader in managed WordPress hosting. All we think about is how to run WordPress in the best way possible. Our WordPress hosting platform keeps sites fast, scalable, and secure. Our team has spent years perfecting our WordPress hosting platform. Every feature, from [product name] and staging sites, to [product name] and [product name], has been built specifically for WordPress users.

As a potential customer that sounds pretty good. It gives you the general impression that all your WordPress hosting problems will be solved. You are promised they can provide the best possible way to have a fast, scalable and secure website. 😀

However, in the comments of their must-use plugin they state:

// Should we cache database queries for logged-in users?

// Normally no, but for high-admin sites it does help and might be worth the risk.

Implied in this code comment is the idea that: a) caching database queries for admin users is a bad thing, b) users with a lot of admin or dashboard activity consumes a lot of resources and caching queries reduces the load on their infrastructure/servers, and c) caching database queries will degrade performance and upset some users.

Caching database queries can make the admin of a website faster, but it contradicts the idea that a website is scalable. Cached database queries can inhibit the ability of an admin to have consistent expectations that the data they are presented with is current. It can also require additional actions by the admin to retrieve the more accurate data, if they are even given that option at all.


Writing the Sales Pitch from Operational Execution

Does the operational execution match up with the sales pitch? In this case it’s ironic that the sales side of this company touts their commitment to performance, while their operations attempts to throttle power users.

If you were to re-write the sales pitch from the actual operational experience, I believe their sales pitch would read more like this:

[Company name] is the industry leader in managing an infrastructure dedicated to the WordPress application. All we think about is how to run servers and WordPress in the most efficient way. Our hosting platform keeps websites online. Our team has spent years perfecting our WordPress hosting platform. Every feature, from [product name] and staging sites, to [product name] and [product name], has been built specifically for hosting WordPress.

You would add an emphasis on infrastructure, and efficiency while de-emphasizing scalability.

The Operational Execution Targets a Different Customer

When you read the revised description of their services, who would find those services attractive? A website owner is never attracted to cached database queries, especially if their WordPress site is more data intensive where the data changes  often (think e-commerce). However, a hosting company is attracted to the expertise to try and maximize their fixed-cost resources.

A Tale of Two Departments Trying to Keep Their Jobs

The Sales Department is incentivized to acquire customers and they do that by telling customers what they want to hear. The Engineering or Development Department is charged with keeping sites online and doing it in the most efficient way possible.

Both departments think they’re doing the right thing, but to what end? Will customers who sign up for an infrastructure that is specialized for WordPress sign up and stay even after they experience caching? Or will an investor looking to acquire expertise in efficiency be interested in the original sales pitch promising performance above all?

In the end, without new paying customers, a business dies.

Confusion Breeds Mediocrity

If the management team of this WordPress host was serious about the message they pitch to new customers, they would align the engineering processes to match the goals. They wouldn’t engineer their platform to decrease data reliability and scalability, especially in a way that is so hidden from the normal WordPress user (making that decision in the code). Instead they would figure out how they can make their platform more reliable and scalable, and more transparent.

We work with the customers of this WordPress web host and we’ve taken notice of their tactics that renege on their sales promises; or at least we assert that they don’t recognize the disconnect between what they say and what they do.

Are Sales and Operations aligned?

What do you do well? What will always be in style to your customers? Can you do more of what people want?

I’m not saying we have this perfectly worked out at Event Espresso and Event Smart. But, I’d recommend discussing with your team whether you’re engineered to fulfill your promises. If your sales and engineering are not aligned, can you change the engineering to match the sales pitch, or should you target a different customer based on your current engineering strategy?