Communication from Another Perspective

When leading a team, it is easy to assume that the job is done once tasks have been assigned, deadlines set and outcomes checked. Yet people may experience the same message very differently. One colleague wants to understand the goal immediately, another values the space to explore ideas, a third is concerned about how the work affects the team, and a fourth needs details and clear quality criteria. Paying attention to such differences can change how we communicate, resolve misunderstandings and build trust.

Editorial note (October 2026): This is a restored and expanded edition of Darko Perović's personal reflection “Komunikacija iz druge perspektive” (“Communication from Another Perspective”), originally published on 16 December 2024. The original byline, leadership experience in an IT company, emphasis on seeing situations from another person's perspective and four named profiles—direction, inspiration, service and competence—are preserved. The additional scenarios, discussion techniques and practical questions below are editorial illustrations, not newly attributed events from Darko's biography. The four profiles are treated as prompts for reflecting on communication preferences, not a scientifically validated personality test or permanent employee classification.

Leadership starts with a change of perspective

In the original essay, Darko Perović described a change in how he understood leadership. Earlier in his career, he placed emphasis on delegating work and monitoring results. Through experience with different people, he came to see another requirement: a manager cannot fully understand the team by interpreting every situation only from the manager's own viewpoint.

Work conversations contain more than the words being spoken. One employee may perceive an approaching deadline as a clear challenge, another as a risk caused by missing information and another as a concern about how the workload will affect colleagues. When leaders overlook those differences, an otherwise reasonable decision can be misunderstood.

Seeing a situation through someone else's eyes does not mean automatically agreeing with every request. It means checking what that person is trying to communicate, which circumstances they see and what support they need. That is a practical starting point for cooperation.

What does it mean to stand in someone else's shoes?

The historic article used the familiar image of stepping into another person's shoes. This should not become an invitation to guess other people's thoughts. On the contrary, assumptions about what someone feels or needs should be checked through questions and careful listening.

Imagine that an employee rarely contributes during a meeting. One explanation might be a lack of ideas; another is that they need time to consider a question or prefer not to interrupt. Without a conversation, a manager does not know which explanation is right. A respectful question after the meeting may be more useful than drawing a public conclusion about motivation.

An editorial exercise is to ask, before an important conversation: What do I not yet know? Which of my assumptions have I treated as facts? What question would help me check understanding? Perspective comes from dialogue rather than labels.

The four profiles mentioned in the original essay

The original text referred to a model with four personal profiles: direction, inspiration, service and competence. Darko wrote that this framework helped him think about what motivates different team members, how they make decisions and how they fit into collective work. That is the historical context in which it is retained here.

There is an important limit to this description. The accessible historical article does not identify a precise model origin, questionnaire, measurement reliability or scientific validation. We therefore do not use the four terms as diagnoses, fixed personality types or evidence for selecting applicants and evaluating performance.

Instead, they can serve as simple conversation prompts. Does this person currently need a clearer goal, more room for ideas, more reassurance about team support or a deeper explanation of quality standards? The same person may need different things in different circumstances.

Direction: a need for clarity and decisions

In this editorial interpretation, direction points to conversations focused on goals, decisions and next steps. When responsibilities must be agreed quickly, a concise explanation of priorities and expected outcomes may be particularly useful.

Consider a colleague asking what must be finished by Friday, who will decide if requirements change and what counts as a satisfactory result. A good response includes the task owner, deadline and completion criteria, rather than a vague instruction to work faster.

Clarity must not turn into brusqueness. People seeking a direct answer still deserve an explanation of important consequences and an opportunity to raise difficulties. The objective is to reduce uncertainty, not to shut down discussion.

Inspiration: ideas, meaning and possibility

Inspiration is a reminder that motivation involves more than a checklist. At certain moments, employees may be most interested in understanding why a change matters, what it might improve and where there is room for a creative response.

An editorial example is a discussion of a new process that one team member considers unnecessarily bureaucratic. Rather than immediately defending every procedure, a manager could first explain the problem the process aims to solve and ask whether that goal might be achieved more simply.

This approach does not guarantee a better idea, but it creates space for relevant suggestions. Inspiration also needs a practical follow-up: after discussing possibilities, the team must agree on resources, decisions, responsibilities and timing.

Service: support and relationships in the team

Service can be used as a prompt to consider cooperation, mutual support and the effects decisions have on other people. In some conversations, the most important missing detail is how a task will affect colleagues or customers.

Imagine a manager proposing a faster delivery date and an employee pointing out that another department would have to work through the weekend. That concern should not automatically be interpreted as resistance. It may reveal a real dependency or a workload problem.

Attention to relationships does not require avoiding difficult decisions. A manager may still need to set boundaries or deliver uncomfortable feedback. Respectful communication can make those conversations clearer without abandoning performance standards.

Competence: evidence, expertise and quality

Competence in this illustration draws attention to verifiable information, professional knowledge and quality criteria. In technical work, an essential part of communication may be defining the problem, examining evidence and agreeing on how a result will be tested.

For example, a specialist may ask for a problem statement, records of earlier attempts or proof that a proposed solution satisfies a requirement. A manager can help by preparing context and distinguishing verified facts from assumptions.

A desire for detail should not automatically be treated as indecision, nor as proof that someone is more capable. Communication needs change according to the task. One person may want technical depth during an incident review and a short decision during a scheduling conversation.

Adapt the message without labelling people

The four names may help open a discussion, but they should never become permanent boxes in which colleagues are placed. Teams can simply agree how important information should be shared: short written instructions, examples, space for discussion or detailed acceptance criteria.

Preferences can change over time. A newcomer may need more explanation than an experienced employee. During a serious incident, everybody may prefer quick factual updates rather than a workshop about long-term possibilities.

A more helpful question than “What type are you?” is “What would help you understand this task and make a good decision?” That keeps communication grounded in the situation and respects the complexity of the person.

Active listening and checking understanding

Listening is not simply waiting for an opportunity to speak. It means trying to understand the message and its context, then confirming that interpretation. A manager might summarise a concern: The objective makes sense, but the team does not have access to the necessary information, so the deadline appears risky. Then the manager asks whether that summary is accurate.

Open questions are often better than quick assumptions: What is slowing you down? Which part of the decision is unclear? What would let you move forward independently? Leaders also need to hear answers that differ from their expectations.

There are limits to what anyone is entitled to know. Employees have a right to privacy and need not reveal every personal circumstance. Empathetic communication creates a respectful opportunity to speak; it is not a requirement to disclose private feelings.

Feedback that helps build trust

In the original essay, Darko emphasised feedback from the team as a particularly valuable response to perspective-taking. When colleagues believe that a leader genuinely wants to understand them, they may be more willing to share concerns and suggestions.

In practice, it helps to separate observations from judgments about a person. Instead of saying that someone lacks motivation, a manager can state that a particular deliverable was late, ask what blocked progress and agree on the next step. The discussion remains accountable without reducing a person to a negative label.

Trust depends on actions rather than slogans. If employees are mocked or punished whenever they report a problem, they are likely to stop speaking openly. Leaders should explain what happened as a result of feedback, even when not every suggestion can be accepted.

Perspective-taking in conflict and under pressure

The need to consider another perspective is often greatest when conversation becomes difficult. During an outage, a customer escalation or a delayed project, different teams naturally focus on different parts of the problem. Engineers may concentrate on root cause, sales staff on customer commitments and management on wider business consequences.

A productive first step is to establish shared facts: what happened, who is affected and which information is missing. Participants can then explain their priorities without assuming that other teams care less about the outcome.

Considering multiple views does not mean every proposal has equal merit. Decisions still require evaluation of risk, deadlines and resources. But understanding different concerns makes it less likely that a practical disagreement turns into a personal contest about who is right.

Leadership requires continuous reflection

Another central idea of the original essay is that leadership learning does not end with experience. Habits that work in a small team may be less effective in a larger organisation. Communication once experienced as admirably direct may, in another context, feel like skipping important questions.

It is useful to request specific feedback from time to time: Which information helped? What remained unclear? How might the discussion have been conducted differently? Managers can also reflect on their own reactions under pressure.

The purpose is not to doubt every decision endlessly. It is to notice when a way of communicating no longer helps people understand goals and cooperate. Adjusting an approach can demonstrate responsibility rather than weakness.

Beyond the workplace: the value of understanding

Darko's original text made clear that seeing the world from another person's perspective also matters outside business. Family life, friendship and everyday interactions all involve differences between our own experience and what another person may be going through.

This editorial expansion does not introduce additional biographical claims about the author. It highlights a general principle: the same event can carry different meanings for different people, and a respectful question is often more useful than an immediate judgment.

Understanding another perspective does not require abandoning personal boundaries. Healthy relationships also depend on being able to say what one can and cannot accept without dismissing the other person's viewpoint.

Conclusion: a leader does more than assign tasks

“Communication from Another Perspective” remains a reflection on a meaningful shift in leadership: from concentrating solely on assigned tasks and measurable outcomes toward making an effort to understand how other people see the work. Darko Perović connected that idea with leading an IT company, four descriptive profiles and the value of feedback.

The next practical step can be simple. In your next conversation, spend less time assuming what someone needs and more time asking questions and checking your understanding. Clear decisions and responsibility still matter, but it is easier to build a team when people know that their perspective has been heard.

Related service: business consulting.