Skip to content

Commit e4396ff

Browse files
authored
Update “Effective Communication” page (#925)
Some improvements from January based on earlier trainings.
1 parent 1016690 commit e4396ff

File tree

2 files changed

+114
-16
lines changed

2 files changed

+114
-16
lines changed

src/technology-consulting/5-communication.md

Lines changed: 110 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -95,18 +95,6 @@ The [communication planning](#communication-planning) section covers strategies
9595

9696
- Define the purpose of your communication and state expectations explicitly.
9797

98-
When reading about [business writing](#business-writing), you’ll learn how to create clear, concise, and actionable communication.
99-
100-
- Specify clear actions and deadlines in your writing.
101-
- Avoid assumptions — write for clarity without losing context.
102-
- Remove emotionally charged language from professional communication.
103-
104-
The [effectively using tools](#communication-tools) section discusses using tools like Grammarly and LLMs to support communication, while emphasizing transparency.
105-
106-
- Use Grammarly for proofreading but review AI suggestions for accuracy.
107-
- Leverage LLMs for brainstorming and gathering feedback.
108-
- Be transparent about AI usage in your process.
109-
11098
The [learn-technology-consulting/communication-methods] page outlines best practices for effectively communicating over [learn-technology-consulting/communication-methods#chat chat].
11199

112100
- Use shared channels to post updates and follow up on threads.
@@ -131,6 +119,18 @@ The section on [learn-technology-consulting/communication-methods#choosing-the-b
131119
- Move long-term reference material to wikis.
132120
- Choose high-bandwidth methods, like meetings, for nuanced topics.
133121

122+
The [effectively using tools](#communication-tools) section discusses using tools like Grammarly and LLMs to support communication, while emphasizing transparency.
123+
124+
- Use Grammarly for proofreading but review AI suggestions for accuracy.
125+
- Leverage LLMs for brainstorming and gathering feedback.
126+
- Be transparent about AI usage in your process.
127+
128+
When reading about [business writing](#business-writing), you’ll learn how to create clear, concise, and actionable communication.
129+
130+
- Specify clear actions and deadlines in your writing.
131+
- Avoid assumptions — write for clarity without losing context.
132+
- Remove emotionally charged language from professional communication.
133+
134134
Finally, the [learn-technology-consulting/giving-receiving-feedback] page outlines methods for delivering and receiving feedback effectively.
135135

136136
- Provide empathetic, timely, and actionable feedback.
@@ -1142,6 +1142,22 @@ In the midst of a significant data center outage, you realize that the disaster
11421142

11431143
</details>
11441144

1145+
#### Discovery
1146+
1147+
<details>
1148+
<summary>Discovery phase for conversion rate optimization</summary>
1149+
1150+
In your role at Bitovi, you are leading the discovery phase for a new client seeking to improve their website’s conversion rate. The website struggles to turn visitors into leads, and your team has been tasked with delivering actionable, prioritized recommendations. However, the situation is complicated by conflicting perspectives among internal stakeholders:
1151+
1152+
- Analytics reveal high bounce rates on key pages, including the blog, resources, and product landing pages.
1153+
- User surveys indicate visitors struggle to locate relevant content quickly, leading to frustration and early exits.
1154+
- The marketing team advocates for adding more direct, prominently placed calls to action across the site to drive conversions.
1155+
- The design team recommends a full website redesign to tackle underlying usability issues, but has flagged concerns about budget constraints.
1156+
- Leadership has delegated the task of reconciling these differing opinions to the client’s product owner, who lacks a clear framework for prioritization.
1157+
- Some client stakeholders believe focusing solely on the homepage will yield the fastest improvements, while others push for a broader approach.
1158+
1159+
</details>
1160+
11451161
#### Frontend
11461162

11471163
<details>
@@ -1183,6 +1199,28 @@ You’re working on a new feature for a mobile application, but the product requ
11831199

11841200
</details>
11851201

1202+
#### Leadership
1203+
1204+
A new design system is being developed for internal use and for client projects. This system will be the go-to toolkit for internal projects and new clients. It promises consistent experiences and a recognizable brand presence that is customizable to fit every client’s needs.
1205+
1206+
Challenges arise:
1207+
1208+
- The Digital Product team is eager to highlight the design system on the company blog but needs a cohesive narrative and polished visuals.
1209+
- A handful of developers responsible for integrating the system into ongoing client work are uncertain about its long-term benefits. They have questions about documentation and asset organization.
1210+
- A group of existing clients, aware that a new system is in the works, are interested in how they could start using the new system for their upcoming projects, but aren’t sure how it works.
1211+
- Company leadership hopes the system will raise the company’s profile, but they lack a clear sense of how it will drive revenue in the long run.
1212+
1213+
---
1214+
1215+
A new design system is in development for internal and external use. This system aims to .
1216+
1217+
Several challenges have come to a head in the last week:
1218+
1219+
- The blog team wants to promote the system on the company blog and LinkedIn. They need a clear, compelling narrative and polished visuals to help both internal staff and external audiences understand what the system is and why it matters.
1220+
- Developers integrating the system into current client work are skeptical about its usefulness. They need answers about documentation, asset organization, and how adopting the system will affect their day-to-day tasks.
1221+
- A couple of existing clients have shown interest, but are unsure how using the system will impact their existing contracts, timelines, and established processes. They need a clear explanation of the path to adoption, the benefits they’ll gain, and how any transition will be managed.
1222+
- Leadership is watching but does not see how the design system will directly support revenue goals. They want clarity on how this initiative leads to stronger sales, better retention, or new market opportunities.
1223+
11861224
#### Product Design
11871225

11881226
<details>
@@ -1224,6 +1262,62 @@ As a Product Designer, you’ve finished the designs for a new e-commerce featur
12241262

12251263
</details>
12261264

1265+
#### Sales
1266+
1267+
##### Reviving a stalled lead
1268+
1269+
You’ve been nurturing a promising lead for months, but they’ve stopped responding to emails. You suspect they’re still interested, but internal challenges and other distractions may be stalling their decision-making process:
1270+
1271+
- Your point of contact, who was previously enthusiastic, has grown unresponsive. In their last interaction, they mentioned upcoming organizational changes, which may have affected priorities.
1272+
- The company has recently had layoffs and budget cuts.
1273+
- At the same time, a new director has joined their team, but you haven’t yet established a relationship with them.
1274+
- Internally, the capability department Directors are pushing to close this deal, because it would be a big deal if we won it.
1275+
- The client’s industry is experiencing rapid change, and you know Bitovi could address the emerging challenges, but you’re not sure if they see the urgency.
1276+
1277+
Your task: Identify key audiences and strategies to re-engage this lead, address their concerns, and push the deal forward while maintaining professionalism and trust.
1278+
1279+
---
1280+
1281+
##### Overcoming Objections Late in the Sales Cycle
1282+
1283+
You’re in the final stages of closing a deal with a prospective client, but during contract negotiations, unexpected objections arise that threaten to derail the agreement:
1284+
1285+
- The procurement team, which previously approved preliminary budgets, is now flagging your pricing as too high compared to internal estimates.
1286+
- The prospect’s legal team has raised concerns about liability clauses in the contract, requesting modifications that your internal leadership is hesitant to approve.
1287+
- Your internal advocate at the prospect company, who has been pushing for the deal, is starting to feel sidelined by their leadership during final decision-making.
1288+
- A competitor, thought to have been ruled out earlier, has resurfaced with a discounted offer that is creating additional pressure.
1289+
- Your internal delivery team has allocated resources for this project, but a prolonged delay in closing may force you to reassign them.
1290+
1291+
Your task: Develop a communication plan to address the objections, reaffirm your value, and guide the client toward closing the deal. Consider how to align your messaging for different audiences involved in this process.
1292+
1293+
---
1294+
1295+
##### Turning a Small Win into a Bigger Opportunity
1296+
1297+
You’ve recently completed a small project for a client, delivering excellent results. While the client is pleased, they haven’t expressed interest in additional collaboration. You see potential for more work, but expanding the relationship requires careful communication:
1298+
1299+
- The client’s team has praised your work but hasn’t provided clarity on their upcoming priorities or budget availability.
1300+
- The client’s company is undergoing a leadership change, which could bring new opportunities or shifts in focus.
1301+
- A competitor has begun pitching a larger, multi-phase engagement to the same client, branding themselves as a more comprehensive partner.
1302+
- The small project revealed operational challenges in the client’s workflow that your team is uniquely positioned to solve.
1303+
- Internally, your sales leadership is eager to explore additional opportunities, but there’s concern about coming across as pushy or overreaching.
1304+
1305+
Your task: Identify the key audiences and craft a communication plan to build on the initial success, uncover the client’s future needs, and position Bitovi as their trusted partner for upcoming challenges.
1306+
1307+
#### TPO
1308+
1309+
##### Conflicting feature prioritization
1310+
1311+
As a Technical Product Owner (TPO), you’re managing a product with a fast-approaching release date, but conflicting priorities among stakeholders are causing delays in decision-making.
1312+
1313+
At the same time:
1314+
1315+
- A flashy new feature is being requested that could attract users, but it adds significant complexity.
1316+
- Technical concerns have been raised about the growing amount of unresolved technical debt.
1317+
- Work on ongoing features has stalled due to unclear direction, leaving team members uncertain about their next steps.
1318+
- There is pressure to meet the release timeline without sacrificing quality or user satisfaction.
1319+
- Concerns about the feasibility of testing all new features thoroughly within the timeline are emerging.
1320+
12271321
## Business writing
12281322

12291323
The best business writing puts the onus on the writer instead of the reader. Think hard about your audience, what they know, what they need to know, their time constraints, etc, and make it as easy on them as physically possible. If you follow this principle, you’ll be a very effective communicator.
@@ -1634,6 +1728,10 @@ Inclusivity is a core Bitovi value. Part of that is recognizing how people want
16341728
- **Avoid problematic colloquialisms:** Steer clear of expressions with unintended negative connotations or cultural insensitivity, such as [“long time no see.”](https://personifycorp.com/blog/words-to-stop-using/) Use clear and neutral phrases like “it’s been a while” or “general guideline.”
16351729
- **Be mindful of cultural differences:** Recognize that communication styles and meanings can vary across cultures. By being open to learning about and respecting different cultural norms, you can communicate more effectively in diverse teams.
16361730

1731+
As a Bitovian, it is essential to use language that is as inclusive as possible, regardless of personal opinions about specific terms. Clients or colleagues may not always voice discomfort with phrases like “blacklist” or “whitelist,” but part of our responsibility is to proactively foster strong relationships through thoughtful, respectful communication. This is a key element of our role in working with customers, as establishing trust and rapport is foundational to our success.
1732+
1733+
While you might not agree with every aspect of these guidelines, it’s important to put personal feelings aside and focus on what we are trying to accomplish as representatives of Bitovi. These standards are in place not to debate the validity of certain concerns but to reduce risks, align with client expectations, and ensure that we maintain a professional and inclusive presence. Following these guidelines reflects the professionalism and care that Bitovi values.
1734+
16371735
Clear and inclusive communication ensures everyone can fully understand and engage in conversations.
16381736

16391737
- **Enunciate when speaking:** Speak clearly and at an appropriate pace to prevent misunderstandings, especially in virtual meetings or when communicating with non-native speakers.

src/technology-consulting/8-giving-receiving-feedback.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Before offering feedback, it’s essential to prepare thoughtfully. This means u
2626

2727
When the time comes to actually deliver feedback, clear communication and empathy are key.
2828

29-
- **SBI model:** The **Situation-Behavior-Impact (SBI)** model is a helpful way to frame feedback. Start by describing the **situation** where the behavior occurred, specify the **behavior** you observed, and explain the **impact** it had. For example: “In yesterday’s client meeting (situation), you interrupted John several times while he was speaking (behavior). This made it harder for him to express his points and may have come across as dismissive (impact).”
29+
- **Use the SBI model:** The **Situation-Behavior-Impact (SBI)** model is a helpful way to frame feedback. Start by describing the **situation** where the behavior occurred, specify the **behavior** you observed, and explain the **impact** it had. For example: “In yesterday’s client meeting (situation), you interrupted John several times while he was speaking (behavior). This made it harder for him to express his points and may have come across as dismissive (impact).”
3030
- **Make sure feedback is timely and relevant to the context:** Feedback is most effective when it’s given promptly after the observed behavior. This makes it easier for the recipient to connect the feedback with the specific actions or events in question. Additionally, keep feedback relevant to the current context and priorities of the team or project. This helps in addressing issues before they escalate and keeps the feedback aligned with ongoing goals.
3131
- **Offer specific, actionable, and objective feedback:** Avoid vague comments like “You need to be better at communication.” Instead, be specific and actionable: “When speaking with clients, try summarizing their points to show you understand before providing your input.”
3232
- **Be mindful of tone:** Tone plays a huge role in how feedback is received. Aim for a neutral and caring tone. Even well-phrased feedback can be taken poorly if the tone sounds accusatory or dismissive.
@@ -59,7 +59,7 @@ Proactively seeking feedback shows a commitment to self-improvement and openness
5959

6060
- **Seek out feedback proactively:** Don’t wait for formal reviews to ask for feedback. Ask colleagues, clients, or supervisors regularly how you’re doing, and if there’s anything you can do differently or better. You might say, “I’d really appreciate your thoughts on how I handled that client meeting. Was there anything I could improve?”
6161
- **Frame your request positively:** Make it clear that you’re open to all types of feedback. A good way to do this is by saying, “I’m looking for ways to improve, and I would really value your honest input.” This sets the expectation that you’re genuinely interested in growing and encourages others to be candid.
62-
- **Be specific in your request:** Instead of asking for general feedback, be clear about what you want input on. For example, you could say, “Can you give me some feedback on how I handled the project kickoff meeting?” This helps the person giving feedback focus their response and makes it more useful for you.
62+
- **Be specific in your feedback request:** Instead of asking for general feedback, be clear about what you want input on and use open-ended “how” and “what” questions. For example, you could say, “What ways would you have approached that meeting differently to make it a better use of everyone’s time?” This helps the person giving feedback focus their response and makes it more useful for you.
6363
- **Ask different people for feedback:** Diversify the perspectives you get by asking for feedback from people with different working relationships with you. A colleague may offer insights into your teamwork skills, while a manager can provide feedback on strategic decision-making. Each perspective can help you understand your performance more fully.
6464

6565
Questions to reflect:
@@ -75,7 +75,7 @@ Receiving feedback effectively requires an open mind and a willingness to grow.
7575
- **It’s natural to feel defensive or emotional, so breathe and remember it’s not about you personally, it’s about growing professionally:** Feedback can stir up emotions, especially if it feels critical. Remind yourself that feedback is about the work, not you as a person. Taking a breath and focusing on the message rather than the delivery can help manage these feelings.
7676

7777
- **Pause before responding:** It’s okay to take a moment before responding to feedback. Pausing helps you avoid reacting defensively and gives you time to consider what’s being said.
78-
- **Seek examples to understand feedback better:** If the feedback is unclear or too general, ask for specific examples. This helps you understand what actions or behaviors to adjust.
78+
- **Seek examples to understand feedback better:** If you receive feedback that is unclear or too general, ask for specific examples. This helps you understand what actions or behaviors to adjust.
7979
- **Express appreciation for feedback:** Regardless of how the feedback makes you feel, thank the person for their time and effort. A simple “Thanks for taking the time to share this with me” can help foster a positive environment for open communication.
8080

8181
Questions to reflect:
@@ -92,7 +92,7 @@ Questions to reflect:
9292
The work doesn’t stop after you’ve received feedback — what you do with it is what makes a difference.
9393

9494
- **Seek additional perspectives:** Sometimes it’s helpful to get a second opinion, especially if feedback seems unexpected or unclear. Ask a trusted colleague for their perspective to get a fuller picture.
95-
- **Turn feedback into actionable steps:** Break down the feedback into specific actions. For example, if you were told to improve communication in meetings, an action step might be “Summarize key points at the end of each meeting to ensure clarity.”
95+
- **Turn feedback into actionable steps:** Break down the feedback into specific actions. For example, if you were told to proactively communicate with your team members, an action step might be “Share my progress with the team daily.”
9696
- **Create a system for measuring progress:** Set up a way to track your progress. This could be as simple as writing down your goals and checking in weekly or asking for feedback from a trusted colleague to see if they’ve noticed improvements.
9797

9898
## Self-assessment and reflection

0 commit comments

Comments
 (0)