<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="/assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Field Notes (Posts about communication)</title><link>https://janetriley.net/</link><description></description><atom:link href="https://janetriley.net/tags/communication.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2024 &lt;a href="mailto:hello@janetriley.net"&gt;Janet Riley&lt;/a&gt; </copyright><lastBuildDate>Tue, 21 May 2024 18:15:28 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Dan Slimmon: An Incident Command Training Handbook</title><link>https://janetriley.net/notes/leadership/dan-slimmon-an-incident-command-training-handbook.html</link><dc:creator>Janet Riley</dc:creator><description>&lt;p&gt;Dan Slimmon: &lt;a href="https://blog.danslimmon.com/2019/06/24/an-incident-command-training-handbook/"&gt;An Incident Command Training Handbook&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;Summary&lt;/h2&gt;
&lt;p&gt;How to structure and lead an incident response. The five questions of a status update. How to manage information flow effectively.&lt;/p&gt;
&lt;p&gt;Slimmon's writing style is direct and simple. It's a mid-length article with some detail, but you could follow it
in a high-stress situation (like mid-incident) and benefit immediately. &lt;/p&gt;
&lt;p&gt;Best case scenario is to have the whole team read it ahead of time to understand the structure. 
When it's showtime everyone can slide into their roles and know their responsibilities. &lt;/p&gt;
&lt;h2&gt;Excerpts&lt;/h2&gt;
&lt;pre class="code literal-block"&gt;&lt;span class="nv"&gt;An&lt;/span&gt; &lt;span class="nv"&gt;Incident&lt;/span&gt; &lt;span class="nv"&gt;Commander&lt;/span&gt;’&lt;span class="nv"&gt;s&lt;/span&gt; &lt;span class="nv"&gt;job&lt;/span&gt; &lt;span class="nv"&gt;is&lt;/span&gt; &lt;span class="nv"&gt;to&lt;/span&gt; &lt;span class="nv"&gt;keep&lt;/span&gt; &lt;span class="nv"&gt;the&lt;/span&gt; &lt;span class="nv"&gt;incident&lt;/span&gt; &lt;span class="nv"&gt;moving&lt;/span&gt; &lt;span class="nv"&gt;toward&lt;/span&gt; &lt;span class="nv"&gt;resolution&lt;/span&gt;. 
&lt;span class="nv"&gt;But&lt;/span&gt; &lt;span class="nv"&gt;an&lt;/span&gt; &lt;span class="nv"&gt;Incident&lt;/span&gt; &lt;span class="nv"&gt;Commander&lt;/span&gt;’&lt;span class="nv"&gt;s&lt;/span&gt; &lt;span class="nv"&gt;job&lt;/span&gt; &lt;span class="nv"&gt;is&lt;/span&gt; &lt;span class="nv"&gt;not&lt;/span&gt; &lt;span class="nv"&gt;to&lt;/span&gt; &lt;span class="nv"&gt;fix&lt;/span&gt; &lt;span class="nv"&gt;the&lt;/span&gt; &lt;span class="nv"&gt;problem&lt;/span&gt;.

&lt;span class="nv"&gt;As&lt;/span&gt; &lt;span class="nv"&gt;Incident&lt;/span&gt; &lt;span class="nv"&gt;Commander&lt;/span&gt;, &lt;span class="nv"&gt;you&lt;/span&gt; &lt;span class="nv"&gt;shouldn&lt;/span&gt;’&lt;span class="nv"&gt;t&lt;/span&gt; &lt;span class="nv"&gt;touch&lt;/span&gt; &lt;span class="nv"&gt;a&lt;/span&gt; &lt;span class="nv"&gt;terminal&lt;/span&gt; &lt;span class="nv"&gt;or&lt;/span&gt; &lt;span class="nv"&gt;search&lt;/span&gt; &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="nv"&gt;a&lt;/span&gt; &lt;span class="nv"&gt;graph&lt;/span&gt; 
&lt;span class="nv"&gt;or&lt;/span&gt; &lt;span class="nv"&gt;kick&lt;/span&gt; &lt;span class="nv"&gt;off&lt;/span&gt; &lt;span class="nv"&gt;a&lt;/span&gt; &lt;span class="nv"&gt;deploy&lt;/span&gt; &lt;span class="nv"&gt;unless&lt;/span&gt; &lt;span class="nv"&gt;you&lt;/span&gt;’&lt;span class="nv"&gt;re&lt;/span&gt; &lt;span class="nv"&gt;absolutely&lt;/span&gt; &lt;span class="nv"&gt;the&lt;/span&gt; &lt;span class="nv"&gt;only&lt;/span&gt; &lt;span class="nv"&gt;person&lt;/span&gt; &lt;span class="nv"&gt;available&lt;/span&gt; &lt;span class="nv"&gt;to&lt;/span&gt; &lt;span class="k"&gt;do&lt;/span&gt; &lt;span class="nv"&gt;it&lt;/span&gt;. 
&lt;span class="nv"&gt;This&lt;/span&gt; &lt;span class="nv"&gt;may&lt;/span&gt; &lt;span class="nv"&gt;feel&lt;/span&gt; &lt;span class="nv"&gt;uncomfortable&lt;/span&gt;, &lt;span class="nv"&gt;especially&lt;/span&gt; &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="nv"&gt;your&lt;/span&gt; &lt;span class="nv"&gt;background&lt;/span&gt; &lt;span class="nv"&gt;is&lt;/span&gt; &lt;span class="nv"&gt;in&lt;/span&gt; &lt;span class="nv"&gt;engineering&lt;/span&gt;. 
&lt;span class="nv"&gt;It&lt;/span&gt; &lt;span class="nv"&gt;will&lt;/span&gt; &lt;span class="nv"&gt;probably&lt;/span&gt; &lt;span class="nv"&gt;feel&lt;/span&gt; &lt;span class="nv"&gt;like&lt;/span&gt; &lt;span class="nv"&gt;you&lt;/span&gt;’&lt;span class="nv"&gt;re&lt;/span&gt; &lt;span class="nv"&gt;not&lt;/span&gt; &lt;span class="nv"&gt;doing&lt;/span&gt; &lt;span class="nv"&gt;enough&lt;/span&gt; &lt;span class="nv"&gt;to&lt;/span&gt; &lt;span class="nv"&gt;help&lt;/span&gt;. 
&lt;span class="nv"&gt;What&lt;/span&gt; &lt;span class="nv"&gt;you&lt;/span&gt; &lt;span class="nv"&gt;need&lt;/span&gt; &lt;span class="nv"&gt;to&lt;/span&gt; &lt;span class="nv"&gt;remember&lt;/span&gt; &lt;span class="nv"&gt;is&lt;/span&gt; &lt;span class="nv"&gt;this&lt;/span&gt;: &lt;span class="nv"&gt;whatever&lt;/span&gt; &lt;span class="nv"&gt;your&lt;/span&gt; &lt;span class="nv"&gt;usual&lt;/span&gt; &lt;span class="nv"&gt;job&lt;/span&gt;, &lt;span class="nv"&gt;when&lt;/span&gt; &lt;span class="nv"&gt;you&lt;/span&gt;’&lt;span class="nv"&gt;re&lt;/span&gt; &lt;span class="nv"&gt;the&lt;/span&gt; &lt;span class="nv"&gt;Incident&lt;/span&gt; &lt;span class="nv"&gt;Commander&lt;/span&gt;, &lt;span class="nv"&gt;your&lt;/span&gt; &lt;span class="nv"&gt;job&lt;/span&gt; &lt;span class="nv"&gt;is&lt;/span&gt; &lt;span class="nv"&gt;to&lt;/span&gt; &lt;span class="nv"&gt;be&lt;/span&gt; &lt;span class="nv"&gt;the&lt;/span&gt; &lt;span class="nv"&gt;Incident&lt;/span&gt; &lt;span class="nv"&gt;Commander&lt;/span&gt;.
&lt;/pre&gt;
&lt;p&gt;&lt;code&gt;Managing information flow is the single most important responsibility of the Incident Commander.&lt;/code&gt;&lt;/p&gt;
&lt;h2&gt;Takeaways&lt;/h2&gt;
&lt;p&gt;Sometimes the most effective thing you can do is coordinate the experts. &lt;/p&gt;</description><category>communication</category><category>leadership</category><guid>https://janetriley.net/notes/leadership/dan-slimmon-an-incident-command-training-handbook.html</guid><pubDate>Thu, 26 May 2022 18:30:55 GMT</pubDate></item><item><title>Docs for Developers: An Engineers Field Guide to Technical Writing</title><link>https://janetriley.net/notes/technical_communication/book_docs_for_developers.html</link><dc:creator>Janet Riley</dc:creator><description>&lt;p&gt;&lt;a href="https://docsfordevelopers.com/"&gt;Docs for Developers: An Engineer's Field Guide to Technical Writing&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://link.springer.com/book/10.1007/978-1-4842-7217-6"&gt;Publisher's Page&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Author: Jared Bhatti, David Nunez, Jen Lambourne, Zachary Sarah Corleissen, Heidi Waterhouse&lt;/p&gt;
&lt;h3&gt;Summary&lt;/h3&gt;
&lt;p&gt;How to write maintainable docs that help your customers use your software.&lt;/p&gt;
&lt;h3&gt;Excerpt&lt;/h3&gt;
&lt;p&gt;&lt;quote&gt;"Docs for Developers demystifies the process of creating great developer documentation, following a team of software developers as they work to launch a new product. At each step along the way, you learn through examples, templates, and principles how to create, measure, and maintain documentation, which you can adapt to the needs of your own organization."&lt;/quote&gt;&lt;/p&gt;
&lt;h3&gt;Takeaways&lt;/h3&gt;
&lt;p&gt;This struck me as the devops of documentation - turn these high level ideas into something we can live in. On my To Read pile. &lt;/p&gt;</description><category>books</category><category>communication</category><category>technical communication</category><category>technical writing</category><guid>https://janetriley.net/notes/technical_communication/book_docs_for_developers.html</guid><pubDate>Wed, 25 May 2022 17:00:00 GMT</pubDate></item><item><title>Gitlab: Technical Writing Fundamentals</title><link>https://janetriley.net/notes/technical_communication/gitlab__tech_writing_fundamentals.html</link><dc:creator>Janet Riley</dc:creator><description>&lt;p&gt;&lt;a href="https://about.gitlab.com/handbook/engineering/ux/technical-writing/fundamentals/"&gt;GitLab's Technical Writing Fundamentals course&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;Summary&lt;/h3&gt;
&lt;p&gt;Written to help contributors write and edit GitLab documentation. The first three parts are grammar and style guidance.
Session 4 covers how to approach four topic types: concepts, tasks, references, and troubleshooting. &lt;/p&gt;
&lt;p&gt;The page links to the recorded versions on YouTube.&lt;/p&gt;</description><category>communication</category><category>tech writing</category><category>technical communication</category><guid>https://janetriley.net/notes/technical_communication/gitlab__tech_writing_fundamentals.html</guid><pubDate>Wed, 25 May 2022 17:00:00 GMT</pubDate></item><item><title>Google: Tech Writing Resources for Developers</title><link>https://janetriley.net/notes/technical_communication/google__tech_writing_resources_for_developers.html</link><dc:creator>Janet Riley</dc:creator><description>&lt;p&gt;&lt;a href="https://developers.google.com/tech-writing"&gt;Google's Tech Writing Resources for Developers&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;Summary&lt;/h3&gt;
&lt;p&gt;Google's Technical writing courses and resources for engineers and engineer-adjacent folks. &lt;/p&gt;
&lt;h3&gt;Excerpt&lt;/h3&gt;
&lt;p&gt;"This collection of courses and learning resources aims to improve your technical documentation. Learn how to plan and author technical documents."&lt;/p&gt;</description><category>communication</category><category>tech writing</category><category>technical communication</category><guid>https://janetriley.net/notes/technical_communication/google__tech_writing_resources_for_developers.html</guid><pubDate>Wed, 25 May 2022 17:00:00 GMT</pubDate></item><item><title>Josh Branchaud: 6 Tips for Better Communication with a Client</title><link>https://janetriley.net/notes/communication/josh_branchaud__better_client_communication.html</link><dc:creator>Janet Riley</dc:creator><description>&lt;p&gt;&lt;a href="https://hashrocket.com/blog/posts/6-tips-for-better-communication-with-a-client"&gt;6 Tips for Better Communication with a Client&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Author: Josh Branchaud&lt;/p&gt;
&lt;h3&gt;Summary&lt;/h3&gt;
&lt;p&gt;Notes from a consulting company on more effective communication with clients. &lt;/p&gt;
&lt;h3&gt;Takeaways&lt;/h3&gt;
&lt;p&gt;Screenshots and moving gifs are great tools for asynchronous communication. &lt;/p&gt;</description><category>communication</category><category>consulting</category><guid>https://janetriley.net/notes/communication/josh_branchaud__better_client_communication.html</guid><pubDate>Wed, 25 May 2022 17:00:00 GMT</pubDate></item><item><title>Matthew Bischoff: Stacking the Deck</title><link>https://janetriley.net/notes/communication/matthew_bischoff__stack_the_deck.html</link><dc:creator>Janet Riley</dc:creator><description>&lt;p&gt;&lt;a href="https://matthewbischoff.com/stacking-the-deck/"&gt;Stacking the Deck&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Author: Matthew Bischoff&lt;/p&gt;
&lt;h3&gt;Summary&lt;/h3&gt;
&lt;p&gt;Design and present a slide deck to get your ideas adopted.&lt;/p&gt;</description><category>communication</category><category>persuasion</category><category>slides</category><guid>https://janetriley.net/notes/communication/matthew_bischoff__stack_the_deck.html</guid><pubDate>Wed, 25 May 2022 17:00:00 GMT</pubDate></item><item><title>Michael Lopp: Out Loud</title><link>https://janetriley.net/notes/communication/michael_lopp__out_loud.html</link><dc:creator>Janet Riley</dc:creator><description>&lt;p&gt;&lt;a href="https://randsinrepose.com/archives/out-loud/"&gt;Out Loud&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Author: Michael Lopp&lt;/p&gt;
&lt;h3&gt;Summary&lt;/h3&gt;
&lt;p&gt;Tips on delivering a compelling presentation from Rands in Repose.  Editorial choices, practicing out loud, consolidation, and timing. &lt;/p&gt;</description><category>communication</category><guid>https://janetriley.net/notes/communication/michael_lopp__out_loud.html</guid><pubDate>Wed, 25 May 2022 17:00:00 GMT</pubDate></item><item><title>Pixar in a Box</title><link>https://janetriley.net/notes/communication/pixar_in_a_box.html</link><dc:creator>Janet Riley</dc:creator><description>&lt;p&gt;&lt;a href="https://www.khanacademy.org/humanities/hass-storytelling/storytelling-pixar-in-a-box/ah-piab-we-are-all-storytellers/a/activity-1?modal=1"&gt;Pixar in a Box: the art of storytelling&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Author: Pixar&lt;/p&gt;
&lt;p&gt;Summary: A Khan Academy course. Pixar walks us through building stories, with an emphasis on movies. Character development, plot, reinforcing the story with visual choices, pacing, and making a pitch. &lt;/p&gt;
&lt;p&gt;This recommendation was in an article on more compelling technical presentations. Not really a fit for the format and time limits of a tech talk, but still interesting.&lt;/p&gt;</description><category>communication</category><category>storytelling</category><guid>https://janetriley.net/notes/communication/pixar_in_a_box.html</guid><pubDate>Wed, 25 May 2022 17:00:00 GMT</pubDate></item><item><title>Series: Making Complex Topics Stick</title><link>https://janetriley.net/notes/communication/gregor_hohpe__making_complex_topics_stick.html</link><dc:creator>Janet Riley</dc:creator><description>&lt;p&gt;Author: Gregor Hohpe&lt;/p&gt;
&lt;p&gt;Summary: A six part series on communicating technical ideas in an accessible way.  By Gregor Hohpe, author of "The Architect Elevator"&lt;/p&gt;
&lt;p&gt;&lt;a href="https://architectelevator.com/strategy/complex-topics-stick/"&gt;Part 1: Content&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://architectelevator.com/strategy/logos-ethos-pathos/"&gt;Part 2: Composition&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://architectelevator.com/strategy/presenting-like-architect/"&gt;Part 3: Delivery&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://architectelevator.com/strategy/presenting-multiplex/"&gt;Part 4: Multiplexing&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://architectelevator.com/strategy/presenting-waveform/"&gt;Part 5: Waveforms&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://architectelevator.com/strategy/presenting-second-curse/"&gt;Part 6: The Second Curse of Speaking&lt;/a&gt;&lt;/p&gt;</description><category>communication</category><category>presenting</category><category>speaking</category><category>storytelling</category><guid>https://janetriley.net/notes/communication/gregor_hohpe__making_complex_topics_stick.html</guid><pubDate>Wed, 25 May 2022 17:00:00 GMT</pubDate></item><item><title>Tanya Snook: Storytelling</title><link>https://janetriley.net/notes/communication/tanya_snook__storytelling.html</link><dc:creator>Janet Riley</dc:creator><description>&lt;p&gt;&lt;a href="https://www.spydergrrl.com/2016/05/storytelling-building-compelling.html"&gt;Storytelling: Building Compelling Stories for Any Audience&lt;/a&gt;
and &lt;a href="https://drive.google.com/open?id=0B4RwK7S5GMvbS1ZVamdZbU9qbXc"&gt;presentation notes&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Author: Tanya Snook&lt;/p&gt;
&lt;p&gt;Excerpt: "This presentation explores storytelling at work. Not milk-and-cookies-time-around-the-campfire storytelling, but using storytelling methods to build and deliver messages in a compelling way. Using empathy to draw your audience in and help them to hear your message, and hopefully create a memorable experience in the process."&lt;/p&gt;</description><category>communication</category><category>storytelling</category><guid>https://janetriley.net/notes/communication/tanya_snook__storytelling.html</guid><pubDate>Wed, 25 May 2022 17:00:00 GMT</pubDate></item></channel></rss>