Architekwiki
  • Home
  • WIKI
  • Start Here
  • Resources
  • Subscribe
  • Other
    • Reading List
    • Ochre >
      • Ochre
      • Ochre KB
      • Ochre FAQs
      • Ochre Help
    • Details
    • The 3 Aspects
    • About
    • Terms of Use
  • Home
  • WIKI
  • Start Here
  • Resources
  • Subscribe
  • Other
    • Reading List
    • Ochre >
      • Ochre
      • Ochre KB
      • Ochre FAQs
      • Ochre Help
    • Details
    • The 3 Aspects
    • About
    • Terms of Use

Architekwiki

A Resource For Architects
Click here to get good stuff in your inbox

Let's Pick On Jargon

1/13/2014

 
JargonImage credit: David Grossman
Every profession has terms that are specific to it. Jargon. Jargon within the profession can have a clarifying effect and can often be a shorthand for more wordy concepts. So jargon has a worthwhile effect WITHIN the profession where everyone understands what is meant. 

A profession’s jargon when used with the public or with clients has the opposite effect - obfuscation, confusion. It doesn't matter whether you intend to make it difficult to be understood, or if it is unintentional. The result is the same. You have chosen (intentionally or not) to rely on the authority of your role as a specialist instead of making yourself clear. I think that this comes across as arrogance. I think it is another way of saying, "Just trust me." Trust is earned, jargon gets in the way of trust.

Everyone has experience with obfuscation. You are in the minority if you don't find it at least annoying. 
Why would you choose to NOT be understood? I can think of one or two scenarios, but they are outweighed by many more that are not very attractive. 

What if you think in jargon? Well, that clears up your motives for using it, but you are still left with poor communication and lack of understanding.

Whenever you need agreement, jargon works against you. Even if you get the agreement, the client has an escape hatch - "I didn't know that's what we agreed to" or "I don't remember discussing that".

You can tell that I am not a fan of jargon. I don't think it is just me. If it sounds better when you use jargon, I think it is because the jargon conceals the weakness of the idea(s). Do we want weak ideas? I don't.

But let's go back to the trust issue. I have heard it said that there are two things you must demonstrate to win a design job - technical competence and trustworthiness that you will deliver on your promises. For many clients judging technical competence depends on past experience. Have you done this before or not? But all clients can judge trustworthiness. They do it all the time. So I think jargon lets you down in the exact scenario where you are really depending on it to make you look like a good choice. 

Lack of understanding (jargon) and trustworthiness travel in different circles.


Comments are closed.
    Resources

    Start Here

    YouTube Channel

    Picture

    Picture

    Terms of Use
    Your use of Architekwiki is implicit agreement with the 
    ​
    Terms of Use.
    x
    Get Good Stuff in Your Inbox
    Picture
    Subscribe

    Archives

    September 2023
    July 2023
    April 2023
    March 2023
    February 2023
    January 2023
    November 2022
    October 2022
    July 2022
    June 2022
    April 2022
    October 2021
    September 2021
    August 2021
    June 2021
    May 2021
    February 2021
    January 2021
    December 2020
    November 2020
    October 2020
    September 2020
    August 2020
    July 2020
    June 2020
    April 2020
    March 2020
    February 2020
    January 2020
    December 2019
    November 2019
    October 2019
    September 2019
    August 2019
    July 2019
    June 2019
    May 2019
    April 2019
    March 2019
    February 2019
    January 2019
    December 2018
    November 2018
    October 2018
    September 2018
    August 2018
    July 2018
    June 2018
    May 2018
    April 2018
    March 2018
    February 2018
    January 2018
    December 2017
    November 2017
    October 2017
    September 2017
    August 2017
    July 2017
    June 2017
    May 2017
    April 2017
    March 2017
    February 2017
    January 2017
    December 2016
    November 2016
    October 2016
    September 2016
    August 2016
    July 2016
    June 2016
    May 2016
    April 2016
    March 2016
    February 2016
    January 2016
    December 2015
    November 2015
    October 2015
    September 2015
    August 2015
    July 2015
    June 2015
    May 2015
    April 2015
    March 2015
    February 2015
    January 2015
    December 2014
    November 2014
    October 2014
    September 2014
    August 2014
    July 2014
    June 2014
    May 2014
    April 2014
    March 2014
    February 2014
    January 2014
    December 2013
    November 2013
    October 2013
    September 2013
    August 2013
    July 2013
    June 2013
    May 2013
    April 2013
    March 2013
    February 2013
    January 2013
    December 2012
    November 2012
    October 2012

    Categories

    All
    Business Development
    Business Management
    Design
    Detail
    Miscellaneous
    Project Management
    Resources

Picture

Picture
VISIT ARCHITEKWIKI'S RESOURCES
​
START HERE
ABOUT
SIGN UP
TERMS OF USE
Architekwiki | Architect's Resource | Greater Cincinnati 
© 2012-2022   Architekwiki​