Omar, the owner of Sauce & Spoon, has requested that Peta expand the tablet rollout to include all dining sections, not just the bar. Deanna expects Peta to do what she can to accommodate an expansion, but Peta feels it is outside the scope of the project. However, because Omar is the owner and a senior stakeholder, Peta decides to get input from other team members. She hopes to identify at least two team members who will support her position on keeping the rollout confined to the bar area. Peta meets with Gilly, Alex, Larissa, Zane, Seydou, and Carter to discuss the pros and cons of expanding the tablet rollout.
Step 1: Access the template
To use the template for this course item, click the link below and select “Use Template.”
Link to template: Email Coalition
OR
If you don’t have a Google account, you can download the template directly from the attachment below.
Activity Template_ Email Coalition
DOCX File
Step 2: Access the supporting materials
The following supporting materials will help you complete this activity. Keep them open as you proceed to the next steps. Each link will open a new Coursera tab.
Email Exchange: Stakeholder Intro
Meeting: Identify Mutual Benefits
Note: To access supporting materials introduced in earlier activities, you can find them in the Resources section.
Step 3: Review the supporting materials
Review the email exchange and meeting transcript. Make note of the following details:
Each person’s involvement with the project
Their stated position on the expansion
Any mutual benefits that could result from keeping the tablet rollout confined to the bar area (remember, a mutual benefit is when all parties involved gain some kind of value or advantage)
You are also encouraged to make note of any other relevant project information. You may add this information to your notes or the project charter.
Step 4: Identify two people to join your coalition
Based on your notes, identify two potential allies to support you in pushing back against the expansion. You can choose from among the following stakeholders:
Gilly
Alex
Larissa
Zane
Seydou
Carter
When choosing potential supporters, consider how much power and influence they have (it may be helpful to refer to your stakeholder analysis and power grid). Your coalition must have enough power and influence to help you convince two senior stakeholders—Deanna, the Director of Operations, and Omar, the owner of Sauce & Spoon—that expanding the rollout is not a good idea.
Step 5: Write an email to each potential supporter
After identifying two potential supporters, write a separate email to each one asking them to join your coalition. Make sure that each email has a subject line, greeting and introduction, body, conclusion, and closing.
Each email should also Include the following:
A short summary of Omar’s request to expand the rollout
At least two reasons why expanding the rollout may be unwise
A request to help you convince Omar and Deanna to stick with the original plan and limit the rollout to the bar area
Step 6: Apply Conger’s four steps of effective influencing
As you compose your email, remember to apply Conger’s steps to influence others effectively:
Establish credibility
Frame for common ground
Provide evidence
Connect emotionally
When planning your influencing approach for each email, consider your audience, their involvement in the project, and their thoughts on the expansion. Think about how an expanded test launch might affect them, as well as any mutual benefits that could affect them.
The Correct Answer and Explanation is :
Here are two sample emails to potential supporters, followed by a 300-word explanation.
Email to Gilly
Subject: Seeking Your Support to Maintain the Tablet Rollout Scope
Hi Gilly,
I hope you’re doing well. I wanted to reach out regarding Omar’s recent request to expand the tablet rollout to all dining sections. While I understand his enthusiasm, I have concerns about moving beyond the original scope and wanted to see if you’d be willing to help push back on this expansion.
Expanding beyond the bar presents two key challenges. First, we haven’t tested the logistics of full-restaurant implementation, meaning potential operational inefficiencies could arise. Second, our staff needs time to adjust to tablet usage in a controlled environment before expanding, or we risk overwhelming both servers and customers.
I know you value smooth service and ensuring a positive guest experience. Keeping the rollout limited to the bar allows us to collect data and refine processes before considering further expansion. Would you be open to joining me in making this case to Omar and Deanna? Your insights and support would be invaluable.
Looking forward to your thoughts.
Best,
Peta
Email to Alex
Subject: Need Your Help to Keep the Tablet Rollout Focused
Hi Alex,
I’m reaching out to get your thoughts on Omar’s request to expand the tablet rollout to all dining sections. While I understand his reasoning, I believe it’s in the restaurant’s best interest to keep the rollout confined to the bar as originally planned.
Rushing expansion poses two main risks: operational disruptions and staff resistance. The bar-only rollout allows us to evaluate efficiency and customer reactions before making system-wide changes. Expanding prematurely could lead to technical issues, longer wait times, and customer dissatisfaction.
Since you’ve been closely involved in implementation, your support would strengthen our argument to maintain the current plan. Would you be open to joining me in advocating for this approach? Your expertise would be incredibly helpful in persuading Omar and Deanna.
Let me know what you think.
Best,
Peta
Explanation (300 words)
The emails above effectively persuade Gilly and Alex to join Peta’s coalition against expanding the tablet rollout beyond the bar. Each email follows Conger’s four steps of effective influencing:
- Establishing Credibility – Peta references her knowledge of the project’s scope and the potential risks of expansion, reinforcing her expertise. She also acknowledges the recipient’s experience, demonstrating respect for their insights.
- Framing for Common Ground – The emails align the argument with each recipient’s concerns. Gilly is likely focused on guest experience, so Peta highlights the risk of overwhelming staff and disrupting service. Alex, as someone involved in implementation, is presented with concerns about technical and operational inefficiencies.
- Providing Evidence – Both emails present logical reasons for limiting the rollout: avoiding untested logistics, preventing staff overwhelm, and ensuring smoother service before expansion. These are concrete points backed by operational reasoning.
- Connecting Emotionally – Peta personalizes the request by addressing each person’s role and expertise, making them feel valued. She also presents the risks in a way that affects them directly, increasing their investment in the decision.
By tailoring the emails to each recipient’s perspective, Peta increases the likelihood of securing their support, strengthening her coalition against the expansion.