Real estate development is a team sport played by specialists who often speak different languages. The land acquisition analyst thinks in terms of zoning density and entitlement risk. The architect visualizes massing and materiality. The construction manager lives in schedules and subcontractor coordination. When these worlds collide without empathy, projects suffer from costly rework, missed deadlines, and eroded trust. We have seen teams unravel over a misread email or a decision made in isolation. The good news is that empathy is not a fixed trait—it is a skill that can be practiced. In this guide, we share five exercises that have helped development teams collaborate more effectively. These are not theoretical ideals; they are grounded in the messy reality of project life. Try one, adapt it, and see what shifts.
1. Why Empathy Matters Now in Real Estate Development
Development projects are growing more complex. Mixed-use towers require coordination across dozens of consultants. Public-private partnerships demand that developers understand community concerns alongside investor expectations. At the same time, teams are often lean, and schedules are tight. In this environment, empathy is not a soft luxury—it is a practical tool for reducing friction and catching errors early.
When team members lack empathy, common problems arise. A civil engineer might design a grading plan without considering how it affects the landscape architect's planting strategy. The financial analyst may push for a lower contingency without appreciating the construction team's exposure to weather delays. These disconnects lead to redesigns, change orders, and strained relationships. Empathy helps each person see the constraints and pressures their colleagues face, so they can make better joint decisions.
Moreover, empathy builds psychological safety—the belief that you can speak up with concerns without being punished. In a psychologically safe team, a junior project coordinator can flag a potential conflict in the schedule without fear of being dismissed. This early warning can save weeks of rework. Research in organizational psychology consistently shows that teams with higher psychological safety outperform others on complex tasks. Real estate development is nothing if not a complex task.
Finally, empathy is a competitive advantage in attracting and retaining talent. The next generation of development professionals values collaborative cultures. If your team is known for silos and blame, you will lose good people to firms that invest in how they work together. Empathy exercises are one concrete way to signal that you care about the human side of development.
2. Core Idea: Empathy as a Collaborative Discipline
Empathy in a team context means understanding a colleague's perspective, motivations, and constraints—and letting that understanding influence your own actions. It is not about agreeing with everyone or being nice all the time. It is about gathering enough insight to make decisions that work for the whole project, not just your silo.
Many people think empathy is something you either have or you don't. In reality, it is a discipline that can be practiced through structured exercises. Just as a construction team runs safety drills to build muscle memory, a development team can run empathy exercises to build collaborative reflexes. These exercises create the space for people to step out of their usual roles and see the project through someone else's eyes.
The five exercises in this guide are designed to address specific empathy gaps that commonly arise in development teams:
- Role shadowing helps team members understand the daily reality of a different discipline.
- Pre-mortems surface hidden assumptions by imagining a future failure and working backward.
- Listening rounds during design reviews ensure every voice is heard before decisions are made.
- Stakeholder mapping broadens empathy beyond the immediate team to include community members, regulators, and end users.
- Weekly check-ins build a habit of sharing not just tasks but also emotional state and workload.
Each exercise takes between 30 minutes and two hours, and none requires a consultant or a budget. The only requirement is a willingness to try something new and a commitment to follow through.
3. How the Exercises Work Under the Hood
The exercises work by creating what we call 'perspective moments'—brief experiences where the usual hierarchy and role boundaries are temporarily suspended. During these moments, the brain forms new associations between your own expertise and someone else's reality. Over time, these associations become automatic, so you start considering the landscape architect's needs even when you are in a hurry.
Let us look at the mechanics of each exercise more closely.
Role Shadowing
Pair two people from different disciplines for a half-day. The 'shadow' follows their partner to meetings, reviews documents, and asks questions. The key is that the shadow is not there to critique or contribute—they are there to observe and learn. Afterwards, each person shares three things they learned that surprised them. This exercise breaks down stereotypes. For example, a financial analyst might discover that the construction manager's daily life is full of small, urgent decisions that cannot wait for a spreadsheet. That insight changes how the analyst communicates budget updates.
Pre-mortem
Before a major milestone (like a design review or a permit submission), gather the team and say: 'It is six months from now, and this project has failed in a spectacular way. What went wrong?' Each person writes down three failure scenarios on sticky notes. Then the group clusters them and discusses the most likely ones. The pre-mortem forces people to articulate fears they might otherwise suppress. It also reveals that different roles worry about different things—and that those worries are often valid. The output is a list of risks to mitigate, but the real value is the shared understanding of what keeps each person up at night.
Listening Rounds
In any meeting where a decision is being made, institute a rule: before anyone can speak a second time, everyone must speak once. This is harder than it sounds. The extroverts and senior people have to wait. The quiet ones are given the floor. Listening rounds ensure that the voice of the junior engineer or the new hire is heard. Often, they have the freshest perspective on a problem because they are not yet embedded in the team's assumptions. This exercise requires a facilitator who can enforce the rule gently but firmly.
Stakeholder Mapping
Take one hour to map all the stakeholders affected by your project—not just the obvious ones like the client and the city planner, but also the neighboring business owners, the future tenants, the local community board, and the subcontractors' workers. For each stakeholder, write down their primary concern and what a win looks like from their perspective. Then discuss where those concerns conflict. This exercise expands the team's empathy circle beyond their immediate colleagues. It also helps anticipate opposition and build more resilient project plans.
Weekly Check-in
Start each week's team meeting with a five-minute round where each person shares two things: their top priority for the week and how they are feeling about the workload on a scale of 1-5. The feeling part is the empathy builder. When a team member says 'I am at a 4 because we are waiting on the geotechnical report and it is stressing me out,' everyone else gains context. They might offer to help, or at least they understand why that person seems tense. Over time, this builds a culture of mutual support.
4. A Walkthrough: Running a Pre-mortem on a Phased Development
Imagine a development team working on a three-phase residential project. Phase 1 is under construction, Phase 2 is in design, and Phase 3 is in site control. The project manager decides to run a pre-mortem before the Phase 2 design review. Here is how it plays out.
The team gathers in a conference room with sticky notes and markers. The project manager sets the scene: 'It is one year from now. Phase 2 has been a disaster—over budget, behind schedule, and the city has issued a stop-work order. Write down three reasons why this happened.'
The architect writes: 'The structural engineer's design required deeper foundations than anticipated, causing delays in excavation.' The construction manager writes: 'The MEP subcontractor went bankrupt mid-project, and we had no backup.' The financial analyst writes: 'We underestimated the cost of the green roof requirement, and the contingency was already spent on Phase 1.' The community liaison writes: 'Neighbors filed a lawsuit over construction noise, halting work for three months.'
When the team clusters the sticky notes, they notice themes: underestimation of costs, reliance on single-source subcontractors, and lack of community engagement. The discussion that follows is candid. The architect admits they had not fully accounted for the soil conditions. The construction manager realizes they need to prequalify backup subcontractors. The financial analyst suggests adding a specific line item for community mitigation. By the end of the hour, the team has a concrete action plan—but more importantly, they have a shared picture of the project's fault lines. The empathy gain is that each person now understands why the others are cautious about certain decisions.
The pre-mortem also revealed a hidden dynamic: the community liaison felt that her warnings about neighborhood concerns were often dismissed. After this exercise, the team agreed to include her in early design meetings so that community feedback could shape the plans before they were finalized. That structural change came directly from the empathy built during the exercise.
5. Edge Cases and Exceptions
No exercise works in every context. Here are some situations where these empathy-building exercises may need adaptation—or may not be appropriate at all.
Extreme Time Pressure
If a project is in crisis mode—say, a permit deadline is 48 hours away—stopping for a pre-mortem or role shadowing will feel counterproductive. In these moments, empathy exercises should be postponed. But do not abandon them entirely. Schedule a 'retrospective' after the crisis passes to rebuild the team's collaborative muscles. The key is to not let urgency become a permanent excuse.
Deeply Entrenched Silos
Some organizations have a culture where different departments actively distrust each other. In such environments, voluntary exercises may be met with skepticism or passive resistance. Start small. Pick the one or two people who are most open to change and run a listening round in a meeting they control. Once they see value, they become champions who can invite others. Trying to force a full-team pre-mortem in a hostile culture can backfire.
Remote or Hybrid Teams
Role shadowing is harder when people are not co-located. Adapt it to a 'virtual shadow' where the shadow joins their partner's video calls for a day, or reviews a sample of their emails (with permission). Listening rounds work well on video if the facilitator is strict about muting and turn-taking. Stakeholder mapping can be done on a shared digital whiteboard. The key is to maintain the same structure and intention, even if the medium changes.
Very Large Teams
If your team has more than 15 people, some exercises become unwieldy. For listening rounds, break into smaller groups of 5-6 and then have each group report one insight. For pre-mortems, have each subgroup focus on a different aspect (e.g., design, construction, finance) and then combine findings. Role shadowing naturally scales because it is done in pairs. Weekly check-ins can be done in department-level meetings, with a summary shared across the whole team.
New Teams
When a team is just forming, exercises like stakeholder mapping and listening rounds can accelerate trust-building. However, be mindful that new members may feel vulnerable. Frame the exercises as a way to learn how the team works, not as a test. The facilitator should model vulnerability by sharing their own uncertainties first.
6. Limits of the Approach
Empathy exercises are not a cure-all. They cannot fix a fundamentally broken incentive structure, a toxic manager, or a business model that pits team members against each other. If your team's bonus system rewards individual heroics over collaboration, empathy exercises will feel like a Band-Aid. The exercises work best when the organizational context supports them—or when the team itself has enough autonomy to create a supportive subculture.
Another limit is that empathy exercises take time, and time is a scarce resource in development. A one-hour pre-mortem is an hour not spent on actual project work. We have found that teams that invest this time see a net positive return through fewer rework cycles and smoother coordination, but the benefit is not always visible immediately. Leaders need patience and a willingness to measure the long-term effect.
Furthermore, these exercises can surface uncomfortable truths. A pre-mortem may reveal that the team does not trust the general contractor's schedule, or that the architect feels the project manager micromanages design decisions. That discomfort is productive, but it requires a facilitator who can handle conflict constructively. If your team tends to avoid difficult conversations, consider bringing in an external facilitator for the first few sessions.
Finally, empathy exercises are not a substitute for clear processes and accountability. A team that communicates well but has no clear decision-making framework will still struggle. Empathy and structure are complementary. Use these exercises to improve how you work within your existing processes, not to replace them.
7. Reader FAQ
How often should we run these exercises?
Role shadowing can be done once per quarter for each pair. Pre-mortems are best timed before major milestones—think design reviews, permit submissions, or construction starts. Listening rounds can be a regular practice in every design or coordination meeting. Weekly check-ins are, as the name suggests, weekly. Stakeholder mapping is useful at project kickoff and again when the project scope changes significantly.
What if someone refuses to participate?
Start with the willing. Do not force anyone. Often, skeptics become believers after they see positive results. You can also frame the exercises as low-stakes experiments: 'Let's try this once and see if it helps.' If someone still refuses, respect their boundary. Over time, they may choose to join when they see colleagues benefiting.
Can these exercises work across different companies (e.g., owner's rep, architect, contractor)?
Yes, but with care. When multiple firms are involved, the power dynamics are different. A subcontractor may feel hesitant to share a concern in a listening round if the general contractor is in the room. In cross-company settings, consider running the exercises within each firm first, and then host a joint session focused on a shared project challenge, not on internal dynamics.
How do we measure whether empathy is improving?
You can use simple pulse surveys: ask team members to rate on a scale of 1-5 how well they feel understood by their colleagues, and whether they feel comfortable raising concerns. Track these scores over time. Also, look for behavioral indicators: are people speaking up more in meetings? Are cross-functional conflicts decreasing? Are decisions being made faster because fewer misunderstandings arise?
What is the single most impactful exercise for a new team?
We have seen the most consistent results from weekly check-ins that include the 'how are you feeling about workload' component. It is low effort, high frequency, and it normalizes talking about challenges. Once that habit is established, the other exercises become easier to introduce.
8. Practical Takeaways
Empathy is not a personality trait; it is a practice. The exercises in this guide are tools to help your team build that practice into the rhythm of project life. Here are three specific actions you can take this week:
- Pick one exercise from this list and schedule it within the next 14 days. Start with the weekly check-in or a listening round—they are the easiest to implement.
- Identify one person on your team from a different discipline and ask them for a 30-minute conversation about their biggest frustration on the current project. Listen without trying to solve anything. That alone is an empathy exercise.
- After running an exercise, spend five minutes as a team reflecting on what you learned. Ask: 'What surprised you? What will you do differently because of this conversation?' That reflection is where the lasting change happens.
Real estate development is hard enough without adding miscommunication and mistrust to the mix. By investing in empathy, you are investing in the one asset that every project depends on: the ability of a diverse group of people to work together toward a common goal. Start small, be consistent, and watch how the dynamics shift.
Comments (0)
Please sign in to post a comment.
Don't have an account? Create one
No comments yet. Be the first to comment!