Let me ask you something. How confident would you be buying a meal from a food truck that is so rusted and smoke-stained that you can’t make out its name on the side? Or how confident would you be staying at a motel where the paint was peeling off the doors, siding was missing on the building, and duct tape held the cracked windows together? Or how confident would you be buying a car from an auto dealer whose windows were so dirty you couldn’t see through them and whose sign was missing a couple of letters? I bet your confidence wouldn’t be very high in those situations. How do you think a client would feel if they came across a website that contains errors while looking for a designer? I bet they wouldn’t feel too confident in hiring that person. That’s what I want to talk about today, making sure your messaging doesn’t contain errors. Let me give you a bit of background here. I decided to talk about this today because someone sent me a message earlier this week. Now, if you’ve ever contacted me for whatever reason, there’s a good chance I looked at your website. It’s just something I do. Any time someone emails me or contacts me on social media, I’ll try to find their website to see how they present themself. So, someone sent me a message earlier this week, and when I found their website, the first thing I saw was a spelling mistake. The very first line of the website was “I Designs Websites.” Other places on the website included passages that lead me to believe this person is not a native English speaker. But I’ll touch more on that later. And even though it was a beautifully designed website, and this person had a fantastic portfolio, those spelling and grammar mistakes made me question the quality of this person’s work. Now imagine I was a client looking for someone to build a website for my new business. Those errors may be enough to make me second guess this person and move on to another web designer. Be careful with jargon. But it’s not just spelling or grammatical errors that can hinder your chance of landing clients. Another section of this same website described their services and how they work. They mention that the first thing they do is build a wireframe to show the client before making their website using WordPress. Elsewhere on the site, it said their web hosting includes a CDN. You probably understand what I just said if you're familiar with websites. Imagine a client with no knowledge of websites other than knowing their business needs one. “Wireframe,” “WordPress,” and “CDN” don’t mean anything to them. Reading these things may cause them more confusion, which may make them look elsewhere for a web designer. I talked about Jargon in episode 217 of the podcast. Jargon is common terminology in specific industries but maybe not so common outside of them. I’m a web designer, and I remember wondering what wireframes were the first time I heard someone use that term. It wasn’t until I understood what a wireframe was that the word became part of my vocabulary. I’m not saying you shouldn’t use these jargon terms in your communication. But if you do, you should add some clarity for anyone unfamiliar with them. For example: “We start by building a wireframe, a mockup layout of your website for you to approve before we start building the real thing in WordPress, a popular website platform, powering over 60% of the world’s websites.” “Our web hosting includes a CDN, a content delivery network that improves the efficiency and speed of your website and helps you rank higher in search engines.” Even if a client doesn’t recognize the jargon, they can still understand what you’re saying because of the descriptions. A designer's job is communication. As designers, people think our job is to make things look good. And in part, it is. But more importantly, a designer’s job is to ensure a message is told clearly and understandably. Design is about communication. And if the communicated message is confusing, then the person, comp