Scribd
Upload
4 views3 pages

Conflict Resolution in Startup Teams

The document outlines a conflict among four college friends working on an app startup, each with different priorities: Alex focuses on technical functionality, Rhea on deadlines, Neha on user experience, and Saurabh on stability. Tensions arise due to differing views on product development and launch timelines, leading to ineffective team meetings. A resolution plan is proposed, emphasizing social intelligence skills and collaborative action steps to balance technical and design needs while ensuring a successful product launch.

Uploaded by

Raghu
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
4 views3 pages

Conflict Resolution in Startup Teams

The document outlines a conflict among four college friends working on an app startup, each with different priorities: Alex focuses on technical functionality, Rhea on deadlines, Neha on user experience, and Saurabh on stability. Tensions arise due to differing views on product development and launch timelines, leading to ineffective team meetings. A resolution plan is proposed, emphasizing social intelligence skills and collaborative action steps to balance technical and design needs while ensuring a successful product launch.

Uploaded by

Raghu
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Social Intelligence Activity

Name: Raghav Duggal Email Id: Raghavduggal25@gmail


.com

Application No. 113649 Phone No. 6284855055

Scenario:
There are four friends in college who decide to build a new app-based startup. They
want to launch within a tight deadline.

1. Alex (Coder): Focuses on technical functionality.


2. Rhea (Business): Focuses on project deadlines and pushes for a minimal viable
product and quick launch.
3. Neha (UI/UX): Focuses on user-friendliness and market readiness, advocating
for changes requiring technical adjustments.
4. Saurabh (Customer Success): Wants a stable, user-friendly app to minimize
post-launch issues and ensure a smooth user experience.

Conflict:
● Alex is frustrated with Neha's suggestions, which he believes delays technical
progress.
● Neha feels Alex is ignoring user experience.
● Rhea wants a quick launch to meet deadlines.
● Saurabh is worried about potential issues with an incomplete product.
● Team meetings are tense, with interruptions, ignored suggestions, and
avoidance of discussions.

Task:
Using social intelligence concepts, analyze the situation and create a plan to resolve the
conflict. Discuss as a group and fill in the table provided.
Group Members:

[Link] Group Member Name

1 Nishant Gupta

2 Raghav Duggal

3 Shaurya Kochhar

4 Akhil Kumar Anand

Conflict Analysis and Resolution Plan:

Role Concerns & Social Action Steps Expected Outcome


Frustrations Intelligence
Skills Needed

Alex Feels Neha’s Active listening, Listen to Neha’s Improved collaboration,


changes slow empathy, reasoning for balanced technical and
technical flexibility, changes, discuss design needs, reduced
progress and constructive feasibility openly, and tension with Neha.
delay coding feedback. agree on priority
tasks; wants changes that won’t
uninterrupted derail deadlines.
development.

Neha Feels Alex is Perspective- Present user A more user-friendly


ignoring user taking, assertive feedback and data to product without
experience yet respectful justify changes, excessive delays;
and long-term communication, suggest phased mutual respect with
usability; compromise. design improvements Alex.
concerned to meet deadlines
about rushed while maintaining
launch usability.
hurting
product
quality.

Rhea Wants quick Mediation, Facilitate structured Deadline met with a


launch to negotiation, meetings, set clear viable product; reduced
meet conflict timelines, define MVP friction between team
deadlines; management, scope, and mediate members.
worried about prioritization. between tech and
losing market design teams.
opportunity;
frustrated by
ongoing
debates.

Saurabh Worried Problem Share likely customer Smoother launch with


about anticipation, issues based on past fewer customer
incomplete diplomacy, experience, push for complaints; higher
product solution-oriented essential quality customer satisfaction.
causing post- thinking. checks before launch,
launch support phased
complaints; updates post-launch.
wants
stability and
ease of use.

You might also like