Skip to main content

Command Palette

Search for a command to run...

A note on the detriment of Jargon

Updated
2 min read
A

Professional software engineer working at CoverMyMeds, an enterprise healthtech firm that ensures patients get access to the medication they need.

Primarily focused on backend and systems design through Ruby and Elixir, but experienced with JavaScript and all things frontend

Interested in learning and teaching the craft of software; technical or otherwise

Join me as I innovate by iterating!

I work on decreasing patients' Time to Therapy in the HealthTech space. As such, I have to communicate with many external stakeholders about highly technical decisions. There are ridiculous amounts of jargon that have to be plowed through before any human understands what's being discussed.

From FRMs, PSCs, to FIAs, DTRs, ATRs, to RMTs, NPIs and NCPDPs, it's easy to get lost. This increases ramp-up time and I reckon it's the leading cause of why developers at our company struggle so much in their first 1-3 months. I know this because here I am, two years later, and I still have trouble keeping my eyes open during some of these meetings. It's hard to build context and understanding when vocabulary poses such a large issue.

I had a conversation earlier today that was so inundated with jargon, it struck me that it would be completely unintelligible to an outside audience.

I had a question about my work and I asked for help. Instead of getting an answer to what was a relatively easy question, I had to work back and forth with someone to make sure we had our terms defined and understood what each other was talking about.

It's not just that these conversations are painful and horrible and bad.

It's that they're fat, and we'd do well to trim it.

Most conversations that we have at meetings have questions on such a fundamental level, e.g. "What does ABC mean?", and we have a lot of groundwork to cover before we can begin talking about any given topic.

We would do better to eliminate as much jargon as possible to enhance our ability to communicate and understand these topics.

Consider this a plea; Stop jargon.

Simplify your speech.

Watch others' eyes stop glossing over in the middle of your meetings.

What do you think? Is this a problem in other fields, or a unique one to Health?

Thanks for reading

Austin

Y

You guys just need to hammer out a list of terms and their definitions that you all agree on. Nobody's getting anywhere fast if you have to spend ¾ of each meeting defining O notation, "web server," "object," "base class," "sorting," "database," yadda yadda yadda

1
A
Austin2y ago

Yeah definitely agree that building that common language is important. Unfortunately in my experience lots of teams build no such thing, and instead stumble gracelessly through slogs of language

Instead of building a common index of important terms, providing lessons and lectures and communication surrounding our language, we simply hope for learning through osmosis. Lots of unnecessary manual work, repetition, and frustration in that process IMO

2
Y

Austin Yup, someone's going to have to step up and nail down a list of terms and their definitions that everyone can refer to. I wonder who will end up getting voluntold to do it?

More from this blog

A

austn.net

17 posts

Software engineer working at an enterprise HealthTech firm helping patients get access to medicine they need.

Sharing Ruby on Rails tips & tricks and career insights to level up developers.