The Google+ project and exec team
threader.app
threader.app
Regarding the main event in question: I like that Google allows people to party in the evenings with whoever they want to party with. I like that Google allows people to reschedule meetings if they aren't feeling well, for whatever reason. It sucks that the author's grandmother died and that he felt the need to work through the night while that happened, but it's unfair to take that out on your colleagues. Nobody would have blamed him if he asked to reschedule the meeting because of his grandmother's health. Heck, they probably wouldn't even have minded if he asked for a different day/time, just so he wouldn't have to work through the night.
I have no idea who the author is. He might be a fantastic person, and Jim/Greg might be total dicks, for all I know. But just from the volume of different complaints mentioned, and his reaction to a meeting reschedule, I get the impression that he isn't the easiest person to work with, and that there are other sides to this story.
Way too much ego tied up in petty disagreements here.
- Raylan Givens
There is a lot of ascribing negative motives to other people's words and behaviors when other explanations seem possible from the description he gave to the situation.
But you have to remember that he was told he'd get to work on Chrome but was then assigned to G+. You have to be extremely laid-back and financially secure to roll with that punch and not put the rest of the company under a microscope (even criticizing petty culture-identity labels like 'nooglers' builds up resentment).
Even if the project was guaranteed, things happen. Roll with it. Building resentment you are just hurting yourself.
Fuck, posts like these piss me off so much. There are so many candidates who would give their arm and leg to work at Google.
Heck, if i didn't have a startup I would have been happy to work even on Orkut at Google.
There could be inaccuracies here, it's a twitter rant after all, but as presented, that would demoralize a lot of people. You don't have to force your own happiness just because some people aren't getting their dream job at a dream company.
Some devs would roll with lower salary, some with different projects. You can still call the shots instead of going ahead and whinging publically
I'd certainly tell people on as many public forums as possible instead of just letting someone walk all over me and also see if I could get anyone with influence to reverse the decision.
Do I sit and take it? Hell no. And you shouldn't either because you should have more self-respect.
I have worked in the biggest bank in Australia where subcontractors were siphoning away the source codes and customer data via mobile hotspots. I blew the whistle to data security and got fired in return. Company later paid me huge chunk of money in return for silence.
Sometimes you just gotta walk away to better deals. Life is unfair more so if you have a big ego.
Yeah it is, but I don't live in the valley.
I mean, your example fits my definition too. I just have a much lower threshold that I tolerate apparently.
But lets wait for someone else to come by with a more impactful story than yours and we can reset the goal posts.
I've heard this is standard behavior for google - completely disregarding what an applicant wants to work on and putting them instead on a project chosen by the hiring committee. Considering that the range of different projects where you may end up is enormous, I agree that it sucks.
HC doesn't pick your job, they decide whether or not to hire you. Hence the name. At Google it's typically trivially simple to switch teams (this article notwithstanding), so teams don't recruit and hire independently like happens in many companies.
So after a hire is approved, they have to be matched up with a team. Teams decide whether or not a hire is appropriate for their team, and candidate decides whether or not team is appropriate for their interests.
If you're approved for hire but you don't like the team you're paired with, say "I'd prefer to work on X", and if X is hiring and their hiring manager thinks you're a good fit, then you can go there instead. That route is more complicated because recruiters specialize in a given area, but the whole point is for you to like your job.
All it took was the dev to say that he preferred working on a specific project. Some teams even have further internal hiring processes from the talent pool.
I am not even sure OP knows that team switching was possible and how internal recruiting works for large organizations
> All it took was the dev to say that he preferred working on a specific project. Some teams even have further internal hiring processes from the talent pool.
I'm not sure if I read that correctly, but don't these two sentences contradict each other? Of course some positions will be more coveted than others, so additional processes are necessary to choose from all the people interested in the position. But it means that just saying "I prefer to work on X" is not nearly enough to transfer (of course it isn't).
So, what number of teams can a typical candidate choose from? Compared to the total number of teams hiring? I guess the typical scenario is that a few teams express interest and then you can choose one of them, which is not much different from just "congratulations, this is your new team".
> At Google it's typically trivially simple to switch teams
How simple is trivially simple? Does the new team have to have sufficient budget/a vacancy? What kind of selection process is there if you are not the only one who wants to transfer to that team? What about your old team? What do you do with your responsibilities at the current project? Can you transfer immediately after you've been hired?
Depends on a variety of factors (candidate skills, season, other people, what projects are being worked on etc.). I've seen everything from between 1, and like 8-10.
>How simple is trivially simple?
There's an internal hiring board that people post openings on. You can apply. AFAIK, the manager can pick between people. Basically all of your other questions come down to "does the hiring manager want to allow it".
>What do you do with your responsibilities at the current project?
Depends, I'd hope people handle it like reasonable humans. In my case at least, I told my manager I was interested in transferring out in the next couple months, and he told me to stick around a bit longer so that he could make sure I got promoted. I ended up not transferring out as my work got more interesting.
In general, its easier to transfer with the blessing of your current manager, but from what I've seen its not required. And there are probably long tail cases where transferring is difficult, or people do unethical things, but I'm not directly familiar with any, and I don't think they're the norm. So for most cases, transferring is trivial.
Edit: And actually, if you read the entire story (more was posted on twitter after this article went up), he was able to transfer off of the team with almost no issues, to a team he found much more interesting, but instead left to go to Dropbox. The whole transferring this was literally a nonissue once he actually tried to do it.
This is a labor law violation, because it's obvious, even to government regulators, that it's unfair to the employee. I would hope everybody would object to labor law violations on their first day of work.
He didn't get the Chrome job.
His resume was "kept on file" as they say.
Months later a different job came up with a totally different team of people, and someone on that team remembered him and recommended him. (Slap of ingratitude to that guy I guess. Just one of many things this guy got wrong.)
When I was a recruiter for ibm I always made sure to check if the potential was an asshole or not before going ahead with tech. Talent can always be learned by those willing. Attitude is permanent.
Without the right attitude though it's hard to train someone.
You can tell when people don't have the right attitude because they stop trying to learn things or listen to outside perspectives. That's the attitude that causes people stop learning and stop growing.
"Let’s call him Greg because his real name is just as vanilla"
Also shows a complete lack of introspection or self awareness that he'd post and promote this drivel and think it makes him look GOOD! Lol. Career suicide imo. If I was considering hiring him and googled him and came across this writing, I'd nope out so fast.
That does indicate a problem for Google if true. This is often the slow death people talk about when big company culture turns like this.
This is made stronger by the fact Google+ failed, and they're shutting it down. If i was an exec at Google I'd totally take this as a retrospective data point, and I'd explore to see how much of this attitude existed within the Plus org, if it was prevalent, it could have had a role in the failure of Plus.
>That does indicate a problem for Google if true.
I mean, if his writing is a reflection of how he behaves then why is this a problem for Google? Getting rid of toxic people in a company is a positive and not a negative.
People on bad projects like scapegoats.
Ganging up on one guy, especially new young upstart, is a sign of a dysfunctional team too.
Sounds like conflict management is not handled very well by anyone in these situations.The author certainly could have handled it better, and "Greg" should have handled it way better.
Very disappointing to hear, but at the same time these kinds of conflict are usually local and only affect a few individuals, so it is probably not very fair to describe the whole project and exec team as operating in this fashion.
People like Greg are poison to a workplace, IMHO.
Good on the author to bring this kind of stuff into the open though so that it hopefully happens less in the future. At least something went right lol!
The author seems like the kind of person that I'd love to do a 3-person startup with. We'd be in an environment where working late into the night is valuable sometimes, and because all of us would be doing that he'd have no reason to be resentful. Hopefully he gets into a group like that before the corporate life trains him to preserve his sanity by not caring so much.
Agreed.
This dude, and many people I've met similar to him, takes people on their word and acts accordingly. He might be a bad fit for an environment where this is not respected, but I'd argue this is not a sign of 'not working well in a team'. Rather, it's a sign of him taking people on their word and finding it difficult to work on a team where this is not respected.
I imagine there are plenty of teams, in companies big and small, that do respect these kinds of things. Or at least do so begrudgingly.
My personal experience is that any work environment that does not manage to handle these 'your word is your word' type situations, even if badly, is a horrible place and destined to fail (barring some exceptional situation where they can get away with it).
Outliers like this particular person are a kind of anchor-point. Perhaps it's okay, even necessary, that they don't quite thrive in certain stages of a company. But when they actively flee the ship, it's a horribly sign.
This so much this.
It’s so hard to find a tribe of passionate driven people who care crazy amounts about their vision and purpose.
This is clearly evident from when he mentioned his outrage that he:
"Never would’ve imagined that I was joining a team of 50+ designers where a bunch of them had never designed before.
And I was “evaluated” at about their level? These weren’t interns, these were designers in their very first roles ever...at Google."
From any UX design professional's perspective, he comes into their world, lacking any background in UX or basic understanding of user centered design methods, and just does the visual design portion of the work, not the actual hard work that goes into understanding human behavior, being curious and testing hypotheses and validating designs with quantitative and qualitative data via UX research methods.
Dude needs to check his ego in my opinion, design is a team sport and anyone can mock up random dribble worthy interfaces in an afternoon and think they deserve the title of designer then diss others who have a 4 year degree in fields related to understanding human behavior, not just art or graphic design (although art degrees are good if you solely focus on visual design due to color theory, typography, understanding design aesthetics, design critiquing etc.)
tl;dr
UI designer ≠ UX designer
It's unfair to take that out on your colleagues, but it is fair to blame it on management and the culture they set. Some people are going to be more politically protected than others for reasons that aren't strongly related to the value they add to the business and able to get away with things others aren't, and if you don't counteract that, you'll both get inefficient results (either they're doing something they shouldn't, or other people don't feel empowered to do something they should) and also cause a loss to morale and trust.
Setting clear (if mechanical) rules about things that would otherwise turn into "the politically connected can do this, the rest of you can't" is absolutely the responsibility of management. Saying to people up front that they should always feel free to take time off or cancel meetings for personal emergencies and the company trusts their judgment (if that is in fact the policy) and making sure people act like it's true - or making sure people show up and have extremely good excuses when they don't, if that's the policy - is management's job.
> Anyhow, my wholesale redesign of all of Jim’s work was obviously making him feel bad.
> One day, he came up to me totally flustered in one of the micro-kitchens. He said “People aren’t liking these icons.” I said, “Oh, ok, let me know who and I’ll collect their feedback and we can make them better.”
...
> Me: “OK, no worries man. Would it make you feel better if I put something together that explains my decision making and then you and whomever else can punch holes in it, and give me direct feedback?”
> Jim: “Yeah, ok, sounds good. I’ll put something on the calendar.”
> 9am the next morning. A dick move.
> I went home and got to work.
> In the early evening I got a call from my dad. My grandmother’s health took a turn for the worst. They weren’t sure she’d make it past the evening.
> I couldn’t grieve. I needed to make this happen. These two designers were beloved by Greg. I had to win them over or they’d screw everything up for me. Everything I’d worked for could come crashing down due to their pettiness.
Like, holy hell. Jim is a _peer_. Nobody asked Morgan to do this work, Morgan volunteered to do it. And he decided to work through a major life event in the off hours for something that didn't come from anyone above him in the hierarchy? And then to blow the other guy up when he reschedules the meeting? Wow.
1) He accepted a salary (115K) lowered than what he thought was fair
2) Design occurred in silos, there was no unity or cohesion
3) His 2nd manager was "political" and "in love with bureaucracy"
4) An exec on a rival team tried to quash his idea
5) Managers often just wanted to slap their name on his work
6) He worked all night to satisfy an angry coworker the night his grandmother died, while coworker partied then rescheduled mtg
For No 1: if you don't think a salary is fair, don't accept it.
Nos 2-5: these happen at almost every medium-large sized company I've ever worked at. If you know a place that isn't political, bureaucratic, siloed and filled with rivals and petty managers, let me know so I can give you my resume.
For No. 6, if you feel a deadline or meeting time is unfair, say so. If you have a sick family member, say so.
He sent this email to his boss:
> "Greg, I had to work most of the night because of Jim, and he canceled our meeting because he was partying with our competitors. In my book, this is totally unacceptable. What am I supposed to do?"
It's never a good idea to send this. It's not going to help you, even if you're in the right. Canceling a meeting is not a gross injustice and if an employee parties afterhours that's his or her business.
I sympathize with the author. Sounds like a good dude. But you have to try to roll with the punches, no workplace will be perfect, I promise you.
Red Hat. It is siloed and can be (increasingly) bureaucratic, but I have never experienced rivals or petty managers and it's the least political place I've ever worked.
Even if Red Hat is amazing for you it might not be for other people. No company is immune to human nature.
Again I feel for the author. Sounds like "Greg" was jerk. But it's not cosmic injustice, it's more a feature of humans working in collectives, IMHO.
Say one was promoted twice in an year- it's always easy to believe that it happened because you deserved it, than to believe it happened to you because the managers like you.
But you need to deal with jerks. There's lots of them out there, often in management positions.
He says this made him "very depressed" and working there was "completely and utterly ruined" -- an on over-reaction. Toxic leadership is bad but you shouldn't let it control you to this extent.
This is one of the problems with the way their hiring is marketed. They are depicted to be asking hard CS and algorithm based questions, and a culture of a workplace is being sold which is based on a merit process along the lines of 'programming abilities'.
The reality in every people structure one will every work at, politics is how the world works. People optimize what's best for themselves. The bosses are often stupid, because bosses that exist never want smart people to grow up and become a competition to them. Money is always attached to hot projects, so bulk of the career growth, bonuses and other juice comes when you work there. Regardless of whatever the merits of that project are.
The same applies to projects too. Once a company has 2 - 3 cash cow projects, the executives won't let new set of rivaling products emerge and become a competition to their fiefdom. Most of the times the competition is killed in plain sight, but other times its back room political sabotage. Only a few days back some one mentioned how Google is a place where $100M revenue opportunities pop up and die all the time.
The same case with that 20% extra time projects. Who is going to let this happen? I'm pretty sure anybody who dares to do these projects will be marked to be a trouble maker by the very managers they report too.
In short once you have more than 2 layers of management at your company, politics is how thing will work. And its perfectly, OK. Because that's how world is.
What is problematic is if the people at the top, Larry Page and Sergey Brin don't know are too naive to understand that its happening in their company since years. Inability to deal with everyday politics can kill companies.
> In short once you have more than 2 layers of management at your company, politics is how thing will work. And its perfectly, OK. Because that's how world is.
The problem is people see "the political system" and "politicians" and think wouldn't it be great if we could do away with that, never understanding these are just examples of normal human behavior taken to extreme levels because of the competition, scale and stakes.
Politics is always present, because it's just a word to describe human power dynamics.
Company politics becomes obvious when different people want different things, and some people exert power and influence to affect outcomes, in subtle or not so subtle ways. It's as inevitable at a small company as a big company, the only difference is that it may not be as extreme and it may take a while longer to show up.
The mistake is people considering working at a company of tens of thousands of people and thinking that somehow normal human behavior doesn't apply here.
It's not all sunshine and rainbows, but to say you understand the internal dynamics of Google and the decisions that Larry and Sergey make is certainly some kind of delusional.
Nobody's perfect, we all have some bad things in our personalities. But it's impossible to read this and extract the value that he tries to convey that Google as a company didn't accommodate him (dismissing the design of buildings or noogler's orientation) rather than he tried too hard to be liked and perceived as valuable member.
Irreplaceable is an extreme version of valuable. Companies are right to avoid that extreme. But they shouldn't take it so far that they are allergic to admitting that employees have value. Any current employee who is right in the middle of the bell curve has value because, while they could be replaced, they are a known quantity.
From the employee side, there can be a temptation to believe that because you're not exceptional, you're not valuable. Even if you're merely average, that is OK, and you need to accept that you are a worthwhile member of the team. If mentally you can't claim the position you rightfully deserve as your own, then you believe something wrong about the world, and like any wrong information, that will corrupt your decisions about how to act.
[0]https://www.google.com/amp/s/amp.businessinsider.com/neal-mo...
I'm increasingly convinced that there's a ton of life experience and wisdom to be gained by working for big tech in your early 20s when you have a lot of flexibility. But when you've figured out what kind of life you want to lead, they're probably not the right fit for you.
I think it boils down to: money is easily quantifiable, happiness and freedom aren't. So people make bad life decisions based on an incomplete assessment of what will really suit them best.
And we may have some inkling as to why Vic left (if the anecdotes are representative of behavior).
”In a couple of months I knocked out more work than they could have built in a year with their eng team.”
No startup deserves a designer with this kind of attitude. Your job isn’t to produce pie-in-the-sky concepts for your portfolio but to work on the product together with the engineers.
The author's biggest work-related mistake was to sit tight when given a managed he had a bad relationship with. In most large organizations (500+ employees), your success and your failure will have a lot to do with a good relationship with your manager. It's not just performance reviews, but your technical influence that will be influenced by this. This matters with sibling teams too, as a political manager (and most bad managers are very political) will not want a report they don't like to have more influence than they do. I have seen people go from being seen as extremely productive to being called very low performers, and vice versa, in 2 months and a manager change. This kind of match, and caring about making teams cohesive, is something that most large valley companies do not really care about, and hurts them greatly, as a lot of talent is underused or downright shoved out the door.
We can learn the some things as managers too: A report we really dislike could really help the company a whole lot if they were in an environment that matches them better, and ultimately that's what we should be caring about, not making people we don't like leave, and helping people we like get promoted. Whether it is by knowing them better, or helping them move somewhere else, is far more work than just undermining them, but its ultimately the right thing to do. What we should foster instead is teamwork, and the minimization of political behavior among reports. The sly report that is always telling me what I like to hear, but playing politics all day is the bad manager of tomorrow. Companies work better when people are aligned with building the best product the company can, not maximizing the credit they get. The more energy is spent on political fights, the worse the product gets.
That said it's still an incredibly interesting story, and I have the feeling that many managers could gain some insight into what's going on in some of those "I am gods gift to development"-type individuals who can be both a huge benefit to a project yet at the same time be toxic to work with.
Also, about contractors in pivotal roles. The author was relatively new to for-profit industry and it happens way more often than one may think. People who go the contractor route are usually senior and experienced enough to be confident in getting and keeping the gigs, as the barrier to getting rid of a contractor is very low.
The thing that cought my eye is that he was telling his boss his coworker was home hung over, becouse he worked while his grandma died instead of visiting her. Like, who is being inconsiderate here really?
The key to understanding the author is at the top of the article.
He skipped college, freelanced for much of his life and worked for non-profits (whose lofty goals transcend internal politics.) As someone who recently worked to make the world a better place, he genuinely tried to help his teammates and naively believe they appreciated his help. (I bet he doesn't know how to read body language and fake smiles). They on the other hand felt he was trying to make them look bad, and use them as promotion stepping stones.
People who work with compilers for a long time have no qualms being wrong. They take feedback and improve. But for Straight A - straight out of college students and political types, being wrong is a personal insult.
Here's what I think:
Most of his co-workers had been complaining about his well meaning meddling. He couldn't be fired for making things better. The email was the excuse his boss had been looking for to get rid of him.
If he joined Google 10 years ago, he would have been a rock star.
My advice:
He should find a way to make freelancing work.
He should join a startup but freelance / consult on the side to augment his pay. Going to business school - or some management training might also do him a lot of good.
Most of all, if he gets another big job, he shouldn't help anyone unless they ask for it.
Wish him good luck.
That doesn't mean anything, and if you're trying to give it meaning, you're probably not qualified to diagnose someone over a twitter thread.
Everything, all-caps profanities and all, would be part of a normal conversation where a friend is ranting to you.
Writing in public that you wanted to assualt a coworker becouse he didn't like your design and cancelled a meeting for being "sick"/hangover is a flashing red warning light with sugar on top.
It's one thing to rant that to some freinds at a bar if you have no history of assaults. Another thing to publicly state it.
Do you want to work with him? I do not.
The hate, the vitorial, the attacks, the arrogance, the lack of accountability, paranoid, passive aggressive, complaining intensely about event trivial things...
This is the type of person I would leave a project over, no matter how exciting the work.
Suddenly it makes sense why we can't use + to force a word in google searches anymore.
Yes.
"Plus" is a dumb and lame product name.
When Jean-Marie Messier was trying to make Vivendi an important Internet company, he decided he wanted to make some kind of portal (copying Yahoo) that would be named "Vivendi Plus". He announced it at a press conference before having even secured the vivendiplus.com domain. That was in Sept. '99. It failed miserably (didn't even launch).
Ten years later when Google wanted to copy Facebook they came up with the exact same name. It failed.
I think just naming a product myBigCompany--Plus is a symptom you don't know what you're doing or where you're going. It's bad form and then it's bad luck.
There are some things you can say about the style of writing but... There is stuff here that resonates and accurately describes downsides of SV life. Just because "it's like that everywhere" doesn't mean we shouldn't aspire to better. Just because we don't like some aspect of this guy's communication style doesn't mean we should dismiss him.
If you're reading, Morgan, don't despair at all the people displaying needless aggression in this thread.
The author sounds like the kind of person who will just passively accept a situation instead of saying what he really thinks, leading to internalized anger and bitterness.
If someone "below" me had a problem with my scheduling or some things I was doing, I'd like them to tell me and not just act angry later on.
People work together and generally try to be accommodating in large companies. But it does require people communicating their needs to each other and being fair. The poster sounded like he was holding a grudge against people and trying to power through things instead of having a frank discussion with other people. It sounds like they have talent, but they need work in working with others.
I get that sometimes you know your ideas are much better than other people's, but at the end of the day you need to work with others and give and take a bit.
The company has to explicitly foster an egoless culture to make fair peer reviews work, but egoless employees aren't going to present themselves well enough to get promotions. The system incentivizes politics. If you didn't see it in your team, your teammates hadn't learned to play the game yet.
I understand why it happens, I’ve been on a few projects like that. The problem is that it’s hard to come up with a genuine new idea that a stack of middle managers will agree on and execute.
But if you say: “Let’s make Twitter/facebook/App Store”, then the middle managers can’t really disagree with you since there’s already a successful example of that thing on the market.
There’s also no room for miscommunication, everyone already knows what Facebook looks like, we just have to copy it.
The problem is that this work is dull, uninspired, and likely to be unsuccessful. What’s the point? Why not just kill this shit before spending millions of dollars on it?
This is the point at which you begin to realize the author is a bit of a jerk.
I also stumbled upon his Twitter at the end of the article and it does more to show really how much this experience has affected him (https://twitter.com/morganknutson). Very sad.
Saying NO, being political, negotiating. . . Not very surprising if he indeed had such bad managers.
Still, feels like wasted time and resources for everybody. I hope he is doing OK now.
Two benefits: them not working productively at a competitor's place is one, and them losing the skills and drive to make real-world useful things after a few years is another.
It is a no-brainer decision from a game theoretic point of view: these companies already have a top-of-the-line, best in the world product. Working on more products requires lots of inspiration, time and luck, and even in the best case all you get is just another amazing product. (I.e., just more of the stuff you already got.)
Using your money and fame to neutralize talent that could be used against you requires no effort or thinking at all, only money. These companies don't know what to do with their profits anyways.
Move on and get a new life. And before you get your next gig, go spend 10 days in a vipasanna center.
Is this the sort of person you'd want to work with or hire to work for you? If it were a company that didn't pay you or were doing something unethical etc then fair enough - blow that whistle... but as far as I can see this is just someone with a chip on their shoulder and a bruised ego who can't move on.
I don't care how dysfunctional his experience was, I don't care how much of a star he might be, I don't need that kind of worry in my life, and it's hard to imagine someone who would. Be interested to know how his career goes after this.
No, this is never true. Airing dirty laundry almost never produces a real change in the world. It just burns bridges and often makes you look petty.
This does sound like a failure of leadership WRT the product and internal management, but, I think we should all try to read past the memory coloring, because I'm sure other members might have a different experience. But I think the main point still holds. Google+ was created as a reaction to FB, and while there were a couple of half decent features, but I can't remember anything they created that was enough to overcome FB's network advantage and draw people away.
Either way, this article is fascinating to hear internals and understand the dynamics behind the scenes.
I'm not going to say anything about all the other obvious caveats here, I think the other comments cover that pretty well. But because this one actually pisses me off: who cares about "partying with our competitors"? Does working at Google mean I shouldn't have friends at other companies? And above all, why the shit is your manager supposed to care about that?
For what it's worth, I've also seen people transfer in less than 3-6 months on the team they were hired into. But if you don't do anything to make it happen, it's not going to happen.
Don't be that guy.
Google+ for all it's short comings were business failures not tech or ux or design failure. I worked on far stupider projects at big companies and I am utterly grateful for the opportunities given to me.
Absurd blog and no matter how muchi hate Google posts like these makes me realize how ungrateful some people can be.
The problem isn't the reassignment itself. It's the lack of communication.
What i guess happened was that Google found candidates for their chrome project and put him in their backlog. Later when they had one more vacancy they went thru this backlog and made offers
If your skillset is in huge demand, and a company needs you badly enough, they might just be willing to guarantee in writing what project you'd be working on - and maybe even give you a window seat, too.
Though if you're in demand, and want project guarantees, you'd probably be happier as a consultant - that way you're sort of always guaranteed to be working on the project you want, because completing that project is the entire reason the company hired you.
My bet is that he wasn't fired/let go because the manager was afraid for his job (that's what the author claims and it is a pretty cheap shot to make) but because the guy's behavior was being toxic for the team. Unfortunately he couldn't see that over his ego ...
That's how it works in life, that how it works in companies.
Complaining that he didn't get his dream project right off the bat is vanity.
I learned a lot from this. It was very demotivating, painful, even humiliating, and it took me a long time to get over it (mostly). What I didn't learn is that all the people who were to blame for this were the bad guys. Here's what I did learn:
- People are people and will do the things that people do, despite your high expectations.
- You can often not change other people. But you can change yourself. Think of what *you* can do to improve relationships.
- You'll rarely change someone's thinking by using logic. This, sadly, is not human nature in a political environment.
- Work is a political environment. Even engineering.
- You must learn what motivates, frustrates, encourages, shames and honors the people you work with.
- Protect the people you work with, do not cause them to raise their defenses.
- If you want something to move forward in a team you must win people over.
- You don't win people over by making them feel threatened that you will take power from them or make them look bad.
- If you truly care about something, having another person claim that idea as their own isn't bad, it's a great victory.
Like others have mentioned, I get the impression there are many sides to this this story, just like any other story. And yes, it does come across as extremely whiny. And also somewhat naive.
Yaaaawwwwwwn.... I'm not exactly sitting on the edge of my seat for part II.
This is where the companies could do a better job with HR of making sure each employee fits well in their team and enjoys themselves, and if not, to relocate them to another team.
This is also a great lesson to learn for yourself: Don't stay on a shitty team, don't work for a failing product. Get out as soon as you can, transfer to another team, or even quit and leave the company if that's not possible.
For me that was the critical omission, the idea that we can be "friends" on Google+ but you have no way to message me. It never made any sense. And I'm not even that smart.
This is clearly evident from when he mentioned his outrage that he:
"Never would’ve imagined that I was joining a team of 50+ designers where a bunch of them had never designed before.
And I was “evaluated” at about their level? These weren’t interns, these were designers in their very first roles ever...at Google."
From any UX design professional's perspective, he comes into their world, lacking any background in UX or basic understanding of user centered design methods, and just does the visual design portion of the work, not the actual hard work that goes into understanding human behavior, being curious and testing hypotheses and validating designs with quantitative and qualitative data via UX research methods.
Dude needs to check his ego in my opinion, design is a team sport and anyone can mock up random dribbble worthy interfaces in an afternoon and think they deserve the title of designer then diss others who have a 4 year degree in fields related to understanding human behavior, not just art or graphic design (although art degrees are good if you solely focus on visual design due to color theory, typography, understanding design aesthetics, design critiquing etc.)
tl;dr
UI designer ≠ UX designer
@morganknutson, your writing style is on point.
that’s all you need to know. can stop reading right there