You don’t have to be in a management position to be a leader

For years, I used to think that in order for me to become a leader, I would need to land a management position of some type. Indeed, for a long time, our culture taught us that you needed to obtain some kind of leadership or management position in order to be a leader. So I strived for climbing the corporate ladder, trying to get myself into the upper ranks and getting into a position where I could be the one calling most (but not necessarily all) of the shots. I even contemplated pursuing an MBA (and, to a small extent, I am still entertaining the idea).

Now that I’m older (and, hopefully, wiser), I no longer have such ambitions. At this point in my career, I am happy where I am, management position be damned. Climbing the corporate ladder is no longer a priority for me (that said, if such an opportunity arises, it doesn’t necessarily mean I would turn it down, but it would depend on the opportunity). If I ever haven an opportunity to be promoted, that’d be great, but it is no longer a priority for me, and if it never happens, I won’t lose sleep over it.

This seems to correspond with a change in my mindset as I advance in my career (and my age). When I was younger and more brash, I wanted to be the center of attention, the rock star. But now that I’m older and have some more experience under my belt, being the rock star is no longer a priority.

What I discovered is that I very much get just as much of a high by helping someone else become the rock star. I frequently take part in mentoring opportunities — through my alma mater, my fraternity, my job, or my extracurricular activities. Whenever I see someone struggling with something, and if I am able to assist (which I’m not always able to do), I’ll offer my advice or my hand. And I get a great deal of satisfaction whenever the light bulb goes off in my student’s or mentee’s head, and (s)he suddenly says, “oh, NOW I get it!”

I was reminded of this last Saturday when I spoke at Data Geeks Saturday. I signed into the virtual room in which I was doing my own presentation, and I caught the tail end of Mark Runyon‘s presentation titled “Elevating Your Career into IT Leadership.” I had seen his presentation before — it was either at PASS Summit or another SQL Saturday — I don’t remember which — but one of the takeaways was that there are many ways to become a leader, and it doesn’t necessarily involve becoming a manager.

There are many ways to be a leader. Be a mentor or a teacher. Volunteer to take the reigns whenever an opportunity arises. If you see someone struggling, help him or her out. Leadership takes many forms. You don’t necessarily have to climb the ladder to attain it.

Who owns the email?

A while back, one of my work colleagues asked a very interesting question.

“When we send out an email, who owns the copyright?  Is it the owners of the data (i.e. individual clients), or is it the owners of the email (i.e. our employer)?”

He continued to lay out the scenario: “Send it to Client 1. Employee at Client 1 leaks the contents of the email; (our company) has to then cede coypright (sic) to the report so that they can distribute it internall?” (sic)

His final comment: “Imagine if (other companies) did that: ‘You wrote this with Office 365, Microsoft Owns (sic) the copyright'”

That’s a good question.  It’s one to which I don’t have an answer.  To be honest, I don’t have the knowledge or background to be able to answer it.  (Maybe someone who understands legal procedure or copyright law can answer it better than I can; if so, please feel free to comment.)  But I do think it’s an important one, nevertheless.

Email is probably one of the least secure forms of electronic communication.  It is often said that email should be treated like postcards, where anyone and everyone who touches it can read it.  It’s something I always keep in mind whenever I send email.  I refuse to send critical data (passwords, PHI, financial data, etc.) over email.  If I do have a need to send critical data, I’ll look for a way to do it securely, whether it’s data encryption, secure channels, direct messaging (which may not entirely be secure), or even face-to-face communication.  Data security is a big deal (too big to cover in just a single article), and each news item about data breaches becomes a bigger focus (as of this article, the Facebook data scandal is one of the biggest and most recent; sadly, I do not believe that this will be the biggest, nor the last, such breach).

If someone told me that I had to answer this question (and mind you, this is my opinion; do NOT quote me or state this as fact), the original author (or any data content copyright holder) owns any copyrights.  If I sent a song lyric over email, whomever it was that wrote the lyric would own that copyright, but I would own anything that I wrote (that is, something that came from my head — intellectual property — and not from someone else).  The purpose of a copyright, after all, is to protect intellectual property.  However, given email’s open and unsecure nature, original thoughts posted to an email should probably be considered to be public domain.  (That said, if an email sender cites some data source, has he or she committed a copyright violation?  I won’t take the time to discuss that now, but that might be another topic for another time.)

Despite email’s security concerns, it is still a useful tool, and is pretty much ubiquitous throughout our daily lives.  So long as we keep in mind that it isn’t secure, and we can keep our communication habits in context, it is a technology that will likely not disappear anytime soon.