WEBVTT
00:00:07.509 --> 00:00:13.756
Hi, I'm Carl from OSP and this is Communicate Connect Grow, the OSP podcast.
00:00:13.756 --> 00:00:20.342
On today's episode, we're talking about avoiding jargon in your writing with the editing code CNECT.
00:00:20.342 --> 00:00:29.455
If you want to be a more effective writer, a more transparent editor, develop clear strategic thinking or learn from our network of expert friends and colleagues.
00:00:29.455 --> 00:00:30.801
That's what we're here for.
00:00:30.801 --> 00:00:36.832
We divide our episodes across three themes Communicate, Connect and Grow.
00:00:36.832 --> 00:00:44.281
This is a Communicate episode and we're talking about connecting with your audience with our editorial code CNECT.
00:00:44.281 --> 00:01:08.587
The Connect editing code falls into the style and phrasing phase of the editing process and it's about using words and clear language.
00:01:08.587 --> 00:01:20.251
In our documentation about this code, it says use language that will connect with your target audience, but avoid jargon that will prevent non-experts from gaining value from your writing.
00:01:20.640 --> 00:01:24.668
Hi, I'm Jam that is short for Jeffrey Alexander McGuire.
00:01:24.668 --> 00:01:35.912
I had the great good fortune to start Open Strategy Partners with my business partner in 2017, and here we are recording in 2023, and we're still talking about it.
00:01:35.912 --> 00:01:55.010
Back in the early days of the company, I was the writer and the editor and Tracy was the structure and ideas and strategy person, and when I would edit her writing, she would get upset and ask why I did something and why I made a change.
00:01:55.010 --> 00:02:12.144
Over time, we came to the realization that if we had a set of codes that explained what I was doing, that that would help her let go of her precious words and come to an improved overall result.
00:02:12.144 --> 00:02:12.967
And here we are.
00:02:12.967 --> 00:02:21.933
The Connect code is similar to many of the other codes we use, but it's got its own flavor.
00:02:21.933 --> 00:02:25.449
The Connect code is about applying empathy.
00:02:25.449 --> 00:02:28.068
Our codes talk about being clear.
00:02:28.068 --> 00:02:34.025
They talk about building trust with the audience and they talk about empathy, which also, of course, goes towards building trust.
00:02:35.039 --> 00:02:46.370
I need to make sure that an article that I'm editing is pitched in a way that's appropriate for the audience that I'm expecting to read it.
00:02:46.370 --> 00:02:53.382
If it's for developers, it should be kind of no nonsense and absolutely can be highly technical.
00:02:53.382 --> 00:02:58.030
If it's for marketers, it probably should be less technical.
00:02:58.030 --> 00:03:03.531
For example, to connect with the marketer, I need to talk about achieving a marketer's goals.
00:03:03.531 --> 00:03:10.012
The language and the way it's written should connect with the target audience.
00:03:10.012 --> 00:03:10.573
There you go.
00:03:10.573 --> 00:03:15.730
It should show them the information they need in a way that is easiest for them to consume.
00:03:16.420 --> 00:03:17.344
I'm Christine Bueller.
00:03:17.344 --> 00:03:34.132
I'm a communications consultant at OSP, where I work on creating blog posts and marketing materials for our often but not always open source and technology clients.
00:03:34.132 --> 00:03:53.653
The Connect editing code is about using language that lands well with your target audience, but also avoiding jargon that will prevent other people from getting value from your writing.
00:03:54.400 --> 00:03:59.209
I'm Chris Fenwick and I do copywriting at OSP and also editing.
00:03:59.209 --> 00:04:06.222
I mean, I think of it primarily as being about avoiding extremely dry jargon.
00:04:06.222 --> 00:04:17.644
Actually, it's about making sure that the audience that you're writing for will respond or, like that, the piece will maybe resonate with them in some capacity.
00:04:17.644 --> 00:04:33.632
So I think it's not just about it's about, in some sense, not being excessively dry and technical, but also coming up with ways that will make them see the relevance of what you're saying to them or that they will respond to more emotionally maybe.
00:04:34.334 --> 00:04:34.694
G'day.
00:04:34.694 --> 00:04:40.656
I'm Felicity Brand, I'm a communications consultant at OSP and I write and edit all day long.
00:04:40.656 --> 00:04:56.423
The CNECT code falls into our style and phrasing phase and it's about using language that will connect with your audience and avoiding jargon that will prevent non-experts from gaining value from your writing.
00:04:56.423 --> 00:05:02.298
Anne Handley has a very famous book Everybody Writes and she compares jargon to cholesterol.
00:05:02.298 --> 00:05:04.290
She said there's a good and a bad kind.
00:05:04.290 --> 00:05:18.980
So I suppose the good kind is it can signal belonging if you're using insider terms that are familiar to your audience, but mostly it's the bad kind, okay.
00:05:18.980 --> 00:05:27.721
So too often jargon will alienate or exclude a reader who isn't on the inside, and at OSP we write for everyone.
00:05:27.721 --> 00:05:32.276
So while jargon can be tempting, the risk is too high.
00:05:32.276 --> 00:05:45.338
This editing code aligns with our pillar of empathy and we have another very similar editing code about language choice, which is term Check out that episode and that's about getting the names of technology correct.
00:05:45.338 --> 00:05:50.733
But CNECT is about avoiding jargon and using language that everybody can understand.
00:05:51.596 --> 00:05:57.173
Some examples of jargon Growth, hacked, incentivize, synergize.
00:05:57.173 --> 00:05:59.199
They're sometimes called non-words.
00:05:59.199 --> 00:06:02.269
They don't convey a lot of inherent meaning.
00:06:02.269 --> 00:06:08.449
In my research for this episode, I came across the term smarketing as an example of jargon.
00:06:08.449 --> 00:06:11.519
I did not understand that term.
00:06:11.519 --> 00:06:19.923
It means sales and marketing alignment through constant communication, and apparently it was coined over 23 years ago.
00:06:19.923 --> 00:06:21.848
So apparently I'm 23 years too late.
00:06:21.848 --> 00:06:24.738
So that's a really good example.
00:06:24.738 --> 00:06:27.389
Smarketing is a really good example of word choice.
00:06:27.389 --> 00:06:34.406
That would definitely put up a wall between readers on the inside who understand the term and readers on the outside who don't.
00:06:34.406 --> 00:06:47.627
Effectively, that's excluding me from this content that I might have been able to gain a lot of value from, but this one word just was kind of like a closed door to me.
00:06:49.815 --> 00:06:51.970
Let's explore how you use this code as an editor.
00:06:53.153 --> 00:07:03.245
The connect code helps remind us to apply empathy when we're creating our communication, to think in terms of hey, what is my audience need?
00:07:03.245 --> 00:07:04.370
That's the information that goes in.
00:07:04.370 --> 00:07:08.199
How will they best receive it?
00:07:08.199 --> 00:07:19.660
That goes into my choice of words and structures and perhaps the metaphors that I want to use different for a project manager than a marketing executive, for example.
00:07:20.540 --> 00:07:33.992
Yeah, as an editor, connect or "scenic avoiding so reading jargon can mean a lot of wasted time for an editor.
00:07:33.992 --> 00:07:52.553
Editors naturally want to be efficient and it's hard to be efficient if you have to pause and look up words multiple times in a single paragraph, let alone an entire piece of writing.
00:07:52.553 --> 00:08:03.370
It can really slow you down and it's also taking your attention away from your main job, which is editing and shaping a piece of writing.
00:08:03.860 --> 00:08:08.216
I think I would probably use it just positively rather than negatively.
00:08:08.216 --> 00:08:15.793
So if I felt someone had done a good job of making some technical issue resonate, then I would point it out.
00:08:15.793 --> 00:08:32.710
I think it's a difficult one, because the reasons for which a piece of writing might not connect could also be covered by a number of other codes besides just this one that could also explain why it wasn't doing what you wanted it to.
00:08:32.710 --> 00:08:39.744
So I think I might have ended up using some other codes instead if I felt like something was wrong with the writing.
00:08:40.399 --> 00:08:47.326
As an editor, you're more able to spot jargon or language that you don't connect with because you're coming in with fresh eyes.
00:08:47.326 --> 00:08:52.149
It may be business or industry jargon, or it may be buzzwords.
00:08:52.149 --> 00:09:05.063
When I'm editing, I'll use this code to flag opportunities for choosing other phrases and I'll typically suggest any that come to mind, or I'll check with the author if that word choice was intentional.
00:09:05.063 --> 00:09:13.004
And I also use this code a lot for positive feedback so that I can celebrate word choice that the author has made.
00:09:13.004 --> 00:09:15.267
That's what makes these codes so flexible.
00:09:15.267 --> 00:09:19.711
You can use them to flag things to check for other opportunities.
00:09:19.711 --> 00:09:25.581
You can also use them to just celebrate a great word choice and reinforce good writing habits.
00:09:28.000 --> 00:09:28.522
As a writer.
00:09:28.522 --> 00:09:30.307
How do you approach this code?
00:09:30.700 --> 00:09:38.825
The most useful part of the connect code when I'm drafting is trying to catch myself not using jargon.
00:09:38.825 --> 00:09:53.072
Jargon when it goes unexplained will often exclude outgroup people or people who are not experts in a given topic yet will hinder them learning.
00:09:53.072 --> 00:09:59.472
And it's easier for us to be inclusive if we are avoiding jargon.
00:09:59.472 --> 00:10:02.129
And now we have a couple of other codes that help us with this.
00:10:02.129 --> 00:10:18.011
We have one called term, and I think there might be another one that's acronyms, I think where basically the rule is, if we have a piece of jargon that's essential to explaining what we're talking about, then we're going to have to step back and explain it.
00:10:18.011 --> 00:10:19.764
And is that a parenthetical?
00:10:19.764 --> 00:10:20.528
Is it a set of links?
00:10:20.528 --> 00:10:22.386
Is it another linking to another article?
00:10:22.386 --> 00:10:28.312
But you can't just leave jargon in place and expect that it's going to be as effective as it could be.
00:10:28.759 --> 00:10:47.350
And, as a writer, when I'm using connect, part of the very beginning of a piece is knowing your target audience, but you don't want it to be so small that it isn't welcoming to anyone else.
00:10:47.350 --> 00:10:57.125
As a writer generally, you want your work to be shared and you want it to be helpful to as many people as possible.
00:10:57.125 --> 00:11:14.900
You know, a thick and fast use of jargon is almost like reading a different language or reading an academic paper meant for only other academics, so that prohibits your work from being accessible to other people.
00:11:15.409 --> 00:11:22.043
I think the general principle is there in the background, but not necessarily a conscious awareness of the codes.
00:11:22.043 --> 00:11:31.284
I think when there's really specific things like technical terms to define and so on, then there are more obvious codes and principles that come to mind.
00:11:31.284 --> 00:11:41.585
I think it's more a case of just like how can you write an introduction that is going to be lively and get somebody's attention and show them the relevance of what you're doing?
00:11:42.090 --> 00:11:47.639
I have a guilty admission as a writer, I'm not thinking about the CNECT code.
00:11:47.639 --> 00:11:57.322
I often rely on jargon, and that's because I'm lazy, so jargon is a really useful shorthand when you want to get your ideas out.
00:11:57.322 --> 00:11:59.634
I'll often use jargon as a placeholder.
00:11:59.634 --> 00:12:15.803
When I'm writing, I'm getting my thoughts out and then once I feel like I've formulated my argument and I'll do another pass to replace jargon or replace empty cliches with more meaningful or clearer expressions.
00:12:15.803 --> 00:12:17.511
It's challenging.
00:12:17.511 --> 00:12:20.195
You can't always see it when you're deep in it.
00:12:20.195 --> 00:12:26.965
As a writer, you can't always spot your jargon, and that's where you rely on your friendly editor and their fresh eyes.
00:12:29.354 --> 00:12:31.278
For the reader to have a great experience.
00:12:31.278 --> 00:12:34.323
Here's why this editing code is extremely important.
00:12:34.690 --> 00:12:45.770
As a reader, I don't want to feel left out If you throw a whole bunch of information at me that I need because I'm trying to make an informed decision about spending my harder time and money.
00:12:45.770 --> 00:13:04.847
I want to feel like I really understand what's going on, and if you shut me out by expecting a certain amount of knowledge that's inappropriate for my level of experience or my needs from your product or service, it's going to be really, really hard for me to make the decision to try you out.
00:13:05.570 --> 00:13:06.412
For readers.
00:13:06.412 --> 00:13:17.846
Connect is important because jargon kind of locks you out, especially if you're newer to a certain subject.
00:13:17.846 --> 00:13:28.804
It might prohibit you from reading that specific piece of writing, but it also might discourage you from learning more about that topic at all.
00:13:28.804 --> 00:13:34.149
You might think, well, this topic is clearly too complex.
00:13:34.149 --> 00:13:35.793
I've changed my mind.
00:13:35.793 --> 00:13:38.138
I don't want to learn about this anymore.
00:13:38.138 --> 00:13:41.043
At OSP we definitely don't want that to happen.
00:13:41.630 --> 00:13:49.692
All the codes are ultimately aimed at the reader, actually, not just some of the style or phrasing ones, and again I think they're always.
00:13:49.692 --> 00:14:01.371
Their success is usually there for a reader when they're not visible, like the reader shouldn't be sort of alienated from the piece or reflecting on it too much, it should just be.
00:14:01.371 --> 00:14:10.129
The point of the code is to guarantee writing that is effective, not writing that necessarily makes you step back from it and wonder, like what's wrong with this?
00:14:10.711 --> 00:14:13.139
As a reader, I think the author is lazy.
00:14:13.139 --> 00:14:23.149
If I encounter a lot of jargon or non-words, I'll think maybe this article was just written for SEO purposes and doesn't contain anything meaningful for a human.
00:14:23.149 --> 00:14:25.052
So I'll quickly leave.
00:14:25.052 --> 00:14:32.745
You're losing a really great opportunity to connect with your audience if you don't choose words that everyone can understand.
00:14:49.062 --> 00:14:53.105
I hope you, dear listener, have not spotted any jargon in this episode.
00:14:53.105 --> 00:14:55.907
If so, we sincerely apologize.
00:14:55.907 --> 00:15:04.803
Next time you start creating a piece of content, sidestep the non-words and try to use real, clear language that everybody understands.
00:15:04.803 --> 00:15:14.024
Share your examples or questions with us via Twitter, at open underscore strategy, or email hello at openstrategypartnerscom.
00:15:14.024 --> 00:15:18.717
This was one of the editorial codes we use at OSP.
00:15:18.717 --> 00:15:20.782
We'll be sharing more of them as we go.
00:15:20.782 --> 00:15:35.083
If you'd like to learn more in the meantime, come over to openstrategypartnerscom, have a look at our writer enablement workshops, case study offering or get in touch to talk about your strategy or product communication needs.
00:15:35.083 --> 00:15:40.500
Thanks to everyone who contributed to this podcast, all the P's at OSP.
00:15:40.500 --> 00:15:42.562
Thanks to our clients who believe in us.
00:15:42.562 --> 00:15:51.604
Shout out to Patrick Gaumont for our high energy maple syrup flavored theme music and to Mike Snow for additional horn arrangements.
00:15:51.604 --> 00:15:57.621
Thank you for listening and subscribing about our three themes on the podcast.
00:15:57.621 --> 00:16:01.880
You'll hear from different members of the OSP team hosting episodes over time.
00:16:02.350 --> 00:16:12.347
Communicate All things communication we share how we tackle writing, editing, word choices, formats, processes and more.
00:16:12.347 --> 00:16:24.149
Connect In-depth conversations with interesting, smart people about who they are, what they do and how they approach their life and work as communicators, technologists and leaders.
00:16:24.149 --> 00:16:35.125
Grow, we cover strategic approaches to understanding and expressing the value of what you do, including tools, templates and practical applications.
00:16:35.125 --> 00:16:41.065
We also feel strongly about building a mindful, positive, human first culture at work.
00:16:41.065 --> 00:16:43.149
That's bound to pop up from time to time too.
00:16:43.149 --> 00:16:50.903
This podcast is us figuring out communication, connection and growing together.
00:16:50.903 --> 00:16:56.042
Subscribe now on YouTube, apple Podcast or the podcast channel of your choice.
00:16:56.042 --> 00:17:00.297
Follow us, suggest guests and topics, ask us questions.
00:17:00.297 --> 00:17:06.131
On social media, we are at open underscore strategy on Twitter Until next time.
00:17:06.131 --> 00:17:08.913
Thanks for listening to Communicate, Connect.
00:17:08.913 --> 00:17:11.696
Grow, the OSP podcast.
00:17:42.755 --> 00:17:46.557
Well, the knee bone is connected to the thigh bone and the thigh bone is connected to the hip bone.
00:00:07.509 --> 00:00:13.756
Hi, I'm Carl from OSP and this is Communicate Connect Grow, the OSP podcast.
00:00:13.756 --> 00:00:20.342
On today's episode, we're talking about avoiding jargon in your writing with the editing code CNECT.
00:00:20.342 --> 00:00:29.455
If you want to be a more effective writer, a more transparent editor, develop clear strategic thinking or learn from our network of expert friends and colleagues.
00:00:29.455 --> 00:00:30.801
That's what we're here for.
00:00:30.801 --> 00:00:36.832
We divide our episodes across three themes Communicate, Connect and Grow.
00:00:36.832 --> 00:00:44.281
This is a Communicate episode and we're talking about connecting with your audience with our editorial code CNECT.
00:00:44.281 --> 00:01:08.587
The Connect editing code falls into the style and phrasing phase of the editing process and it's about using words and clear language.
00:01:08.587 --> 00:01:20.251
In our documentation about this code, it says use language that will connect with your target audience, but avoid jargon that will prevent non-experts from gaining value from your writing.
00:01:20.640 --> 00:01:24.668
Hi, I'm Jam that is short for Jeffrey Alexander McGuire.
00:01:24.668 --> 00:01:35.912
I had the great good fortune to start Open Strategy Partners with my business partner in 2017, and here we are recording in 2023, and we're still talking about it.
00:01:35.912 --> 00:01:55.010
Back in the early days of the company, I was the writer and the editor and Tracy was the structure and ideas and strategy person, and when I would edit her writing, she would get upset and ask why I did something and why I made a change.
00:01:55.010 --> 00:02:12.144
Over time, we came to the realization that if we had a set of codes that explained what I was doing, that that would help her let go of her precious words and come to an improved overall result.
00:02:12.144 --> 00:02:12.967
And here we are.
00:02:12.967 --> 00:02:21.933
The Connect code is similar to many of the other codes we use, but it's got its own flavor.
00:02:21.933 --> 00:02:25.449
The Connect code is about applying empathy.
00:02:25.449 --> 00:02:28.068
Our codes talk about being clear.
00:02:28.068 --> 00:02:34.025
They talk about building trust with the audience and they talk about empathy, which also, of course, goes towards building trust.
00:02:35.039 --> 00:02:46.370
I need to make sure that an article that I'm editing is pitched in a way that's appropriate for the audience that I'm expecting to read it.
00:02:46.370 --> 00:02:53.382
If it's for developers, it should be kind of no nonsense and absolutely can be highly technical.
00:02:53.382 --> 00:02:58.030
If it's for marketers, it probably should be less technical.
00:02:58.030 --> 00:03:03.531
For example, to connect with the marketer, I need to talk about achieving a marketer's goals.
00:03:03.531 --> 00:03:10.012
The language and the way it's written should connect with the target audience.
00:03:10.012 --> 00:03:10.573
There you go.
00:03:10.573 --> 00:03:15.730
It should show them the information they need in a way that is easiest for them to consume.
00:03:16.420 --> 00:03:17.344
I'm Christine Bueller.
00:03:17.344 --> 00:03:34.132
I'm a communications consultant at OSP, where I work on creating blog posts and marketing materials for our often but not always open source and technology clients.
00:03:34.132 --> 00:03:53.653
The Connect editing code is about using language that lands well with your target audience, but also avoiding jargon that will prevent other people from getting value from your writing.
00:03:54.400 --> 00:03:59.209
I'm Chris Fenwick and I do copywriting at OSP and also editing.
00:03:59.209 --> 00:04:06.222
I mean, I think of it primarily as being about avoiding extremely dry jargon.
00:04:06.222 --> 00:04:17.644
Actually, it's about making sure that the audience that you're writing for will respond or, like that, the piece will maybe resonate with them in some capacity.
00:04:17.644 --> 00:04:33.632
So I think it's not just about it's about, in some sense, not being excessively dry and technical, but also coming up with ways that will make them see the relevance of what you're saying to them or that they will respond to more emotionally maybe.
00:04:34.334 --> 00:04:34.694
G'day.
00:04:34.694 --> 00:04:40.656
I'm Felicity Brand, I'm a communications consultant at OSP and I write and edit all day long.
00:04:40.656 --> 00:04:56.423
The CNECT code falls into our style and phrasing phase and it's about using language that will connect with your audience and avoiding jargon that will prevent non-experts from gaining value from your writing.
00:04:56.423 --> 00:05:02.298
Anne Handley has a very famous book Everybody Writes and she compares jargon to cholesterol.
00:05:02.298 --> 00:05:04.290
She said there's a good and a bad kind.
00:05:04.290 --> 00:05:18.980
So I suppose the good kind is it can signal belonging if you're using insider terms that are familiar to your audience, but mostly it's the bad kind, okay.
00:05:18.980 --> 00:05:27.721
So too often jargon will alienate or exclude a reader who isn't on the inside, and at OSP we write for everyone.
00:05:27.721 --> 00:05:32.276
So while jargon can be tempting, the risk is too high.
00:05:32.276 --> 00:05:45.338
This editing code aligns with our pillar of empathy and we have another very similar editing code about language choice, which is term Check out that episode and that's about getting the names of technology correct.
00:05:45.338 --> 00:05:50.733
But CNECT is about avoiding jargon and using language that everybody can understand.
00:05:51.596 --> 00:05:57.173
Some examples of jargon Growth, hacked, incentivize, synergize.
00:05:57.173 --> 00:05:59.199
They're sometimes called non-words.
00:05:59.199 --> 00:06:02.269
They don't convey a lot of inherent meaning.
00:06:02.269 --> 00:06:08.449
In my research for this episode, I came across the term smarketing as an example of jargon.
00:06:08.449 --> 00:06:11.519
I did not understand that term.
00:06:11.519 --> 00:06:19.923
It means sales and marketing alignment through constant communication, and apparently it was coined over 23 years ago.
00:06:19.923 --> 00:06:21.848
So apparently I'm 23 years too late.
00:06:21.848 --> 00:06:24.738
So that's a really good example.
00:06:24.738 --> 00:06:27.389
Smarketing is a really good example of word choice.
00:06:27.389 --> 00:06:34.406
That would definitely put up a wall between readers on the inside who understand the term and readers on the outside who don't.
00:06:34.406 --> 00:06:47.627
Effectively, that's excluding me from this content that I might have been able to gain a lot of value from, but this one word just was kind of like a closed door to me.
00:06:49.815 --> 00:06:51.970
Let's explore how you use this code as an editor.
00:06:53.153 --> 00:07:03.245
The connect code helps remind us to apply empathy when we're creating our communication, to think in terms of hey, what is my audience need?
00:07:03.245 --> 00:07:04.370
That's the information that goes in.
00:07:04.370 --> 00:07:08.199
How will they best receive it?
00:07:08.199 --> 00:07:19.660
That goes into my choice of words and structures and perhaps the metaphors that I want to use different for a project manager than a marketing executive, for example.
00:07:20.540 --> 00:07:33.992
Yeah, as an editor, connect or "scenic avoiding so reading jargon can mean a lot of wasted time for an editor.
00:07:33.992 --> 00:07:52.553
Editors naturally want to be efficient and it's hard to be efficient if you have to pause and look up words multiple times in a single paragraph, let alone an entire piece of writing.
00:07:52.553 --> 00:08:03.370
It can really slow you down and it's also taking your attention away from your main job, which is editing and shaping a piece of writing.
00:08:03.860 --> 00:08:08.216
I think I would probably use it just positively rather than negatively.
00:08:08.216 --> 00:08:15.793
So if I felt someone had done a good job of making some technical issue resonate, then I would point it out.
00:08:15.793 --> 00:08:32.710
I think it's a difficult one, because the reasons for which a piece of writing might not connect could also be covered by a number of other codes besides just this one that could also explain why it wasn't doing what you wanted it to.
00:08:32.710 --> 00:08:39.744
So I think I might have ended up using some other codes instead if I felt like something was wrong with the writing.
00:08:40.399 --> 00:08:47.326
As an editor, you're more able to spot jargon or language that you don't connect with because you're coming in with fresh eyes.
00:08:47.326 --> 00:08:52.149
It may be business or industry jargon, or it may be buzzwords.
00:08:52.149 --> 00:09:05.063
When I'm editing, I'll use this code to flag opportunities for choosing other phrases and I'll typically suggest any that come to mind, or I'll check with the author if that word choice was intentional.
00:09:05.063 --> 00:09:13.004
And I also use this code a lot for positive feedback so that I can celebrate word choice that the author has made.
00:09:13.004 --> 00:09:15.267
That's what makes these codes so flexible.
00:09:15.267 --> 00:09:19.711
You can use them to flag things to check for other opportunities.
00:09:19.711 --> 00:09:25.581
You can also use them to just celebrate a great word choice and reinforce good writing habits.
00:09:28.000 --> 00:09:28.522
As a writer.
00:09:28.522 --> 00:09:30.307
How do you approach this code?
00:09:30.700 --> 00:09:38.825
The most useful part of the connect code when I'm drafting is trying to catch myself not using jargon.
00:09:38.825 --> 00:09:53.072
Jargon when it goes unexplained will often exclude outgroup people or people who are not experts in a given topic yet will hinder them learning.
00:09:53.072 --> 00:09:59.472
And it's easier for us to be inclusive if we are avoiding jargon.
00:09:59.472 --> 00:10:02.129
And now we have a couple of other codes that help us with this.
00:10:02.129 --> 00:10:18.011
We have one called term, and I think there might be another one that's acronyms, I think where basically the rule is, if we have a piece of jargon that's essential to explaining what we're talking about, then we're going to have to step back and explain it.
00:10:18.011 --> 00:10:19.764
And is that a parenthetical?
00:10:19.764 --> 00:10:20.528
Is it a set of links?
00:10:20.528 --> 00:10:22.386
Is it another linking to another article?
00:10:22.386 --> 00:10:28.312
But you can't just leave jargon in place and expect that it's going to be as effective as it could be.
00:10:28.759 --> 00:10:47.350
And, as a writer, when I'm using connect, part of the very beginning of a piece is knowing your target audience, but you don't want it to be so small that it isn't welcoming to anyone else.
00:10:47.350 --> 00:10:57.125
As a writer generally, you want your work to be shared and you want it to be helpful to as many people as possible.
00:10:57.125 --> 00:11:14.900
You know, a thick and fast use of jargon is almost like reading a different language or reading an academic paper meant for only other academics, so that prohibits your work from being accessible to other people.
00:11:15.409 --> 00:11:22.043
I think the general principle is there in the background, but not necessarily a conscious awareness of the codes.
00:11:22.043 --> 00:11:31.284
I think when there's really specific things like technical terms to define and so on, then there are more obvious codes and principles that come to mind.
00:11:31.284 --> 00:11:41.585
I think it's more a case of just like how can you write an introduction that is going to be lively and get somebody's attention and show them the relevance of what you're doing?
00:11:42.090 --> 00:11:47.639
I have a guilty admission as a writer, I'm not thinking about the CNECT code.
00:11:47.639 --> 00:11:57.322
I often rely on jargon, and that's because I'm lazy, so jargon is a really useful shorthand when you want to get your ideas out.
00:11:57.322 --> 00:11:59.634
I'll often use jargon as a placeholder.
00:11:59.634 --> 00:12:15.803
When I'm writing, I'm getting my thoughts out and then once I feel like I've formulated my argument and I'll do another pass to replace jargon or replace empty cliches with more meaningful or clearer expressions.
00:12:15.803 --> 00:12:17.511
It's challenging.
00:12:17.511 --> 00:12:20.195
You can't always see it when you're deep in it.
00:12:20.195 --> 00:12:26.965
As a writer, you can't always spot your jargon, and that's where you rely on your friendly editor and their fresh eyes.
00:12:29.354 --> 00:12:31.278
For the reader to have a great experience.
00:12:31.278 --> 00:12:34.323
Here's why this editing code is extremely important.
00:12:34.690 --> 00:12:45.770
As a reader, I don't want to feel left out If you throw a whole bunch of information at me that I need because I'm trying to make an informed decision about spending my harder time and money.
00:12:45.770 --> 00:13:04.847
I want to feel like I really understand what's going on, and if you shut me out by expecting a certain amount of knowledge that's inappropriate for my level of experience or my needs from your product or service, it's going to be really, really hard for me to make the decision to try you out.
00:13:05.570 --> 00:13:06.412
For readers.
00:13:06.412 --> 00:13:17.846
Connect is important because jargon kind of locks you out, especially if you're newer to a certain subject.
00:13:17.846 --> 00:13:28.804
It might prohibit you from reading that specific piece of writing, but it also might discourage you from learning more about that topic at all.
00:13:28.804 --> 00:13:34.149
You might think, well, this topic is clearly too complex.
00:13:34.149 --> 00:13:35.793
I've changed my mind.
00:13:35.793 --> 00:13:38.138
I don't want to learn about this anymore.
00:13:38.138 --> 00:13:41.043
At OSP we definitely don't want that to happen.
00:13:41.630 --> 00:13:49.692
All the codes are ultimately aimed at the reader, actually, not just some of the style or phrasing ones, and again I think they're always.
00:13:49.692 --> 00:14:01.371
Their success is usually there for a reader when they're not visible, like the reader shouldn't be sort of alienated from the piece or reflecting on it too much, it should just be.
00:14:01.371 --> 00:14:10.129
The point of the code is to guarantee writing that is effective, not writing that necessarily makes you step back from it and wonder, like what's wrong with this?
00:14:10.711 --> 00:14:13.139
As a reader, I think the author is lazy.
00:14:13.139 --> 00:14:23.149
If I encounter a lot of jargon or non-words, I'll think maybe this article was just written for SEO purposes and doesn't contain anything meaningful for a human.
00:14:23.149 --> 00:14:25.052
So I'll quickly leave.
00:14:25.052 --> 00:14:32.745
You're losing a really great opportunity to connect with your audience if you don't choose words that everyone can understand.
00:14:49.062 --> 00:14:53.105
I hope you, dear listener, have not spotted any jargon in this episode.
00:14:53.105 --> 00:14:55.907
If so, we sincerely apologize.
00:14:55.907 --> 00:15:04.803
Next time you start creating a piece of content, sidestep the non-words and try to use real, clear language that everybody understands.
00:15:04.803 --> 00:15:14.024
Share your examples or questions with us via Twitter, at open underscore strategy, or email hello at openstrategypartnerscom.
00:15:14.024 --> 00:15:18.717
This was one of the editorial codes we use at OSP.
00:15:18.717 --> 00:15:20.782
We'll be sharing more of them as we go.
00:15:20.782 --> 00:15:35.083
If you'd like to learn more in the meantime, come over to openstrategypartnerscom, have a look at our writer enablement workshops, case study offering or get in touch to talk about your strategy or product communication needs.
00:15:35.083 --> 00:15:40.500
Thanks to everyone who contributed to this podcast, all the P's at OSP.
00:15:40.500 --> 00:15:42.562
Thanks to our clients who believe in us.
00:15:42.562 --> 00:15:51.604
Shout out to Patrick Gaumont for our high energy maple syrup flavored theme music and to Mike Snow for additional horn arrangements.
00:15:51.604 --> 00:15:57.621
Thank you for listening and subscribing about our three themes on the podcast.
00:15:57.621 --> 00:16:01.880
You'll hear from different members of the OSP team hosting episodes over time.
00:16:02.350 --> 00:16:12.347
Communicate All things communication we share how we tackle writing, editing, word choices, formats, processes and more.
00:16:12.347 --> 00:16:24.149
Connect In-depth conversations with interesting, smart people about who they are, what they do and how they approach their life and work as communicators, technologists and leaders.
00:16:24.149 --> 00:16:35.125
Grow, we cover strategic approaches to understanding and expressing the value of what you do, including tools, templates and practical applications.
00:16:35.125 --> 00:16:41.065
We also feel strongly about building a mindful, positive, human first culture at work.
00:16:41.065 --> 00:16:43.149
That's bound to pop up from time to time too.
00:16:43.149 --> 00:16:50.903
This podcast is us figuring out communication, connection and growing together.
00:16:50.903 --> 00:16:56.042
Subscribe now on YouTube, apple Podcast or the podcast channel of your choice.
00:16:56.042 --> 00:17:00.297
Follow us, suggest guests and topics, ask us questions.
00:17:00.297 --> 00:17:06.131
On social media, we are at open underscore strategy on Twitter Until next time.
00:17:06.131 --> 00:17:08.913
Thanks for listening to Communicate, Connect.
00:17:08.913 --> 00:17:11.696
Grow, the OSP podcast.
00:17:42.755 --> 00:17:46.557
Well, the knee bone is connected to the thigh bone and the thigh bone is connected to the hip bone.
