The Barbara Problem
Posted by Seligas@reddit | talesfromtechsupport | View on Reddit | 81 comments
I'm here to talk about Barbara. That's not her real name, for me or maybe you, but you probably have or have had a Barbara.
That coworker who cannot do a single ticket correctly, and in fact must redo every ticket threefold before they are finally resolved. You avoid responding to them in group chat. You know better now. If you answer, you'll become responsible for resolving their entire issue, but their name is the one that will go on the ticket. Trying to explain something to them, even something simple that is vital to their everyday job ends with you pulling out your hair as they attempt to repeat your words back to you and reveal their persistent misunderstanding as you listen to something that doesn't in the slightest resemble anything you just relayed to them. They even shotgun answers to every question asked in chat with no concern for whether the answer is correct or could add hours of extra labor and headaches for level 2 to sort out.
Finally, and this is the most egregious part of all, your boss is fully aware of their incompetence and refuses to do anything about it. Perhaps your boss knows something you don't. Perhaps Barbara is not a real coworker, perhaps instead they are an effigy, a totem strategically maintained to channel and consolidate the spiritual miasma of incompetence in one individual so as to ward the rest of the team against it. Or perhaps your boss simply derives catharsis and entertainment from your suffering. It is not for you to know. You merely know that to live is to suffer and to have a Barbara is to live in suffering.
I first became aware of Barabara on day one. She was assigned to train me. My workplace is a small company and very disorganized, so training involved throwing us onto the phone with no knowledge base to speak of or actual knowledge of our work at all, pretending we knew exactly what we were doing, and then begging our seniors in chat to, "please answer my question, I've been stalling this lady for twenty minutes and have no idea what to do."
When available, our trainers would ask us to ride along on some of their simpler calls or invite us to share our screen on Teams to walk us through something.
I asked my assigned trainer Barabara for her help exactly once.
Having done IT work before, I had gathered as much information as possible and taken extensive notes on the call I received. A single instance of our software on one machine would not connect, another adjacent machine on the same network could. It could be a server issue, but my experience told me it was more likely an issue local to the machine. I explained my suspicions to Barbara.
Barbara explained to me that it was probably an issue with the server and proceeded to immediately connect to the server we hosted for the customer. She insisted that sometimes if you fiddled with some things, turned stuff off and on, and disabled or enabled other things the issue would be fixed. I am not being vague on the details of her methodology for the sake of expedience, these are almost verbatim the exact words she used. To this day I have no idea what she was doing on the server for the excruciating half hour that followed as I forced a strained smile and reassured the customer that our, "resident expert" was looking into their issue. I think I do not want to know. Some knowledge is not for those who wish to remain of sound mind to know.
At minute twenty-five of listening to Barbara make strained sounds of confusion and frustration over Teams, I was getting desperate. Barbara was not listening to my insistent suggestions that perhaps investigating the local machine would prove more enlightening. Off to the side, I messaged another coworker who had been assigned to train a compatriot in much the same way Barabara had been assigned to me. He told me to hold on and that he'd take a look in a minute.
To my great relief Barbara by happenstance had an urgent appointment she needed to be on in five minutes and recommended I escalate a ticket to level 2 because this issue was completely beyond our ability to solve. I expressed my immense disappointment that she had to go but assured her that I'd get right on that as I surreptitiously connected the other senior to the computer I was working on. Within three minutes he opened the software, looked at it, checked the settings, closed it, opened an INI file, changed a 1 to 0, and gave the customer and me a concise and simple explanation as to why that change fixed it as he demonstrated that everything was working now.
I never made the mistake of asking Barbara for help again. In fact, I managed to consistently dodge her "training", expressing my truly heartfelt disappointment that our schedules seemingly never lined up as I silently parried her every submitted request for access to my Outlook calendar. She seemed genuinely sorry that she wasn't fulfilling her obligation to me, unknowingly being of far greater help to me in her complete absence. By the six-month mark, I managed to badger my other seniors in private messages for solutions to every problem I ran across until my own knowledge surpassed Barbara's limited skillset many times over despite her, as I learned later, three years of tenure over me.
Unfortunately, this fact is the only thing she managed to catch onto quickly, and soon I became yet another person constantly tagged in chat for her urgent self-made emergencies.
There are more stories. Many, many more of Barbara. Each of them a solitary towering peak of frustration and futility in a mountain range of constant incomprehensible interactions that leave me questioning my sanity and competence. But I'll leave you with just the one for now.
Diminios@reddit
I... think I might be the Barbara (Barbarian?) at our company. At least in part.
P5ychokilla@reddit
We had a Barbara in my office, Jill, her real name, she managed to misspell it constantly to "Jull", either through meaty fingers or a complete apathy to correct it, she thereafter became known as Jull.
Jull was moved to customer relations.
Naturage@reddit
I have a Barbarian in my team, luckily he joined after I was in a more senior role than him.
Barbarian's special talent is that he has great command of bureaucratese, so when you glance through an email from him, it looks great, fancy, and informative. Only when you need to actually figure out what he said - the whole thing, like an equation with far too many brackets, starts simplifying into... nothing.
The fact that Barbarian earns more than half of the team so far has led to one resignation, but I know two more who are considering it.
zeus204013@reddit
Why??? š§
fresh-dork@reddit
impresses the suits, so they give him bonuses
alf666@reddit
I know you're joking, but this is unironically the reason why.
This is also why IT never gets the funding it needs for anything, not just people.
It's because IT people massively suck at translating tech nerd language into stuff MBAs can understand.
Don't say this:
An MBA will hear this from your mouth instead:
However, if you say this instead:
An MBA will hear this:
matthewt@reddit
I was once running a team consulting to an in-house team at a client.
They were great, except for one person, who kept bugging us with questions they should already know the answer to (either because basic competence or because we already explained it to them repeatedly) and doing work that had to be redone from scratch because they'd completely messed it up.
I had a top level billing category created for said person and encouraged my team to log all of the time spent because of them to that.
Two invoices later they were transferred somewhere they weren't my problem anymore.
Chakkoty@reddit
THIS. I keep telling my colleagues to "collect evidence" so we can take it to the fixer uppers and present a case. Document everything.
Naturage@reddit
He came with several years of work experience to a team that mostly hires fresh from uni, which put him above 5 or so juniors. Our company structure is very rigid when it comes to raises and promotions, and largely determined by seniority. He'll be out-earning those five for years.
Also worth saying, I don't begrudge him. Man's got a silver tongue and leveraged that in the interview - good on him. I just wish for more competent colleagues.
Valheru78@reddit
I used to have a boss (owner of the company actually) like that, the man could use the most flowing language, spit out lots of intelligent sounding long sentences but when you really listened you noticed that he was using lots of words to say absolutely nothing.
Born salesman but when the operations manager left the company and he started managing us by himself we also noticed that he was only interested in hearing himself talk and was very good at screaming at his employees, never seen a company lose so many employees in such a short time.
LVDave@reddit
Sounds like your "Barbarian" is a "word-salad" chef..
LoathsomeNarcisist@reddit
I used to translate corporat-ese emails into English for my engineer boss.
Most broke down to 'They want you to waste time reporting to more people about why less work is being acomplished'
He told me it was nice to have someone on his team who was fluent in 'weasel'.
The_Sabretooth@reddit
That's management material!
deeppanalbumparty_@reddit
Or is it manglement material?
pocketpc_@reddit
That was a brilliant way of describing the way that my manager writes emails, thank you
harrywwc@reddit
yeah, I've come across many 'manglement' doc's that are, at the end of them, semantically null. pages and pages that all come up to just "word salad".
androshalforc1@reddit
My barbera was Dave. Whenever communicating with Dave you need to understand the 50/50 rule, he would only hear 50% of what you told him, and he would pass on 50% off what he heard.
He was also deathly afraid of admitting to his own mistakes even minor ones. There was always an excuse, always someone else. even when we could clearly point out that the problem was his. If you canāt admit your mistakes, you canāt learn from them.
YankeeWalrus@reddit
I offer you this wisdom, perhaps the only thing of value you get out of knowing Barbara:
No one is completely useless. One can always serve as a bad example.
PrinciplePleasant@reddit
I'm in healthcare IT, which has a necessary overlap between clinical and technical analysts. My Barbara was an older nurse who left the bedside for the IT side...but to this day, I will never understand why somebody ever approved that transition. I joined a team after she had left it, heard horror stories about what it was like to work with her, and then got to experience Barbara firsthand when she re-joined our team (under a different manager than she'd had before). Barbara was fond of telling people that she's "not a computer person" and needed help resolving literally every ticket that wasn't a clinical workflow question. Barbara was a major factor in my eventually leaving that team, and she finally retired recently. Working with her was so scarring that just hearing her voice on project calls made my skin crawl for years after I switched teams.
Dunnachius@reddit
She lost her medical license (as a nurse, med tech, doctor, whatever) and still knew someone corrupt enough to ensure she kept a job?
PrinciplePleasant@reddit
She didn't lose her licensure, just wanted to get away from direct patient care. There are a lot of healthcare careers (including but not limited to IT roles) that require RN licensure but don't involve patient care.
ToucheMadameLaChatte@reddit
I have unfortunately been the Barbara while on-call for my job before, specifically when it came to our sftp programs. We've got an absolute mess of sftp jobs with similar names on our production servers and counterparts on the sftp server outside of the firewall that our clients use to exchange files with us, and every time we have something go wrong I have to relearn how to do it and more often than not had to reach out to someone else for help.
I have since found the documentation for our sftp jobs, so hopefully I will no longer be the Barbara. But at least at my worst, I was still aware that I knew nothing and didn't spout off incorrect answers to others.
Dunnachius@reddit
You canāt be Barbara unless youāre in total denial of your incompetence.
micaturtle@reddit
No, my beautiful Madame LaChatte, you are NOT a Barbara. I work with a 30-40 person call center helpdesk. I am always glad when people ACTUALLY reach out for help, and the person you reached out to should have linked you to that documentation to begin with (after helping you with your issue) Barbaras are the ones you have to tell the same thing to multiple times, the ones who after you link them to a knowledge base article with the info, continue to ask the same question because they're too lazy (or dense) to read it. They are the ones who send tickets that say "computer not printing" with no printer name, no computer name, and no troubleshooting done at all.
We've all had snafus, and times when we are confidently incorrect. It's inevitable in a job that is as heavily knowledge based as tech support. It's what you do after your knowledge gap is corrected that makes the difference.
langlier@reddit
I've worked with many Barbaras. I've made the claim that I could turn a trained monkey into a competent helpdesk person. My Barbara's have challenged that... Mostly its either a lack of confidence or an overabundance. In either case it's a refusal to learn and adapt.
Taulath_Jaeger@reddit
It has been said that there is a significant overlap between the least intelligent humans and most intelligent monkeys...
sincereferret@reddit
I watched āInside Outā and saw how the ONLY person who actually āread the Manualā was the emotional Sadness.
But some people wonāt read the manual no matter what.
And often the people who write the manual donāt want it followed.ā¹ļø
oloryn@reddit
I've had multiple jobs where being willing to read the manual made you "the expert" on too many things, resulting in either being spread too thin, or being overworked.
sincereferret@reddit
So true.
Drazilou@reddit
I have a Barbara too... Sort of. I work in IT, development, and they have great technical knowledge (surpassing my own), BUT...
They have tunnel vision/no overview of what's happening. They catch on to (part of) the problem and LOOK NO FURTHER. Related issues are 'other' issues to them.
Or they find some other irrelevant problem that needs to be fixed (probably true, but that doesn't solve MY problem), and then try to explain to me that this HAS TO be fixed, and doesn't listen when I try to lead them back to solving my problem first (the new found thing can go on the backlog), so I can get on with my work.
Or they try different solutions that DO work, but create other/more/bigger problems elsewhere (which is why I didn't apply those solutions).
I find myself cleaning up their mess, straightening their stories out and answering simple questions they took on a wild ride, deep into the technical side, confusing other parties we have to work with..
They're like a bull in a porcelain store, but also the one with the longest tenure and most/deepest technical knowledge about the application...
DukkhaWaynhim@reddit
Ah, yes, the Hellraiser Method, where they solve puzzles that open portals to Hell...
the_syco@reddit
The great knowledge of a subject, but severe tunnel vision reminds me of someone I knew. He is on the spectrum, but knows he's on the spectrum, so he tries not to go full tunnel vision. But being on the spectrum seems allows him to master the application beyond a lot of other people. I'm thinking your Barbara may be on the spectrum.
Stryker_One@reddit
Is Barbara havening issues?
trro16p@reddit
You mean she is related to George?
Stryker_One@reddit
Is that a scary thought?
ChooseExactUsername@reddit
I haven't read a "havening" story in a long time. "George" fills me with dread of a new Remedy ticket. Yes, we use Remedy at work. Yes, it amazes me on how people I work with can #$=#@ a ticket so bad.
We all have our Barbaras and Georges and ...
the_syco@reddit
Work with a Kendal. Unfortunately it's hard to sack someone in the public service. He causes three times the work, as you have to get someone to check his work, and then someone else to fix what he had "fixed".
ac8jo@reddit
Or Barbara is related to one of the owners/high-ranking idiots. Or something like that.
The shame is that she's assigned to train you, and it sounds like it should be the other way around.
the_syco@reddit
Sometimes you wonder who the Barbara is related to, or if she's a mistress...
VTi-R@reddit
Maybe she is George's sister.
the_syco@reddit
I just read two of George's tickets. I wonder if I knew George.
MikeTheMuddled@reddit
I came here to say this. Bless you, sir. Ahhh....The Chronicles of George. Fond memories...
12stringPlayer@reddit
I am havening a flashback right now, hadn't thought about George in years.
Fritzzy1960M@reddit
Barbara and George could probably have combined chronicles!
MCoH13@reddit
We refer to our resident Barbara as "Jar Jar".
Maybe we should adjust it to "Bar Bar" now... š¤
harrywwc@reddit
Bar Bar Jinx?
MCoH13@reddit
š¤£ Love it!
mathwiz617@reddit
Yep, I know Barbra. Our site has a standard method of telling different projects apart, as dictated by the customer. Our Barbra was brought in from a different site that deals with different customers.
Barbra took one look at our system, claimed it made no sense, she alone could fix it, and she was going to tell the customer that this system written in the contract that had been used longer than Iāve been alive was wrong.
Barbra still works for our company. I have no clue how. I think she was āgivenā PTO whenever the customerās higher-ups visited.
amygdala23@reddit
I love your suggestion that Barbara may not actually realĀ
pockypimp@reddit
At my previous job our boss liked to use contractors initially. Basically to get a feel for the abilities and if the contractor was good see about hiring them in after a year. That's how I got hired in and a couple of my coworkers.
Then we had what OP would call a Kendal. Kendal was about my age (at the time mid-40's) so used to the old DOS days. He claimed to have mainframe knowledge and things like that. A lot of stuff not necessary in our L2 Infrastructure work and we had some "unique" software that had to be dealt with on the Applications team side.
We would sit in meetings bi-weekly with our boss. Being that he was the newest in the group my coworker, my boss and myself would talk about tickets, upcoming projects and any solutions we found. So the meeting was a good forum to bring up questions and how to's. Kendal would ask or be told how to identify and solve an issue. He'd take notes, he'd be writing things on his notepad. Then hours later or more he'd ask for the same information we discussed in the meeting. At one point he had asked how to resolve an issue 3 meetings in a row. Each time he was given the same instructions. The following meeting he asked again and our boss asked "You asked that last week, and I think the week before. I see you taking notes, are you not reading them?"
harrywwc@reddit
"write only notepad"
Jonathan_the_Nerd@reddit
/r/StoriesAboutBarbara
Make it happen.
ChooseExactUsername@reddit
Yes, vote number two. OP's writing style and skill would make a enjoyable read.
I'm sure we all have "Barbara" stories but I can't write good.
I had "no shut Cindy" who could not and should not have been allowed to logon to routers. Most problems were "Cindy, did you you enable the interface?" followed by the answer "That darn 'no shutdown' command, I forgot about that." Every day, day after day, month after month, year...
GenericUser237@reddit
You have my sympathies. I also work with a āBarbaraā. My āBarbaraā asks for my help multiple times a day and routinely ignores my advice to go in completely the wrong direction with the tickets heās working on. Many of those end up breaching SLA because of his incompetence.
TastySpare@reddit
I'm surrounded by Barbarasā¦
Fixes_Computers@reddit
I shave my head as a prophylactic measure.
PotatoInBrackets@reddit
nice story, you're really a good writer, I'd love to read more!
sincereferret@reddit
A totem of āspiritual miasma and incompetence.ā
I believe some of my coworkers could be her.
cwthree@reddit
Suddenly, the ongoing employment of certain people make a lot more sense.
ricebasket@reddit
Can we cut it out with giving womenās names to archetypes that annoy us?
A_Unique_User68801@reddit
BE MORE INCLUSIVE.
NO, NOT LIKE THAT.
Seligas@reddit (OP)
I've worked with incompetent men too, I just have a very specific woman I work with that I wanted to complain about. If it had been a guy, I would have used the name Kendal.
micaturtle@reddit
I work with a Barbara (and, coincidentally, she was a trainer for part of my training too!) When I applied for senior position, they asked me if I would be okay if someone else got the role. I told them I would be absolutely fine if someone else got it. However, if "Barbara" got the position because of seniority, I would flip tables. Thankfully, she did not get it. She's still in helpdesk, banging out mediocre tickets that we all have to fix when eu inevitably calls back.
tesseract4@reddit
There was a Barbara in the tech support center I used to do L2 work for. She started while I was working there, and training her was an exercise in futility. There was never any retention of any information between calls for her. You got the distinct impression that when you explained how to perform a marginally-technical task that she didn't understand, because she didn't know what things like "Desktop" and "Folder" and "Control Panel" meant. It was excruciating. I have since learned, having left that place long ago, that she's still working there, and, at 20 years in, is the most senior L1 in that department. I'm also told she hasn't gotten any better at it, but she shows up on time and answers the phone.
macphile@reddit
My father likes to say that 90% of work is showing up. The people who are there every day get the projects, sometimes the raises and promotions...the people who are out sick a lot or miss meetings, they get shit. They'd rather have someone who's there and picking the phone up and sort of vaguely trying and polite than someone who's brilliant but isn't there to pick that phone up.
AskReddit2012@reddit
Our Barbara also did things like request high back leather executive chairs and monitor privacy screens the first time we solicited the desk for anything they needed on an Office Depot order we were making (for things like notepads, pens, post it notes, etc). We usually put in a shared order to minimize paperwork since it was all coming out of the same budget.
It was her first corporate job, and Iām still shocked the lack of high back leather executive chairs that her peers were not using didnāt give her a clue that maybe her request was a touch out of bounds.
NotTheOnlyGamer@reddit
Hey, if you don't ask, you can't receive. I respect anyone who wants to get a comfy chair.
AskReddit2012@reddit
You know those times in your life when you say to yourself if you donāt ask, you donāt receive, itās really a double edged sword. Sometimes you just shouldnāt askā¦
True, you could get what you ask for if you just ask for it. But if the request is so far out of the norm that it makes you look foolish or ignorant, then thatās what people will remember and will not take you seriously in future interactions.
Dragonstaff@reddit
Good story. Your writing style reminds me of u/lawtechie and his 'Ian' stories.
Dougally@reddit
Is Ian a male Barbara?
gallifrey_@reddit
epic Doctor Who (1963) reference
ryanlc@reddit
Pretty much, yup. Ian was/is a complete tool.
sheikhyerbouti@reddit
I had an entire department filled with Barbaras.
They were also located in the owner's country of birth, so they were immune to any criticism.
I'm glad I no longer work there.
Vogete@reddit
I had to deal with 5 Barbara's at my previous work. One turned okay after 4 years. Lots of frustration but finally he was doing alright.
Two others luckily left quite soon, one of these was a very cocky Barbara. He always thought he knew everything better, despite the constant failures and proof from multiple people that they were wrong. He refused to believe that someone with his education can be wrong about anything.
One of them was fired, because despite being a Barbara, he never actually showed up to work. Those were the better days, because when he showed up, that's where you had a real bad day.
And the last one is still going strong, the biggest and highest ranking Barbara of all. She is beyond incompetent. If you write more than one sentence in an email, she cannot comprehend it. She is unfortunately someone with power and responsibilities, but she cannot fulfil anything. She's not a bad person but you can't reason with her due to her incompetence.
zeus204013@reddit
Low iq?
deadsantaclaus@reddit
Many businesses suffer from the philosophy of āwarm body syndromeā.
You never replace that warm body.
hillsfar@reddit
For over a decade, I worked alongside such a person. I literally had only been on the team for a few weeks when they came to me, asking for help on problems despite being the same team for 5 years.
I and others were constantly asked to fix his mistakes. People would just hang up and call I again if they got him, hoping to get someone else.
The only reason you could think of that he would survive whole rounds of layoffs of others far more competent, was that he was a visible minority of a particular group where he was the only one of that historically oppressed minority, and he was a veteran, and he was the sole breadwinner for his family, including kids, which likely factored into our boss constantly protecting him.
Finally, around the time that we had a few others of the same minority doing extremely well, I guess they were able to let him go.
diabolic_recursion@reddit
She should open a rhubarb bar in Germany...
Just a joke about Rhabarberbarbara, her Rhabarberbarbarabar or her main customers, the Rhabarberbarbarabarbarbaren (rhubarb-barbara bar barbarians), which by the way has existed for waaaaay longer than tiktok.
Rahbek23@reddit
We sort of work with one, one of our clients which we provide support for. Some clients develop themselves, and they are one of them, so we are just in a advisory role. Anyway - she has been there for an eternity (like 20 years), is actually quite knowledgeable about the business and their numbers (she's is/was a controller) and a nice pleasant person overall.
But she DOES NOT EVOLVE.
The way she is developing has barely changed, ever. Stuff like she will have a scripts called xxx_2020, then xxx_2021 etc, often with no other change than a filter on the year. Hideous scripting for so many reasons. An obvious way to deal with this would be to just loop over each year, and good that feature is readily available.... since 2006 I believe.
On top of that she is also a controller as I said, so she has a tendency to completely get locked in on tiny corners of something rather than seeing the bigger picture. But I think that's an occupational damage judging by a lot of controllers I have worked with.
Left_of_Center2011@reddit
To quote the legendary Blazing Saddles, āyou use your tongue purtier than a twenty-dollar whoreā
k6lui@reddit
I had two Barbaras in my career so far, the first one had a disability and therefore the position was near fully financed by our government so the little work which was put out was still bringing in money, the other Barbara only made it through probation by sleeping with our boss. Fun times