IT Career the Strategy Game
-
20 sided dice is needed for this game.
Add some "Rage Quit" cards somewhere."An end user card is played against you with the WreckIT Ralph^ action card."
- ^Roll 7 or more to avoid broken equipment.
Deploy Interrupt card: It's an HR issue^^
- ^^ Roll a 1 or more to remove 2 stress tokens and collect 1 Jellyfish Token^^^. Then go back to playing FarmVille (Miss a turn).
- ^^^ Awarded for spineless actions
-
The problem is what is the goal of the game? Everyone has their own goals when it comes to career. Sometimes it's to earn as much as possible, but often times there are many other goals. Even if you say that we all have a goal to satisfy Maslow's "Hierarchy of Needs", the definition of those needs will vary from person to person. I'm sure we all know people or are so-called "successful" in their careers, but miserable as sin, and people who are relatively unsuccessful but happy as a pig in ****. I suspect the game would be focussed on your personal idea of what a career should look like, which only works if people similar to you play it.
-
I agree with the concept that you have, but I wonder how much it matters. What I mean is, what I've at least found personally, is that the pursuit of career success, in any form, tends to result in the same set of things: more money, better work environment, less time tied to the office, better food at work, more freedom, more creativity, more flexibility, more benefits, better lifestyle, etc.
While this isn't always true, I think that the trend is, and the trend is all the game can reflect. The only things that would not be reflected by the game, I think, are things that are not part of your job like a desire to not bother, a desire to be stagnant, a desire to do less, the desire for stability and for those people, which is a lot of people, they would never want to play the game in the first place because they are already aware that they do not desire to advance their careers.
But anyone interested in career success, no matter how I think you define it, the manner of doing so and the means are roughly the same. So while money might be the "score" it would reflect all of those other things too, generally.
-
I'll give an extreme example. A friend of mine refused to do anything but be a factory worker because he "wanted free time at home" and refused to give any of it up in order to "have a career." In doing so, he ended up not only working long days but having to commute as well, for forever. His job would never give him long vacations, short days or work from home. His desire for an extremely short term goal left him with a lifetime of not achieving the very goal he set out to achieve.
Meanwhile, by the time that we were in our mid-twenties my work life was flexible and by thirty it was short and then became work from home. It's a personal anecdote, but the idea stands. If you look at people in the middle of their IT career versus people in the top senior ranks, those in the top ranks almost never have to come in on their days off, often get to work from home, make more money, have more freedom, get to be more creative, determine their own paths, etc.
-
But I totally understand the idea that money is not the goal, I'm just thinking of it as a proxy here. The ability to make money would be the goal, not necessarily being paid the most. I've taken many paycuts in exchange for other things, but always tied to career advancement, if that makes sense.
-
@scottalanmiller said:
What I mean is, what I've at least found personally, is that the pursuit of career success, in any form, tends to result in the same set of things: more money, better work environment, less time tied to the office, better food at work, more freedom, more creativity, more flexibility, more benefits, better lifestyle, etc.
I think most of those things come with seniority. I'm happy being a big fish in a small pond because it gives me near complete freedom to work as I please. If I moved to a bigger company, I'd likely earn more money but have less freedom.
-
@Carnival-Boy said:
I think most of those things come with seniority. I'm happy being a big fish in a small pond because it gives me near complete freedom to work as I please. If I moved to a bigger company, I'd likely earn more money but have less freedom.
Big companies aren't the same as moving up. Yes, seniority brings privilege. But the issue is that so many people do things that don't bring them seniority. That's really what I'm getting at with career advancement. Seniority in terms of being ahead in your career, not just old.
-
I think that whole, seniority doesn't have to work on days off, etc thing really depends on the position. For example, if you're the senior person on a platform, say O365 hosted Exchange - I'm willing to bet that guy gets called in on his vacation when there is a problem that reaches a certain point. Granted you hope that the people below you can handle 99.99% of things, but there is always that 0.01% that bites you.
-
@Carnival-Boy said:
I'm sure we all know people or are so-called "successful" in their careers, but miserable as sin, and people who are relatively unsuccessful but happy as a pig in ****.
I'd argue that if you're happy as a pig, then you probably are successful, maybe not as successful as you could be, but still successful. Otherwise, how are you really happy?
-
@Dashrender said:
I think that whole, seniority doesn't have to work on days off, etc thing really depends on the position. For example, if you're the senior person on a platform, say O365 hosted Exchange - I'm willing to bet that guy gets called in on his vacation when there is a problem that reaches a certain point. Granted you hope that the people below you can handle 99.99% of things, but there is always that 0.01% that bites you.
I've been that guy, final level of support for a bank with tens of thousands of machines under me. Yes, I was on call 24x7, but I also got three hours days, able to drink on the job, could work from home any time I wanted, could work from any country in which we had an office, had a staff of people just to screen my calls and connect me only when needed, no normal workload except for the escalations. Once you get to that level, you get to pick how you take your benefits. Yeah, I was always on call, but the benefits more than made up for it.
-
@Dashrender said:
@Carnival-Boy said:
I'm sure we all know people or are so-called "successful" in their careers, but miserable as sin, and people who are relatively unsuccessful but happy as a pig in ****.
I'd argue that if you're happy as a pig, then you probably are successful, maybe not as successful as you could be, but still successful. Otherwise, how are you really happy?
I'd argue that if you're happy and you know it, clap your hands.
-
@Dashrender said:
@Carnival-Boy said:
I'm sure we all know people or are so-called "successful" in their careers, but miserable as sin, and people who are relatively unsuccessful but happy as a pig in ****.
I'd argue that if you're happy as a pig, then you probably are successful, maybe not as successful as you could be, but still successful. Otherwise, how are you really happy?
At my last job, I worked with a great group of folks, but got paid just barely enough to support my family. I was happy, but got tired of the struggle to make ends meet.
-
@scottalanmiller said:
@Dashrender said:
I think that whole, seniority doesn't have to work on days off, etc thing really depends on the position. For example, if you're the senior person on a platform, say O365 hosted Exchange - I'm willing to bet that guy gets called in on his vacation when there is a problem that reaches a certain point. Granted you hope that the people below you can handle 99.99% of things, but there is always that 0.01% that bites you.
I've been that guy, final level of support for a bank with tens of thousands of machines under me. Yes, I was on call 24x7, but I also got three hours days, able to drink on the job, could work from home any time I wanted, could work from any country in which we had an office, had a staff of people just to screen my calls and connect me only when needed, no normal workload except for the escalations. Once you get to that level, you get to pick how you take your benefits. Yeah, I was always on call, but the benefits more than made up for it.
I have to ask, what was your job in that position?
Work three hours a day? doing? when not in an escalation.
-
@Dashrender Drinking on the job, apparently, ha ha ha.
-
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
I think that whole, seniority doesn't have to work on days off, etc thing really depends on the position. For example, if you're the senior person on a platform, say O365 hosted Exchange - I'm willing to bet that guy gets called in on his vacation when there is a problem that reaches a certain point. Granted you hope that the people below you can handle 99.99% of things, but there is always that 0.01% that bites you.
I've been that guy, final level of support for a bank with tens of thousands of machines under me. Yes, I was on call 24x7, but I also got three hours days, able to drink on the job, could work from home any time I wanted, could work from any country in which we had an office, had a staff of people just to screen my calls and connect me only when needed, no normal workload except for the escalations. Once you get to that level, you get to pick how you take your benefits. Yeah, I was always on call, but the benefits more than made up for it.
I have to ask, what was your job in that position?
Work three hours a day? doing? when not in an escalation.
Yeah, in the office like three hours a day. I'd spread it out with time at the bar in the middle. Position was Linux Technology Chief. I didn't get assigned projects, but I had to always be available for escalation, 24x7x365. I was there for guidance, to authorize things that no one else could, to be a bypass for SVP approval (when the "staff" couldn't get their hands dirty) or to handle the technical issues that didn't get caught by the staff before me.
-
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
I think that whole, seniority doesn't have to work on days off, etc thing really depends on the position. For example, if you're the senior person on a platform, say O365 hosted Exchange - I'm willing to bet that guy gets called in on his vacation when there is a problem that reaches a certain point. Granted you hope that the people below you can handle 99.99% of things, but there is always that 0.01% that bites you.
I've been that guy, final level of support for a bank with tens of thousands of machines under me. Yes, I was on call 24x7, but I also got three hours days, able to drink on the job, could work from home any time I wanted, could work from any country in which we had an office, had a staff of people just to screen my calls and connect me only when needed, no normal workload except for the escalations. Once you get to that level, you get to pick how you take your benefits. Yeah, I was always on call, but the benefits more than made up for it.
I have to ask, what was your job in that position?
Work three hours a day? doing? when not in an escalation.
Yeah, in the office like three hours a day. I'd spread it out with time at the bar in the middle. Position was Linux Technology Chief. I didn't get assigned projects, but I had to always be available for escalation, 24x7x365. I was there for guidance, to authorize things that no one else could, to be a bypass for SVP approval (when the "staff" couldn't get their hands dirty) or to handle the technical issues that didn't get caught by the staff before me.
Nice - but really, how man of those types of jobs are there? a dozen? Even if we say there is one at every Fortune 1000, that's only 1000 of those jobs, so they are pretty impractical to aspire to.
Sure, everyone wants to be President some day (ok not really, but you get my point), it's just not a realistic goal for 99.9999%. -
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
I think that whole, seniority doesn't have to work on days off, etc thing really depends on the position. For example, if you're the senior person on a platform, say O365 hosted Exchange - I'm willing to bet that guy gets called in on his vacation when there is a problem that reaches a certain point. Granted you hope that the people below you can handle 99.99% of things, but there is always that 0.01% that bites you.
I've been that guy, final level of support for a bank with tens of thousands of machines under me. Yes, I was on call 24x7, but I also got three hours days, able to drink on the job, could work from home any time I wanted, could work from any country in which we had an office, had a staff of people just to screen my calls and connect me only when needed, no normal workload except for the escalations. Once you get to that level, you get to pick how you take your benefits. Yeah, I was always on call, but the benefits more than made up for it.
I have to ask, what was your job in that position?
Work three hours a day? doing? when not in an escalation.
Yeah, in the office like three hours a day. I'd spread it out with time at the bar in the middle. Position was Linux Technology Chief. I didn't get assigned projects, but I had to always be available for escalation, 24x7x365. I was there for guidance, to authorize things that no one else could, to be a bypass for SVP approval (when the "staff" couldn't get their hands dirty) or to handle the technical issues that didn't get caught by the staff before me.
Nice - but really, how man of those types of jobs are there? a dozen? Even if we say there is one at every Fortune 1000, that's only 1000 of those jobs, so they are pretty impractical to aspire to.
Sure, everyone wants to be President some day (ok not really, but you get my point), it's just not a realistic goal for 99.9999%.Set the bar too high, and you'll always have something to strive for. Set it too low, and you'll surpass it, and lose your motivation.
-
@dafyre said:
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
I think that whole, seniority doesn't have to work on days off, etc thing really depends on the position. For example, if you're the senior person on a platform, say O365 hosted Exchange - I'm willing to bet that guy gets called in on his vacation when there is a problem that reaches a certain point. Granted you hope that the people below you can handle 99.99% of things, but there is always that 0.01% that bites you.
I've been that guy, final level of support for a bank with tens of thousands of machines under me. Yes, I was on call 24x7, but I also got three hours days, able to drink on the job, could work from home any time I wanted, could work from any country in which we had an office, had a staff of people just to screen my calls and connect me only when needed, no normal workload except for the escalations. Once you get to that level, you get to pick how you take your benefits. Yeah, I was always on call, but the benefits more than made up for it.
I have to ask, what was your job in that position?
Work three hours a day? doing? when not in an escalation.
Yeah, in the office like three hours a day. I'd spread it out with time at the bar in the middle. Position was Linux Technology Chief. I didn't get assigned projects, but I had to always be available for escalation, 24x7x365. I was there for guidance, to authorize things that no one else could, to be a bypass for SVP approval (when the "staff" couldn't get their hands dirty) or to handle the technical issues that didn't get caught by the staff before me.
Nice - but really, how man of those types of jobs are there? a dozen? Even if we say there is one at every Fortune 1000, that's only 1000 of those jobs, so they are pretty impractical to aspire to.
Sure, everyone wants to be President some day (ok not really, but you get my point), it's just not a realistic goal for 99.9999%.Set the bar too high, and you'll always have something to strive for. Set it too low, and you'll surpass it, and lose your motivation.
At the same time, I wonder how many people actually strive for those positions like Scott mentioned and achieve them? I'd bet it's more likely they wind up in them through xyz situation, and not directed action on their part to get that position. Though I suppose I could be wrong. I'm sure Scott got it because either he made the company create it for him, or he sought it out.
-
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
I think that whole, seniority doesn't have to work on days off, etc thing really depends on the position. For example, if you're the senior person on a platform, say O365 hosted Exchange - I'm willing to bet that guy gets called in on his vacation when there is a problem that reaches a certain point. Granted you hope that the people below you can handle 99.99% of things, but there is always that 0.01% that bites you.
I've been that guy, final level of support for a bank with tens of thousands of machines under me. Yes, I was on call 24x7, but I also got three hours days, able to drink on the job, could work from home any time I wanted, could work from any country in which we had an office, had a staff of people just to screen my calls and connect me only when needed, no normal workload except for the escalations. Once you get to that level, you get to pick how you take your benefits. Yeah, I was always on call, but the benefits more than made up for it.
I have to ask, what was your job in that position?
Work three hours a day? doing? when not in an escalation.
Yeah, in the office like three hours a day. I'd spread it out with time at the bar in the middle. Position was Linux Technology Chief. I didn't get assigned projects, but I had to always be available for escalation, 24x7x365. I was there for guidance, to authorize things that no one else could, to be a bypass for SVP approval (when the "staff" couldn't get their hands dirty) or to handle the technical issues that didn't get caught by the staff before me.
Nice - but really, how man of those types of jobs are there? a dozen? Even if we say there is one at every Fortune 1000, that's only 1000 of those jobs, so they are pretty impractical to aspire to.
Sure, everyone wants to be President some day (ok not really, but you get my point), it's just not a realistic goal for 99.9999%.Why does it matter how many there are of that kind? The point isn't that I had some special job, the point is that as you get more senior, the jobs generally get better and better. Think about it, who has the worst jobs, the entry level people. If they had better jobs than the people above them, they would refuse to take promotions. Each level of seniority has to bring enough benefits for people to want to do it. It's a gradual scale. Keep moving up, it keeps getting better (on average.)
-
@Dashrender said:
@dafyre said:
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
I think that whole, seniority doesn't have to work on days off, etc thing really depends on the position. For example, if you're the senior person on a platform, say O365 hosted Exchange - I'm willing to bet that guy gets called in on his vacation when there is a problem that reaches a certain point. Granted you hope that the people below you can handle 99.99% of things, but there is always that 0.01% that bites you.
I've been that guy, final level of support for a bank with tens of thousands of machines under me. Yes, I was on call 24x7, but I also got three hours days, able to drink on the job, could work from home any time I wanted, could work from any country in which we had an office, had a staff of people just to screen my calls and connect me only when needed, no normal workload except for the escalations. Once you get to that level, you get to pick how you take your benefits. Yeah, I was always on call, but the benefits more than made up for it.
I have to ask, what was your job in that position?
Work three hours a day? doing? when not in an escalation.
Yeah, in the office like three hours a day. I'd spread it out with time at the bar in the middle. Position was Linux Technology Chief. I didn't get assigned projects, but I had to always be available for escalation, 24x7x365. I was there for guidance, to authorize things that no one else could, to be a bypass for SVP approval (when the "staff" couldn't get their hands dirty) or to handle the technical issues that didn't get caught by the staff before me.
Nice - but really, how man of those types of jobs are there? a dozen? Even if we say there is one at every Fortune 1000, that's only 1000 of those jobs, so they are pretty impractical to aspire to.
Sure, everyone wants to be President some day (ok not really, but you get my point), it's just not a realistic goal for 99.9999%.Set the bar too high, and you'll always have something to strive for. Set it too low, and you'll surpass it, and lose your motivation.
At the same time, I wonder how many people actually strive for those positions like Scott mentioned and achieve them? I'd bet it's more likely they wind up in them through xyz situation, and not directed action on their part to get that position. Though I suppose I could be wrong. I'm sure Scott got it because either he made the company create it for him, or he sought it out.
All of them. Because there are always new people coming in to fill the lowest, most entry level positions. There is always an opportunity to move into something better.
