Skip to content

Commit

Permalink
deploy: dd3c180
Browse files Browse the repository at this point in the history
  • Loading branch information
Workflow committed Nov 21, 2024
1 parent 65343c5 commit 88a0c05
Show file tree
Hide file tree
Showing 2 changed files with 32 additions and 86 deletions.
116 changes: 31 additions & 85 deletions learn-technology-consulting/communication.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -639,18 +639,18 @@ <h3 id="overview">Overview</h3>
<ul>
<li>State expectations explicitly and determine the purpose and audience of your communication.</li>
</ul>
<p>Effectively Using Tools to Enhance Communication</p>
<ul>
<li>Use Grammarly to catch errors, but review AI-generated content before sending.</li>
<li>Use LLMs for brainstorming, creating visual aids, or gathering feedback.</li>
<li>Be transparent about AI usage in your communication process.</li>
</ul>
<p>Business Writing</p>
<ul>
<li>Write with clarity and specify clear actions and deadlines.</li>
<li>Avoid assuming shared context — be concise but thorough.</li>
<li>Eliminate emotionally charged language from written communication.</li>
</ul>
<p>Effectively Using Tools to Enhance Communication</p>
<ul>
<li>Use Grammarly to catch errors, but review AI-generated content before sending.</li>
<li>Use LLMs for brainstorming, creating visual aids, or gathering feedback.</li>
<li>Be transparent about AI usage in your communication process.</li>
</ul>
<p>Professional communication</p>
<ul>
<li>Use inclusive language, show compassion, and stay open-minded.</li>
Expand Down Expand Up @@ -857,62 +857,62 @@ <h3 id="emotions">Emotions</h3>
<table>
<thead>
<tr>
<th>Emotion</th>
<th>Voice</th>
<th>Pacing</th>
<th>Facial Expression</th>
<th>Descriptors</th>
<th scope="col">Emotion</th>
<th scope="col">Descriptors</th>
<th scope="col">Voice</th>
<th scope="col">Pacing</th>
<th scope="col">Facial Expression</th>
</tr>
</thead>
<tbody>
<tr>
<td>Angry</td>
<th scope="row">Angry</th>
<td>Aggressive, Bitter, Critical, Distant, Frustrated, Humiliated, Let down, Mad</td>
<td>Loud, forceful, with hard consonants.</td>
<td>Quick, with intensity.</td>
<td>Scowling, clenched jaw, narrowed eyes.</td>
<td>Aggressive, Bitter, Critical, Distant, Frustrated, Humiliated, Let down, Mad</td>
</tr>
<tr>
<td>Bad</td>
<th scope="row">Bad</th>
<td>Bored, Busy, Stressed, Tired</td>
<td>Low, flat, resigned.</td>
<td>Monotone, slow.</td>
<td>Neutral or subtly grimacing.</td>
<td>Bored, Busy, Stressed, Tired</td>
</tr>
<tr>
<td>Disgusted</td>
<th scope="row">Disgusted</th>
<td>Awful, Disapproving, Disappointed, Repelled</td>
<td>Low, nasal, and sharp with emphasis on the negative emotion.</td>
<td>Clipped, abrupt.</td>
<td>Scrunched nose, narrowed eyes, tightened lips.</td>
<td>Awful, Disapproving, Disappointed, Repelled</td>
</tr>
<tr>
<td>Fearful</td>
<th scope="row">Fearful</th>
<td>Anxious, Insecure, Rejected, Scared, Threatened, Weak</td>
<td>Quieter, with a tremble or shakiness.</td>
<td>Hesitant, with frequent pauses.</td>
<td>Wide eyes, tense expression, possibly biting lip.</td>
<td>Anxious, Insecure, Rejected, Scared, Threatened, Weak</td>
</tr>
<tr>
<td>Happy</td>
<th scope="row">Happy</th>
<td>Accepted, Content, Interested, Optimistic, Peaceful, Playful, Powerful, Proud, Trusting</td>
<td>Bright, enthusiastic, with a higher pitch than usual.</td>
<td>Slightly faster, with energy.</td>
<td>Big smile, open eyes.</td>
<td>Accepted, Content, Interested, Optimistic, Peaceful, Playful, Powerful, Proud, Trusting</td>
</tr>
<tr>
<td>Sad</td>
<th scope="row">Sad</th>
<td>Depressed, Despair, Guilty, Hurt, Lonely, Vulnerable</td>
<td>Slow, soft, with a downward inflection.</td>
<td>Drawn-out, with pauses.</td>
<td>Frown, furrowed brows, downcast eyes.</td>
<td>Depressed, Despair, Guilty, Hurt, Lonely, Vulnerable</td>
</tr>
<tr>
<td>Surprised</td>
<th scope="row">Surprised</th>
<td>Amazed, Confused, Excited, Startled</td>
<td>High-pitched, with a sharp rise in intonation.</td>
<td>Sudden shifts, sometimes speeding up mid-sentence.</td>
<td>Wide eyes, raised eyebrows, open mouth.</td>
<td>Amazed, Confused, Excited, Startled</td>
</tr>
</tbody>
</table>
Expand Down Expand Up @@ -1558,15 +1558,15 @@ <h3 id="exercise-communication-plan">Exercise: Communication plan</h3>
<p>Skim through the scenarios below and choose one that resonates with you.</p>
<p>For your chosen scenario, create a communication plan by answering the following questions:</p>
<ul>
<li><strong>Purpose:</strong> What is my goal in communicating with them?</li>
<li><strong>Audience:</strong> Who do I need to communicate with?</li>
<li><strong>Content (main point):</strong> What is the one key idea I absolutely need to convey?</li>
<li><strong>Content (supporting details):</strong> What details should I include? What should I leave out?</li>
<li><strong>Call to action:</strong> What specific action or response do I need from them?</li>
<li><strong>Audience:</strong> With whom do you need to communicate?</li>
<li><strong>Purpose:</strong> Why do you need to communicate with them? What do you want them to feel?</li>
<li><strong>Content (main point):</strong> What is the one key idea you want to communicate?</li>
<li><strong>Content (supporting details):</strong> What are the supporting details that contribute to your main point? [What should you leave out?]</li>
<li><strong>Call to action:</strong> What specific action or response do you need from your audience?</li>
</ul>
<p>Outline your approach and think critically about how to tailor your message for each audience in the scenario you chose.</p>
<h4 id="backend">Backend</h4>
<p><details open>
<p><details>
<summary>Backend API performance concerns</summary></p>
<p>You’re a Backend Developer working on optimizing the API for a social media platform. Several performance issues have been reported by the frontend team, and the client is concerned about user retention:</p>
<ul>
Expand All @@ -1576,60 +1576,6 @@ <h4 id="backend">Backend</h4>
<li>There’s pressure from the project manager to improve performance, but the client keeps adding new features that complicate optimization efforts.</li>
<li>The DevOps team is suggesting a different infrastructure setup to improve performance, but it may require rewriting parts of the code.</li>
</ul>
<p><details>
<summary>Communication plan</summary></p>
<ul>
<li><strong>Purpose:</strong> Collaborate on how to handle large data sets and improve user experience.</li>
<li><strong>Audience:</strong> Frontend developers.</li>
<li><strong>Content (main point):</strong> Pagination will be introduced, but it will require restructuring the existing API endpoints.</li>
<li><strong>Content (supporting details):</strong>
<ul>
<li>Explain that implementing pagination will improve performance for large data sets.</li>
<li>Highlight that restructuring the endpoints is necessary, but it will take time due to the volume of changes required.</li>
<li>Acknowledge their performance issues, but explain that some delays are caused by the backend needing to fetch and process large datasets.</li>
</ul></li>
<li><strong>Call to action:</strong> Ask the frontend team to work with you to test the pagination feature once implemented and provide feedback on any potential impact on the user interface.</li>
</ul>
<hr />
<ul>
<li><strong>Purpose:</strong> Set realistic expectations regarding performance improvements and feature development.</li>
<li><strong>Audience:</strong> Client (who is adding new features).</li>
<li><strong>Content (main point):</strong> While the team is optimizing the API, adding more features can slow down progress and introduce complexity.</li>
<li><strong>Content (supporting details):</strong>
<ul>
<li>Explain that optimizing the search queries and aggregating data from multiple services is the current priority to improve user experience.</li>
<li>Mention that adding new features at this stage may delay these performance optimizations.</li>
<li>Suggest a balance between new features and performance improvements to meet user retention goals.</li>
</ul></li>
<li><strong>Call to action:</strong> Request a discussion on feature prioritization and suggest a phased approach to adding new features after critical optimizations are complete.</li>
</ul>
<hr />
<ul>
<li><strong>Purpose:</strong> Align on performance improvement priorities and manage scope creep from the client.</li>
<li><strong>Audience:</strong> Project Manager.</li>
<li><strong>Content (main point):</strong> Performance improvements are achievable, but ongoing feature requests are complicating the optimization process.</li>
<li><strong>Content (supporting details):</strong>
<ul>
<li>Outline the current performance challenges, especially with search queries and data aggregation.</li>
<li>Highlight that the client’s feature requests are adding complexity to the optimization efforts.</li>
<li>Propose a focus on performance improvements before implementing further features.</li>
</ul></li>
<li><strong>Call to action:</strong> Seek support in pushing back on the client’s immediate feature demands and request that the project manager help manage client expectations to focus on core optimizations first.</li>
</ul>
<hr />
<ul>
<li><strong>Purpose:</strong> Collaborate on improving infrastructure to boost API performance while ensuring minimal code rewrites.</li>
<li><strong>Audience:</strong> DevOps team.</li>
<li><strong>Content (main point):</strong> Any infrastructure changes must be balanced with the feasibility of backend code modifications.</li>
<li><strong>Content (supporting details):</strong>
<ul>
<li>Acknowledge their suggestions for infrastructure changes and the potential benefits for performance.</li>
<li>Explain the code structure’s current state and how much of it might need to be rewritten for the new setup.</li>
<li>Suggest evaluating how infrastructure changes could be phased in without a complete rewrite of the codebase.</li>
</ul></li>
<li><strong>Call to action:</strong> Request their help in outlining a more detailed plan for the infrastructure changes, including an analysis of how to integrate them without causing major disruptions to the backend code.</li>
</ul>
<p></details></p>
<p></details></p>
<p><details>
<summary>Incomplete database migrations</summary></p>
Expand Down
2 changes: 1 addition & 1 deletion static/bundles/bit-docs-site/static.js
View file

Large diffs are not rendered by default.

0 comments on commit 88a0c05

Please sign in to comment.