{"id":65660,"date":"2020-11-04T08:45:46","date_gmt":"2020-11-04T13:45:46","guid":{"rendered":"https:\/\/architizer.com\/blog\/?p=65660"},"modified":"2020-10-29T17:22:52","modified_gmt":"2020-10-29T21:22:52","slug":"young-architect-guide-emails","status":"publish","type":"post","link":"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/","title":{"rendered":"5 Common Mistakes Architects Make When Writing Emails"},"content":{"rendered":"
\n
\n

Mike LaValley is the architect, speaker, and writer behind\u00a0Evolving Architect<\/a>. For more creative and nerdy insights, follow him on\u00a0Instagram<\/a>\u00a0or check out his\u00a0upcoming book<\/a>.<\/i><\/p>\n

Email is a necessary evil.<\/p>\n

In a digital world, email still reigns supreme over most forms of professional communication. Yes, it\u2019s true that some correspondence is done via \u2018snail mail\u2019 or (gulp) fax. The vast majority of our documented interactions day-to-day are found in our inbox.<\/p>\n

It makes sense then that we should try to focus on how to get better at writing emails so that we can both maximize our efficiency with them and to prevent some of the unfortunate consequences of taking email for granted.<\/p>\n

Let\u2019s take some time to understand exactly what it takes to build a better email. We\u2019ll look at the purpose and format of an email and then dive into a few pitfalls you should avoid and habits you should strive for.<\/p>\n<\/div>\n<\/div>\n

\n
\n
\n<\/div>\n<\/div>\n
\n
\n

The Purpose of an Email<\/h2>\n

The purpose of an email is to professionally document something happened. You\u2019ll see it\u2019s no more or less important than any other type of correspondence as we dive deeper into what makes an email tick.<\/p>\n

When you want to document a conversation or meeting, ask a formal question to another person, or notify others out in the world of something, an email can be used as the vehicle to do just that.<\/p>\n

Inherently, an email is essentially just a faster version of a letter.<\/p>\n

Yep, that\u2019s right. Email doesn\u2019t have to be any more complicated than that.<\/p>\n

To think of it another way, an email has essentially just taken the place of physical mail because of how efficient and fast it can be. That doesn\u2019t mean it\u2019s not without its faults. Email can become convoluted and unwieldy if not considered with respect.<\/p>\n

\n<\/div>\n<\/div>\n
\n

The Format of an Email<\/span><\/h2>\n<\/div>\n
\n
\n

The advantage of an email is that it can be, at its simplest form, an abbreviated version of an actual letter.<\/p>\n

While the same logic may apply in general to an email, there are a few small changes that you\u2019ll want to consider to keep your emails streamlined.<\/p>\n

1. The Introduction<\/strong><\/p>\n

Address the email to the party or parties you want the email to go to. Make it very clear what your purpose for the email is right up front.<\/p>\n

2. The Body<\/strong><\/p>\n

Next, ask your question or state the purpose of the email in more detail. If you have an attachment connected to the email, identify what its purpose is as well.<\/p>\n

3. The Conclusion<\/strong><\/p>\n

Be polite and sign off. Repeat the \u2018call to action\u2019 you would like the person on the other end to do next. Do you want them to respond? Is it just for their reference? Let them know and sign off with a professional email signature at the bottom.<\/p>\n

\"\"

Image via Xplornet<\/a><\/em><\/p><\/div>\n

5 Email Pitfalls to Avoid<\/span><\/h2>\n<\/div>\n<\/div>\n
\n
\n

All sounds pretty easy so far, right?<\/p>\n

Well, if I know anything about email, it\u2019s that email takes practice. Here are 5 pitfalls to avoid when writing your next email.<\/p>\n<\/div>\n<\/div>\n

\n
\n

1. Making spelling and grammar mistakes<\/h2>\n

Guys, this should be without question, but you\u2019d be surprised at how many emails I see cross my desk every, single day with poor or entirely non-existent spelling and grammar.<\/p>\n

You can tell when someone hasn\u2019t written often before or when they just don\u2019t care by the format and professional feel within an email.<\/p>\n

Let\u2019s go back to what we just discussed above about an email essentially just being a digital equivalent of a physical letter. Would you just not punctuate sentences in a letter? Would you not spellcheck? Would you not try to proofread?<\/p>\n

I mean, maybe you would, but I don\u2019t think so. I believe in you.<\/p>\n

So don\u2019t get sucked into thinking that you can slack off in an email. Take the extra minute to write every email with the mentality that it\u2019s a physical piece of mail.<\/p>\n

2. Criticizing or blaming colleagues<\/h2>\n

I don\u2019t know if I\u2019ve ever really blamed someone for something in an email. As an Architect, putting the blame on someone tends to lead to more problems than solutions. Criticizing a person or group for something that may have happened isn\u2019t productive, and in an email, could be used later against that party or you depending on what the issue is.<\/p>\n

A question I\u2019ve always asked myself when writing down literally ANYTHING is, \u201cWould I be willing to let anyone read this?\u201d In particular, I think of my grandparents. Not that they would have wanted to have read any of my emails, but would they have been ashamed at what I wrote?<\/p>\n

I try to be a fairly even keeled person overall, so I don\u2019t really lean towards confrontational language when I write anyway, but keeping that in the back of my head does keep me from going to the darker side of email.<\/p>\n

It may be a cheesy lesson, but don\u2019t write something down if you wouldn\u2019t be willing to let anyone read it.<\/p>\n

3. Complaining about others<\/h2>\n

Do you have email tirades with your office peers about others in or out of the office? If you said, yes, stop it. Stop it right now. It doesn\u2019t matter if you\u2019re venting about something real or not.<\/p>\n

Complaining about others is toxic, especially when you write it. Going back to the last point, what if the person you were talking about found out about it? What if your boss did?<\/p>\n

If you have legitimate complaints about something or someone, try to confront it head on and go to the source of the problem offline. A conversation over the phone or in person can immediately release tension that doesn\u2019t need to be festering in some dark corner of you inbox.<\/p>\n

4. Over-explaining everything<\/h2>\n

Let me tell you, I used to over explain topics like nobody\u2019s business. I was a pro at it in fact. Looking back, it\u2019s something I\u2019m still working on.<\/p>\n

You know why?<\/p>\n

People lose interest in what you\u2019re talking about and communication essentially breaks down.<\/p>\n

You may have been able to write your epic, \u2018War and Peace\u2019 email to explain your encyclopedic knowledge of something, but it will end up only serving you. It won\u2019t help the people on the other end understand the purpose of the email or help them sift through your library of novels later when they need to.<\/p>\n

5. Using architecture jargon<\/h2>\n

We\u2019re Architects. As such, we speak in a bit of our own language. We\u2019ve learned from years of working in an office that there are words we\u2019ve reinterpreted and there are words we have completely just made up to explain our creative endeavors.<\/p>\n

Now, that said, we need to talk to people the way that THEY talk. Communication essentially breaks down when someone can\u2019t understand what you\u2019re saying.<\/p>\n

If you didn\u2019t know the language someone else was speaking, there would be no way for you to discuss the nuances of the issues at hand. Emails are the same. You can\u2019t write an email to someone the way you speak to your architecture friends who have been living in the world of design for years with you.<\/p>\n

The best corollary I can think of is how newspapers are written. Most newspapers are written to a fourth or fifth grade reading comprehension so that the readers understand the news presented to them.<\/p>\n

You need to treat your emails the same way. Write to your audience, not yourself.<\/p>\n

\"\"

Image via Business Insider<\/a><\/em><\/p><\/div>\n<\/div>\n<\/div>\n

\n
\n

To balance things out, here are 5 good email habits to strive for:<\/p>\n

1. Stick to one topic.<\/h2>\n

I struggle with this, but it\u2019s important. If at all possible, only write one email for one topic or idea.<\/p>\n

The reason for this is twofold – to keep the conversation about one subject and to keep the conversation searchable for future reference.<\/p>\n

For me, it can sometimes feel a bit overkill to send an owner three different emails about different topics, especially if they\u2019re being sent in quick succession. In those cases, I\u2019ll at the very least try to keep the email as brief as possible with a clear delineation for each topic.<\/p>\n

It\u2019s not perfect, but I do strive for each email I send to be its own topic because it allows me to quickly search for that email again later if I need to. When there are multiple topics, it becomes very difficult to sift through thousands of emails for one email at one moment in time.<\/p>\n

2. Craft a strong, catalogued subject line.<\/h2>\n

I\u2019ve adapted a technique implemented by a few of the firms I\u2019ve worked at to include a project number, project name, and topic all within the subject. This allows me to scan through emails easily to find what I\u2019m looking for.<\/p>\n

When you\u2019re working on multiple projects for the same owner, it becomes even more critical to develop this practice so that you\u2019re not sending the same person emails about two entirely different projects, ultimately confusing the issue and likely the person on the other end.<\/p>\n

Whatever your system, try to consistently use the same subject format when you send emails. If you get weird or broken subjects from others that don\u2019t fit your own (as you inevitably will), feel free to re-write them as necessary when you respond. It will help you catalogue the topic later and ultimately help the conversation.<\/p>\n

Sometimes people are writing emails entirely from their phones or they\u2019re in a hurry, or they may just not care.<\/p>\n

But you can care. You can help catalogue the conversation for everyone.<\/p>\n

3. Make your email scannable.<\/h2>\n

If you have to send a more complicated email, which can often be the case when there are issues requiring many different stakeholders, try to make the emails scannable.<\/p>\n

Many people on the other end of your emails may not be able to follow, or even need to follow, your emails if they are written as an ocean of bloated paragraphs.<\/p>\n

Instead, when I do have to send larger, complicated emails, I\u2019ll include subjects that I underline and\/or bolden in order to emphasize the different types of points or topics I\u2019m trying to cover.<\/p>\n

Someone who is just trying to scan the email can then do so fairly easily and just respond as necessary.<\/p>\n

4. Be concise.<\/h2>\n

We\u2019ve discussed this a few times already, but I can\u2019t stress enough how being brief in an email can be a benefit to all who read your correspondence.<\/p>\n

A concise email can efficiently get your point across and help the person on the other end understand what you\u2019re trying to get at quickly.<\/p>\n

The last thing you want to do is confuse the person you\u2019re sending the email to, or even worse, make their eyes glaze over as they begin to resent your epic work of non-fiction.<\/p>\n

It takes time, but saying less is a craft that, once learned, can mean all the difference.<\/p>\n

5. Include a clear call to action.<\/h2>\n

When it comes to the point of an email, you should try to be as clear as possible with what you want the recipient to do next.<\/p>\n

Is the email you\u2019re sending for their reference or do they need to perform some type of action (ie. answer a question or physical take action)?<\/p>\n

Try to place your call to action at the top of your email if possible so that a person scanning will see it right away. Then, explain what you\u2019re talking about and reiterate it again so that the intent of what you are asking for is clear.<\/p>\n<\/div>\n<\/div>\n

\n
\n
\n<\/div>\n<\/div>\n
\n
\n

Final Thoughts<\/h2>\n

Email is a necessary evil as a professional working in the 21st century. There may be another form of communication society uses in the next fifty or one-hundred years, but email is here to stay for the time being.<\/p>\n

If there\u2019s one lesson I\u2019ve learned from my time writing emails as an Architect, it\u2019s that email, like any other document in your toolbox, can be used later in a court of law to settle disputes or resolve issues. I\u2019ve heard of situations where email played a pivotal role in documenting not only a one-off incident, but a pattern of either unprofessional behavior or neglectful action.<\/p>\n

When I write emails, I do so with purpose. I do so trying to write them as though they could be read by anyone, used by anyone, and protect myself and the firm I work for if it ever came to that.<\/p>\n

Keep a defensive mindset when you write your next email. Strive not for perfection in writing, but better writing that could help you avoid professional pitfalls later.<\/p>\n

It may sound silly, but treat your emails with care. It does make a difference.<\/p>\n

This post originally appeared on Mike LaValley’s Evolving Architect<\/a> blog. Architects: Showcase your next project through\u00a0Architizer<\/a>\u00a0and sign up for our\u00a0inspirational newsletter<\/a>.<\/em><\/p>\n

Top image via Driven Media<\/a><\/em><\/p>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

Here are some common pitfalls to avoid when writing your next email \u2014 and some good habits to pick up, too.<\/p>\n","protected":false},"author":92,"featured_media":65663,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"architizer_featured_type":"insert","architizer_featured_image":"","_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[2,6],"tags":[],"architizer_project":[],"architizer_brand":[],"architizer_firm":[],"architizer_product":[],"class_list":["post-65660","post","type-post","status-publish","format-standard","hentry","category-practice","category-tools"],"acf":[],"yoast_head":"\n5 Common Mistakes Architects Make When Writing Emails - Architizer Journal<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"5 Common Mistakes Architects Make When Writing Emails - Architizer Journal\" \/>\n<meta property=\"og:description\" content=\"Here are some common pitfalls to avoid when writing your next email \u2014 and some good habits to pick up, too.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/\" \/>\n<meta property=\"og:site_name\" content=\"Journal\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/Architizer\/\" \/>\n<meta property=\"article:published_time\" content=\"2020-11-04T13:45:46+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2020-10-29T21:22:52+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.architizer.com\/wp-content\/uploads\/9808f9dd8bcaa1e4e417540824c96cb6-1.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"2338\" \/>\n\t<meta property=\"og:image:height\" content=\"1227\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Michael LaValley\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/blog.architizer.com\/wp-content\/uploads\/9808f9dd8bcaa1e4e417540824c96cb6-1.jpg\" \/>\n<meta name=\"twitter:creator\" content=\"@Architizer\" \/>\n<meta name=\"twitter:site\" content=\"@Architizer\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Michael LaValley\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"11 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/\"},\"author\":{\"name\":\"Michael LaValley\",\"@id\":\"https:\/\/architizer.com\/blog\/#\/schema\/person\/3184ef2abc3a70de1222172268217e79\"},\"headline\":\"5 Common Mistakes Architects Make When Writing Emails\",\"datePublished\":\"2020-11-04T13:45:46+00:00\",\"dateModified\":\"2020-10-29T21:22:52+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/\"},\"wordCount\":2220,\"publisher\":{\"@id\":\"https:\/\/architizer.com\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/blog.architizer.com\/wp-content\/uploads\/9808f9dd8bcaa1e4e417540824c96cb6.jpg\",\"articleSection\":[\"Practice\",\"Tools\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/\",\"url\":\"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/\",\"name\":\"5 Common Mistakes Architects Make When Writing Emails - Architizer Journal\",\"isPartOf\":{\"@id\":\"https:\/\/architizer.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/blog.architizer.com\/wp-content\/uploads\/9808f9dd8bcaa1e4e417540824c96cb6.jpg\",\"datePublished\":\"2020-11-04T13:45:46+00:00\",\"dateModified\":\"2020-10-29T21:22:52+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/#primaryimage\",\"url\":\"https:\/\/blog.architizer.com\/wp-content\/uploads\/9808f9dd8bcaa1e4e417540824c96cb6.jpg\",\"contentUrl\":\"https:\/\/blog.architizer.com\/wp-content\/uploads\/9808f9dd8bcaa1e4e417540824c96cb6.jpg\",\"width\":2500,\"height\":1227},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/architizer.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"5 Common Mistakes Architects Make When Writing Emails\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/architizer.com\/blog\/#website\",\"url\":\"https:\/\/architizer.com\/blog\/\",\"name\":\"Journal\",\"description\":\"Inspiration and Tools for Architects\",\"publisher\":{\"@id\":\"https:\/\/architizer.com\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/architizer.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/architizer.com\/blog\/#organization\",\"name\":\"Architizer\",\"url\":\"https:\/\/architizer.com\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/architizer.com\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/blog.architizer.com\/wp-content\/uploads\/favicon.df2618023937.png\",\"contentUrl\":\"https:\/\/blog.architizer.com\/wp-content\/uploads\/favicon.df2618023937.png\",\"width\":36,\"height\":36,\"caption\":\"Architizer\"},\"image\":{\"@id\":\"https:\/\/architizer.com\/blog\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/Architizer\/\",\"https:\/\/x.com\/Architizer\",\"https:\/\/www.instagram.com\/architizer\/\",\"https:\/\/www.linkedin.com\/company\/architizer\/\",\"https:\/\/www.pinterest.com\/architizer\/\",\"https:\/\/www.youtube.com\/user\/Architizer\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/architizer.com\/blog\/#\/schema\/person\/3184ef2abc3a70de1222172268217e79\",\"name\":\"Michael LaValley\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/architizer.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/580c60a1b0c4c3ffc3282ce0fb7369eb32222c3b1257e3f77e407d2897b6d4c6?s=96&d=https%3A%2F%2Fblog.architizer.com%2Fwp-content%2Fuploads%2Flogo-600x600-1.jpg&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/580c60a1b0c4c3ffc3282ce0fb7369eb32222c3b1257e3f77e407d2897b6d4c6?s=96&d=https%3A%2F%2Fblog.architizer.com%2Fwp-content%2Fuploads%2Flogo-600x600-1.jpg&r=g\",\"caption\":\"Michael LaValley\"},\"url\":\"https:\/\/architizer.com\/blog\/author\/michael-lavalley\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"5 Common Mistakes Architects Make When Writing Emails - Architizer Journal","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/","og_locale":"en_US","og_type":"article","og_title":"5 Common Mistakes Architects Make When Writing Emails - Architizer Journal","og_description":"Here are some common pitfalls to avoid when writing your next email \u2014 and some good habits to pick up, too.","og_url":"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/","og_site_name":"Journal","article_publisher":"https:\/\/www.facebook.com\/Architizer\/","article_published_time":"2020-11-04T13:45:46+00:00","article_modified_time":"2020-10-29T21:22:52+00:00","og_image":[{"width":2338,"height":1227,"url":"https:\/\/blog.architizer.com\/wp-content\/uploads\/9808f9dd8bcaa1e4e417540824c96cb6-1.jpg","type":"image\/jpeg"}],"author":"Michael LaValley","twitter_card":"summary_large_image","twitter_image":"https:\/\/blog.architizer.com\/wp-content\/uploads\/9808f9dd8bcaa1e4e417540824c96cb6-1.jpg","twitter_creator":"@Architizer","twitter_site":"@Architizer","twitter_misc":{"Written by":"Michael LaValley","Est. reading time":"11 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/#article","isPartOf":{"@id":"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/"},"author":{"name":"Michael LaValley","@id":"https:\/\/architizer.com\/blog\/#\/schema\/person\/3184ef2abc3a70de1222172268217e79"},"headline":"5 Common Mistakes Architects Make When Writing Emails","datePublished":"2020-11-04T13:45:46+00:00","dateModified":"2020-10-29T21:22:52+00:00","mainEntityOfPage":{"@id":"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/"},"wordCount":2220,"publisher":{"@id":"https:\/\/architizer.com\/blog\/#organization"},"image":{"@id":"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/#primaryimage"},"thumbnailUrl":"https:\/\/blog.architizer.com\/wp-content\/uploads\/9808f9dd8bcaa1e4e417540824c96cb6.jpg","articleSection":["Practice","Tools"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/","url":"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/","name":"5 Common Mistakes Architects Make When Writing Emails - Architizer Journal","isPartOf":{"@id":"https:\/\/architizer.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/#primaryimage"},"image":{"@id":"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/#primaryimage"},"thumbnailUrl":"https:\/\/blog.architizer.com\/wp-content\/uploads\/9808f9dd8bcaa1e4e417540824c96cb6.jpg","datePublished":"2020-11-04T13:45:46+00:00","dateModified":"2020-10-29T21:22:52+00:00","breadcrumb":{"@id":"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/#primaryimage","url":"https:\/\/blog.architizer.com\/wp-content\/uploads\/9808f9dd8bcaa1e4e417540824c96cb6.jpg","contentUrl":"https:\/\/blog.architizer.com\/wp-content\/uploads\/9808f9dd8bcaa1e4e417540824c96cb6.jpg","width":2500,"height":1227},{"@type":"BreadcrumbList","@id":"https:\/\/architizer.com\/blog\/practice\/tools\/young-architect-guide-emails\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/architizer.com\/blog\/"},{"@type":"ListItem","position":2,"name":"5 Common Mistakes Architects Make When Writing Emails"}]},{"@type":"WebSite","@id":"https:\/\/architizer.com\/blog\/#website","url":"https:\/\/architizer.com\/blog\/","name":"Journal","description":"Inspiration and Tools for Architects","publisher":{"@id":"https:\/\/architizer.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/architizer.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/architizer.com\/blog\/#organization","name":"Architizer","url":"https:\/\/architizer.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/architizer.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/blog.architizer.com\/wp-content\/uploads\/favicon.df2618023937.png","contentUrl":"https:\/\/blog.architizer.com\/wp-content\/uploads\/favicon.df2618023937.png","width":36,"height":36,"caption":"Architizer"},"image":{"@id":"https:\/\/architizer.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/Architizer\/","https:\/\/x.com\/Architizer","https:\/\/www.instagram.com\/architizer\/","https:\/\/www.linkedin.com\/company\/architizer\/","https:\/\/www.pinterest.com\/architizer\/","https:\/\/www.youtube.com\/user\/Architizer"]},{"@type":"Person","@id":"https:\/\/architizer.com\/blog\/#\/schema\/person\/3184ef2abc3a70de1222172268217e79","name":"Michael LaValley","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/architizer.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/580c60a1b0c4c3ffc3282ce0fb7369eb32222c3b1257e3f77e407d2897b6d4c6?s=96&d=https%3A%2F%2Fblog.architizer.com%2Fwp-content%2Fuploads%2Flogo-600x600-1.jpg&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/580c60a1b0c4c3ffc3282ce0fb7369eb32222c3b1257e3f77e407d2897b6d4c6?s=96&d=https%3A%2F%2Fblog.architizer.com%2Fwp-content%2Fuploads%2Flogo-600x600-1.jpg&r=g","caption":"Michael LaValley"},"url":"https:\/\/architizer.com\/blog\/author\/michael-lavalley\/"}]}},"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"https:\/\/blog.architizer.com\/wp-content\/uploads\/9808f9dd8bcaa1e4e417540824c96cb6.jpg","amp_enabled":true,"_links":{"self":[{"href":"https:\/\/architizer.com\/blog\/wp-json\/wp\/v2\/posts\/65660","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/architizer.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/architizer.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/architizer.com\/blog\/wp-json\/wp\/v2\/users\/92"}],"replies":[{"embeddable":true,"href":"https:\/\/architizer.com\/blog\/wp-json\/wp\/v2\/comments?post=65660"}],"version-history":[{"count":0,"href":"https:\/\/architizer.com\/blog\/wp-json\/wp\/v2\/posts\/65660\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/architizer.com\/blog\/wp-json\/wp\/v2\/media\/65663"}],"wp:attachment":[{"href":"https:\/\/architizer.com\/blog\/wp-json\/wp\/v2\/media?parent=65660"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/architizer.com\/blog\/wp-json\/wp\/v2\/categories?post=65660"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/architizer.com\/blog\/wp-json\/wp\/v2\/tags?post=65660"},{"taxonomy":"architizer_project","embeddable":true,"href":"https:\/\/architizer.com\/blog\/wp-json\/wp\/v2\/architizer_project?post=65660"},{"taxonomy":"architizer_brand","embeddable":true,"href":"https:\/\/architizer.com\/blog\/wp-json\/wp\/v2\/architizer_brand?post=65660"},{"taxonomy":"architizer_firm","embeddable":true,"href":"https:\/\/architizer.com\/blog\/wp-json\/wp\/v2\/architizer_firm?post=65660"},{"taxonomy":"architizer_product","embeddable":true,"href":"https:\/\/architizer.com\/blog\/wp-json\/wp\/v2\/architizer_product?post=65660"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}