If the boss likes to ask other employees about their life plans (marriage, children) in open forums, is that legal? What should employees do in this situation?
Showing posts with label dumb management theories. Show all posts
Showing posts with label dumb management theories. Show all posts
Friday, March 4, 2016
What is an employer allowed to ask, once the employee is hired?
From the inbox, an interesting question, paraphrased as such:
I have to say, I have never been asked that question by my boss, and if I were asked, I would probably feel the need to answer vaguely or politely demur answering. But I tend to be deferential to authority, and only if pressed, I would probably feel the need to say, "That is not your concern, sir."
It is important to note: this is NOT a question about interviews, this is a question about "questions from your boss, once you are hired."
Readers, what say you?
Thursday, December 10, 2015
The Boss Likes Good News
I thought this viewpoint from Bob Lutz (a longtime GM executive) about the engineering culture at Volkswagen was... interesting and potentially revealing:
Ferdinand Piƫch, the immensely powerful former chief of Volkswagen's supervisory board, is more than likely the root cause of the VW diesel-emissions scandal. Whether he specifically asked for, tacitly approved, or was even aware of the company's use of software to deliberately fudge EPA emissions testing is immaterial.
I sat next to him at an industry dinner in the Nineties, just after the fourth-generation Golf had debuted at the Frankfurt show. I told him, "I'd like to congratulate you on the new Golf. First of all, it's a nice-looking car, but God, those body fits!"
"Ah, you like those?"
"Yeah. I wish we could get close to that at Chrysler."
"I'll give you the recipe. I called all the body engineers, stamping people, manufacturing, and executives into my conference room. And I said, 'I am tired of all these lousy body fits. You have six weeks to achieve world-class body fits. I have all your names. If we do not have good body fits in six weeks, I will replace all of you. Thank you for your time today.' "
That's how you did it?"
"Yes. And it worked."Assuming that this story is true and that this actually is the prevailing culture at Volkswagen, it's not surprising that such a ruse was devised to keep the bosses happy (and EPA in the dark.)*
I presume Truly Wise Bosses when when the turn the screws to your employees (if you have to), knowing when to let them lead, and knowing when they may be turning to nefarious and ultimately destructive means to give you good news.
*It also reminds me of one of my favorite quotes from Bill Buford's "Heat", about the famous New York City chef, Mario Batali:
Did Mario know what the kitchen was like without him? According to Tony [CJ's note: one of his sous-chefs], "Mario knows exactly what he doesn't want to know."I think a lot of bosses know exactly what they don't want to know.
Friday, November 13, 2015
All unhappy companies?
Here's a long article in the Lebanon, NH Valley News about a small company called Seldon Technologies with a hilarious and horrifically sad middle section when the scientists talk about Seldon's core technology, carbon nanotubes for water filtration:
During an internal compliance review of the company’s technology, Seldon scientists discovered that its signature innovation — super-small cylinder-shaped carbon nanotubes, or CNTs — “had little or no effect on performance” of the filtration “media” to remove contaminants, according to the company’s confidential 85-page 2013 business plan, a copy of which was provided to the Valley News.
As a result, the authors of the plan wrote, the tests “have called into question both the validity and value of (Seldon’s) patents.”
The finding turned out to be both bad news and good news for the company.
The good news: When reformulated to exclude carbon nanotubes, the filtration media was just as effective and no longer needed approval from the Environmental Protection Agency, meaning it could finally be sold into the U.S. consumer market.
The bad news: The discovery undermined the company’s selling point as a cutting-edge nanotechnology innovator, the key to Seldon’s industry positioning and marketing.
Seldon employees, many of whom asked not to be identified because they didn’t want to jeopardize their chances of finding new jobs by talking publicly about their former employer, said the discovery forced Seldon to focus efforts on developing filter technology that did not employ nanotechnology.
“It looked as though carbon nanotubes were the cat’s [behind]*, but they were not,” said one employee. The reformulated filtration media works nearly as well, the employee said, but “is not that much of a secret sauce.”The article quotes a lot of Seldon scientists who detail the various financial and management gyrations; they're pretty brutal. I often feel that there are way too many whiz-bang stories about startups and not enough skepticism, or postmortems. There are successes in startups, but there are many more failures.
*CJ's bowdlerization for corporate firewalls
Thursday, November 5, 2015
Glassdoor review of the week: Cambridge Major Labs, Germantown, WI
A recent Glassdoor review* of Cambridge Major Laboratories in Germantown, Wisconsin has this funny little comment:
Pros
The opportunities for growth and development are very good, the people who work there are friendly and amazingly helpful.
Cons
Work-life balance needs to be better. People get frustrated when there is no balance.
Advice to Management
Slow down - the company is growing and doing well. Focus on giving your employees a work-life balance. Show some appreciation other than pizza or ice cream and people will be more willing to stay.I have this theory that there are two kinds of gifting languages in the United States.
There's the giving of food, which is typically the gifting language amongst friends and peers (you bring your coworkers a plate of cookies, you buy a friend their favorite distilled spirit, etc., etc.)
There's also the giving of money, which is quite often the language of appreciation between employer and employee. An employee will receive a check for a small sum along with their Lucite plaque or whatever. While most of the time, the appreciation matters more than the check, I think people would react differently if the small sum was delivered in, say, fresh-baked cookies.
I don't want to sound entitled or unappreciative, but I have noted that employees tend to react poorly when employers co-opt the gifting language of friends (i.e. "let's have a pizza party!") in place of money.
Readers, I'm sure I'm wrong here. Your thoughts?
Thursday, October 8, 2015
Why is France different?
| Credit: Jacques Brinon/AP |
I don't know anything about this story or the structure of French airlines or French labor policy, but this story really shocks me, in the rather brutal violence of it (they don't have assault/battery laws?), that it was allowed to happen (they don't have security guards in France?) and, finally, that I cannot think of a case where similar things happened to American executives during the Great Recession.
As I said on Twitter the other day, I think acts of social shunning of CEOs and the like (refusing to shake hands, other signs of disrespect and unfriendliness) are certainly fair game, especially during rather brutal layoffs here. But it hasn't seemed to happen - why not? Do our HR departments just do a better job of keeping us peons away? Why is France different?
Thursday, August 13, 2015
A clarifying graph of ages of laid-off Intel employees
![]() |
| Age distribution of a July 2015 layoff of Intel employees Credit: Oregonlive.com |
I would like to see the distribution of overall employees at Intel - one presumes that they would be shifted to the left a bit, but I don't really know anything about semiconductor manucturing production/R&D to speculate on the median age of the workforce.
I don't seem to remember similar graphs coming out of the 2003-2013 period of layoffs in pharma - I wonder why?
Sure looks like the upper end of the age distribution took the biggest hit, though, doesn't it?
UPDATE: A commenter points out a portion of the article I meant to comment on:
UPDATE: A commenter points out a portion of the article I meant to comment on:
This layoff skewed older – considerably so. The average age of an Intel employee in the United States is 42.6. The average age of an employee laid off last month was 48.1. Workers in their 50s were 1.7 times more likely to lose their job than the average worker overall; workers in their 60s were 2.7 times more likely to be laid off than the average. Meanwhile, workers in their 20s and 30s were considerably less likely to lose their jobs. Employment attorneys say this isn't unusual, and it could be difficult to make a discrimination case in court."I gotta check out some more of the literature around this issue, see if there's more chemistry/pharma-relevant stuff.
Wednesday, July 15, 2015
Satoru Iwata on layoffs: "laying off a group of employees will not help to strengthen Nintendo's business"
| I have clear childhood memories of this NES game, "Top Gun." Credit: gamefaqs.com |
I am not a gamer, but I couldn't miss the news that Nintendo president Satoru Iwata died this week. Via Twitter, I saw his comment on "corporate restructuring" from 2013, which struck me (naturally) as being very wise:
Nintendo global president Satoru Iwata believes that his company can get back into the black without firing any of its employees, through good ol' fashioned efficiency and cost-saving measures.
"It is true that our business has its ups and downs every few years, and of course, our ideal situation is to make a profit even in the low periods, return these profits to investors and maintain a high share price," Iwata said during a recent shareholders meeting, in response to a question about "corporate restructuring" as a solution to Nintendo's problems.
"If we reduce the number of employees for better short-term financial results," he continued, "employee morale will decrease, and I sincerely doubt employees who fear that they may be laid off will be able to develop software titles that could impress people around the world." Iwata also noted that global exchange rates have played a major part in Nintendo's financial situation, saying that "the influence of exchange rates is the main aspect of this matter," rather than Nintendo's headcount.
"Employees make valuable contributions in their respective fields, so I believe that laying off a group of employees will not help to strengthen Nintendo's business in the long run," he said. "Our current policy is to achieve favorable results by continuously cutting unnecessary expenses and increasing business efficiency."
It's a shame that more pharmaceutical company executives don't think this way about their R&D scientists.
Friday, September 19, 2014
ScienceCareers: Ph.Ds, don't apply for BS/MS positions
This piece in ScienceCareers is rather hard to read. It's about Ph.D. scientists who apply for B.S/M.S.-level positions, written by a scientific recruiter:
I can't help but agree with Mr. Jensen that applying for and accepting a B.S./M.S.-level position is rather unwise, in that it is a dramatically different role than Ph.D.s. What I am surprised at his choice to not talk about why they might be applying for these roles, i.e. they can't find work as Ph.D.-level research scientists.
Finally, it's sad that, in our lawyer/lawsuit-phobic* culture, we apparently can't tell applicants what we think about them. It's good for companies, sure, but it sure leaves the applicant confused. We need to be giving people feedback, even it's unpleasant. I am not really one to suggest changes to federal law, but it seems to me that passing a law to offer employers limited immunity to lawsuits in exchange for telling applicants (especially on-site interviewees) their weaknesses would be a good idea.
UPDATE: Anon0919140334P rather effectively repudiates Mr. Jensen:
The discovery that you’re overqualified for many advertised jobs often comes as a rude shock. You’ve seen the ads, as Jonathan did, seeking skills in your area of expertise—but the employer hasn’t specified a Ph.D. Instead, the employer is seeking someone with a Bachelor of Science or a Master of Science degree. That’s not ideal, but you have those degrees, too, so why not apply?
“Each of our labs has openings for B.S. or M.S.-level scientists who play a key role in our research effort. But those labs also have positions for Ph.D.s, and the two are completely separate roles,” says a client of mine, a human resources (HR) manager for a multinational R&D institution.
I told the client a story that Jonathan shared with me: Jonathan called a networking contact and found himself speaking to the hiring manager for a position he had applied to previously. He asked why his application hadn’t succeeded, and the hiring manager gave him an answer: He was overqualified for the position.
My client gasped audibly when I relayed that story. This was, apparently, a violation of standard protocol: Managers should “know better than to provide a lot of color,” my client says. Apparently, they’re not supposed to reveal that much about why they didn’t hire you. That’s why you rarely get a direct answer to questions like that. My HR contact, though, shared more information with me about being overqualified, so now I can share it with you.Read the whole thing, if only so you can share in my irritation.
I can't help but agree with Mr. Jensen that applying for and accepting a B.S./M.S.-level position is rather unwise, in that it is a dramatically different role than Ph.D.s. What I am surprised at his choice to not talk about why they might be applying for these roles, i.e. they can't find work as Ph.D.-level research scientists.
Finally, it's sad that, in our lawyer/lawsuit-phobic* culture, we apparently can't tell applicants what we think about them. It's good for companies, sure, but it sure leaves the applicant confused. We need to be giving people feedback, even it's unpleasant. I am not really one to suggest changes to federal law, but it seems to me that passing a law to offer employers limited immunity to lawsuits in exchange for telling applicants (especially on-site interviewees) their weaknesses would be a good idea.
UPDATE: Anon0919140334P rather effectively repudiates Mr. Jensen:
Wow... I'm sure glad I didn't follow this guy's advice 8 years ago when I applied to my current company. I am a PhD chemist, and had been working as a postdoc in a national lab. I applied for a BS/MS posting because it was exactly in line with what I wanted to do and looked like a nearly perfect match for my skill sets. The only drawback was that they were looking for someone at a lower degree level. When I interviewed, I learned that the position was a replacement for a technician who had left the company. The group was looking to increase its skill level, and thought a BS/MS was the right slot for the job.
I convinced them I'd be a better choice, and though there were some growing pains initially (group didn't function properly at first when I changed the role from technician to scientist), I was eventually promoted to lead the group. I've been doing that for the past four years. I also make significantly above the ACS salary median for PhDs, so it's not like I locked myself into a low-paying role by applying for an MS position.
I've been on several recent hiring committees, and in many cases we consider candidates with different degree levels. I actually interviewed someone today. In his company, the only people who advance up the science ladder are PhDs, and he's looking to get out of there specifically because of that culture (has a BS + 15 years of technical & managerial experience). He stated that one of the reasons he applied for this position is because he's heard that it's still possible to advance in our company without a doctorate. This is definitely true, and is supported by the fact that two of our current top scientists have MS degrees.
I therefore take a stance that's opposite from Jensen's: If you have a PhD and there's an MS level position that looks attractive, you should absolutely apply for it. If the company has the right culture, you might just get the job and find yourself in a place you can spend the rest of your career.I think the trick is, most large enough companies have HR/hiring cultures that are more like Jensen's client and less like Anon's. More's the pity.
Friday, October 18, 2013
Quote of the week: Cellbio, on creativity
I love this comment at In the Pipeline about creativity and medicinal chemists by Cellbio:
...However, there are clear drivers of organizational creativity that can be consciously built, enforced and which do positively impact creativity. And when in place, it also becomes evident that while there are more and less creative individuals, contributions to creativity can and do come from all angles, often by people outside of the depth of field under discussion because they have a fresh perspective.
The drivers are a culture where ideas have no hierarchy, where managers are skilled at management and artfully disappear from moments of team success, where "leaders" are not modeled of off academic PIs where the presumption is the final scientific say sits higher in the organization, where teams have the strongest voice, where the breadth of the team is exposed to strategic goals not just tasks, where failure is safe and when safe to fail honest opinions about the potential of projects frees people to change direction and pursue ideas with merit instead of advancing toward goals that meet career objectives and satisfy internal metrics of success.
WIth a unyielding belief in this and never wavering, creativity can be cultivated. And perhaps, the high jump analogy is incorrect in that success of highly functional drug discovery teams can be driven by one foot jumps by many members. I think the concept of productive creativity is too narrow if one assume's that creativity stops when the target or NCE is "discovered". Perhaps this contributes to our industry failings as I am quite sure drug discovery from this point forward requires as much or more creative energy.The part about "strategic goals" reminds me of the German military concept of Auftragstaktik, where subordinates are told the goal to accomplish, their assigned resources and the timeframe, not how to accomplish the goal.
Have a great weekend!
Thursday, September 26, 2013
It's the same everywhere
I totally get what this Reddit poster is saying about graduate school:
I'm a graduate student in an R1 university. I wanted to share my experiences to determine if what I'm observing is a problem everywhere or if it is specific to my university.
Don't get me wrong, my department has many intelligent people and is often underrated. However many people barely scrape by doing a minimal amount of research and hardly showing up. Some people shock me when they pass their oral exams or get a PhD when they can't explain LeChatelier's principle. I have a hard time thinking that such people would pass an oral at MIT or Caltech. However this isn't my concern; perhaps I underestimate them and should get off my high horse. What grinds my gears is how these people perform in the lab and affect my research
What I see is a general lack of regard for safety and a lack of respect for instrumentation/apparatus that many people use. Pulling solvent into vacuum pumps (and not changing pump oil), clutter everywhere, furtive use of instrumentation by people who know that they don't know what they're doing and who do not own the instrument, huge scale-ups (for example involving liters of bromine and no headspace in the flask), things of that nature. Oh, and a large proportion of Chinese students who don't understand English and will tell you they understand everything you say, then break stuff. I really don't mind explaining something twice-I don't understand what their deal is. The best part is that if you bring it up during group meeting or send out a mass email describing how not to screw up the glovebox, everyone nods and agrees, then nothing changes the next day. I'm not saying I'm perfect or have an immaculate hood, but I do try to be very respectful and careful if I am using someone else's instrument for example.
My point here is that there is clearly a lack of leadership in my lab, but my lab has too many people and I have too much research to do for me to try to improve things. As much as I have tried, it really isn't my job or in my authority to manage them. I can't wait to get into industry where if people do this kind of crap, they're fired.I remember making the exact same complaints in graduate school. What I find most remarkable about this post (which is not a unique complaint) is a similar post by someone in a very different field:
Over the last eight months, I have led a company in Afghanistan to conduct various engineer missions. An active-duty company deployed on its own to fall under a National Guard battalion under an active-duty engineer brigade.
...The lesson that I learned relating to the aforementioned comments is this: We are a bureaucratic organization with rules, regulations, and doctrine that are sound and have been well researched, but we continue to flounder due to the lacking personalities and void of accountability. Understanding the art and science of warfare is enforced in schools, not in our formations....
...My personal battle has been with peers on battalion and brigade staffs. When I do not receive the information that I require, I demand it as it is required for success. The demanding is my unraveling. I have found myself in a pitched battle with officers junior to me calling me "bro," saying that I do not have tact, and then going to tell their respective commander that I do not play nice. I didn't know that I had to play nice. I thought I was selected as a commander to achieve a mission within my higher commander's intent....
...Perhaps this is why the top percentage is leaving the military. Not spouse careers, salary, benefits, upward mobility, or awards. Existing with other peers who do one-third the amount of significant output may be the real factor. At least that is my factor.Perhaps it's my lot in life to bounce around non-elite institutions of various sizes, but it seems to me that most organizations in this country muddle through and most have their malcontents and incompetents. Some companies do their best to weed them out, but that takes time and effort and judging who "isn't meeting expectations" is a hard science at best.
Organizations that are truly excellent from top-to-bottom are probably few and far between (no matter the size.) I wonder if I'm being overly pessimistic. Readers?
Wednesday, August 21, 2013
Submarine science, or doing projects on the sly
![]() |
| "Quiet! Management thinks we're doing that stupid Project A!" (Credit: metroactive) |
I was both surprised and not surprised to read this comment by Validated Target in a recent In The Pipeline thread on innovation:
..."loose cannons and mavericks" does not equal non-conformist innovators. The history of Drug Disco is filled with examples of the latter.
1. Cimetidine started out as a two-person project (chemist and biologist) who were inspired by Black's work on H2R antagonists. As it was told to me by those who were there, they were repeatedly told to stop work on the (back burner) project. As other SKF projects withered and died, pre-cimetidine results FINALLY merited further examination, the project was green lighted. Cimetidine / Tagamet saved SKF. The two guys who took the heat were non-conforming innovators.
2. I've heard that Prozac was a 2-man (chem + bio) project for a while at Lilly until it picked up speed. I think it was the biologist who, from the literature or a meeting, first wanted to go after an SRI. It was not some corporate committee that set a mandate or a glorified thought leader. It was a scientist with an idea and it worked and everybody took a pill and chilled out (and cashed in!).
3. I can't think of others cases at the moment. (IBM threatened to fire Bednorz and Mueller if they didn't stop work on the unofficial yet Nobel worthy superconductor project.)Later in the thread, London Chemist has another one:
the Germans working on gabapentin were repeatedly told to stop working on it by W-L's* US management.*Warner-Lambert
I think it is terribly interesting how often scientists will say "Oh, yes, sir, I've been working all day on Project A" and in a hidden hood somewhere, they're actually running Project B experiments, too. I've done it before, and I don't doubt that I'll do it again sometime in the future. In the classic New York Times Magazine article "Lethal Chemistry At Harvard", the chemistry students of Harvard actually had a name for it:
They spoke of ''submarine science,'' in which graduate students feel obliged to spend their days doing experiments suggested by their adviser -- even if they are certain they won't work -- and wait until after hours to try what they wanted in the first place.I wonder if advisers/managers ever realize that, chances are, their students/employees are working on something on the side? I wonder if they ever try to make sure to quash that behavior ("Johnson, I want 100% effort on Project A! 6 reactions a day!") or if they just don't care, just as long as Project A is meeting its milestones.
(I'll tell ya one thing -- if I'm ever the boss (that'll be the day), I just won't care.)
Thursday, April 18, 2013
Thought for the morning: "Powerpoint makes us stupid.", Gen. James Mattis, USMC
It's perhaps a repeat, but a good one:
“PowerPoint makes us stupid,” Gen. James N. Mattis of the Marine Corps, the Joint Forces commander, said this month at a military conference in North Carolina. (He spoke without PowerPoint.) Brig. Gen. H. R. McMaster, who banned PowerPoint presentations when he led the successful effort to secure the northern Iraqi city of Tal Afar in 2005, followed up at the same conference by likening PowerPoint to an internal threat.
“It’s dangerous because it can create the illusion of understanding and the illusion of control,” General McMaster said in a telephone interview afterward. “Some problems in the world are not bullet-izable.”One wonders if you could do a correlating chart between a decline in "real innovation" and the introduction of Powerpoint to US industry.
Friday, February 22, 2013
Was there, or is there, poaching between pharma companies?
A while ago, some documents relating to Palm poaching Apple technical staff surfaced. Here's a quote from Gizmodo's account:
I think there have been a variety of famous departures of medicinal and process chemists during the late 1990s and 2000s for new shores. But I wonder if it is/was common for pharma companies to entice each other's program managers over if/when they wanted to compete -- and, if so, if it happens much anymore? Did presidents of R&D (at the LaMattina level, say) ever call each other and made angry noises? I wonder if they ever called a truce, like Apple and Google decided to? (Such truces, of course, are 1) possibly illegal, 2) good for the corporations and 3) less good for individual workers -- 'twas ever thus.)
Notably, former Palm CEO Edward Colligan has made a statement which points out that the company was threatened with patent litigation if it didn't stop poaching staff from Apple. In the legal filing, Colligan explains how Jobs suggested that "if Palm did not agree to such an agreement, Palm could face lawsuits alleging infringement of Apple's many patents." An email which made up part of the discussions is pictured below, in which Jobs points out the asymmetry of the situation, writing: "I'm sure you realize the asymmetry in the financial resources of our respective companies when you say: ‘We will both just end up paying a lot of lawyers a lot of money.'"I don't really have much to say about the Palm versus Apple thing -- business ain't beanbag and corporations will do whatever it takes to get leverage and coercive power over other organizations.
I think there have been a variety of famous departures of medicinal and process chemists during the late 1990s and 2000s for new shores. But I wonder if it is/was common for pharma companies to entice each other's program managers over if/when they wanted to compete -- and, if so, if it happens much anymore? Did presidents of R&D (at the LaMattina level, say) ever call each other and made angry noises? I wonder if they ever called a truce, like Apple and Google decided to? (Such truces, of course, are 1) possibly illegal, 2) good for the corporations and 3) less good for individual workers -- 'twas ever thus.)
Thursday, February 7, 2013
Better labor relations = better product quality?
From the annals of "I'm skeptical", a brief (and rare) comment on chemical manufacturing in The New York Times by economics reporter Adam Davidson:
I don't doubt that Mr. Newcomb is correct and that things at ISP have gotten better from a labor/management point of view, but as a proud employee of NAICS 325, I am skeptical that we're getting the full story here.
For 25 years, Monty Newcomb has worked at the same chemical plant in Calvert City, Ky., making products that hold pills together and remove sediment from beer. In his early years, Newcomb watched his union, the International Association of Machinists and Aerospace Workers, lose one battle after another in its ongoing struggle with management... [snip] Newcomb told me that at his company, International Specialty Products, workers were disgruntled and the work suffered — for example, more than 20 percent of one chemical they produced didn’t pass inspection.
As a union steward, Newcomb feared that unless something changed, the plant would shut down and everyone would lose his job. So in the mid-’90s, his union asked management to attend its High Performance Work Organization Partnership program, which was creating a revolution in labor-management relations.
[warm fuzzy section about improving management-labor relations, improvements in efficiency, etc.]
And although the plant, now owned by Ashland Inc., currently exports about 50 percent of its product, it’s keeping production in Kentucky, where it recently invested $15 million in upgrades. “We make things so much cheaper than anyplace now,” Newcomb explained. Ninety-nine percent of that particularly pesky chemical now passes inspection.I would really, really, really like to know the backstory behind this, and why one particular product did not meet spec routinely, and how that might be connected to management-labor relationships. Count me skeptical, but there are a host of other factors that might contribute to improvements, like, I dunno, a change in the process? Or a change in the spec? Or new raw materials? Perhaps I am a novice process chemist, but if human factors are contributing to 20% of batches failing, it's probably not the operators' fault. (Or maybe it might be. I'm doubtful (and potentially very naive) about sabotage.)
I don't doubt that Mr. Newcomb is correct and that things at ISP have gotten better from a labor/management point of view, but as a proud employee of NAICS 325, I am skeptical that we're getting the full story here.
Subscribe to:
Posts (Atom)

