I remember sitting across from a visibly frustrated engineering manager in Singapore. She had just come out of a performance review with one of her strongest developers, and the conversation had gone sideways. ‘I gave him honest feedback,’ she told me, ‘and he completely shut down. He barely said a word for the rest of the meeting. Now I am worried he is going to start looking for another job.’ When I asked her to walk me through exactly what she had said, the problem became clear almost immediately.
She had opened with, ‘You need to improve your communication with stakeholders — it is not at the level we need.’ Direct? Yes. Honest? Absolutely. But it landed like a verdict rather than a conversation. The developer heard criticism of who he was, not guidance on what he could do differently. He did not hear a leader invested in his growth. He heard a leader who was dissatisfied with him as a person.
Over twenty years of coaching leaders across ASEAN, I have seen this pattern repeat itself hundreds of times. Leaders know that feedback is essential. They have read the articles, attended the workshops, and intellectually understand its importance. But when the moment arrives, most default to one of two extremes: they either deliver feedback so bluntly that it damages the relationship, or they soften it so much that the message gets lost entirely. Both approaches fail. The art of giving feedback that people actually want to hear lies in a specific, learnable structure that balances honesty with respect.
The Communication Gap
The feedback gap in most organisations is not about frequency — it is about quality. Many leaders I coach tell me they give regular feedback. But when I speak with their teams, I hear a different story. Team members describe feedback that is vague (‘You need to step up’), untimely (delivered weeks after the event), or one-directional (the leader talks, the team member nods). This kind of feedback does not develop people — it alienates them.
In ASEAN business culture, the feedback gap is particularly pronounced. Face-saving is a deeply embedded value across Malaysian, Indonesian, Singaporean, and Thai workplaces. This does not mean people do not want feedback — they do, desperately. But the way feedback is delivered matters more than in many Western contexts. Public criticism, even if well-intentioned, can cause lasting damage to trust and morale. And vague positive feedback (‘Good job’) is seen as empty and insincere by high performers who genuinely want to grow.
The leaders who get feedback right understand that it is not a transaction — it is a relationship act. Every piece of feedback either deposits trust into the relationship or withdraws it. The goal is to make feedback feel like a gift the receiver genuinely values, not a burden they have to endure.
The S.T.A.R.T. Framework for Effective Feedback
1. Situation — Anchor Feedback in a Specific Moment
Vague feedback is useless feedback. When you say, ‘You need to communicate better,’ the receiver has no idea what you are referring to. Which communication? When? With whom? The lack of specificity forces them to guess, and human nature means they will either assume the worst or dismiss it entirely.
Effective feedback starts by anchoring the conversation in a specific, observable situation. Instead of general statements, describe exactly what you observed, when it happened, and the context. For example: ‘In Tuesday’s sprint review, when the product owner asked about the delay in the authentication module, I noticed you gave a very brief answer without explaining the technical constraints the team faced.’
I coached a delivery lead in KL who transformed her feedback conversations simply by adopting this practice. She told me, ‘When I anchor feedback in a specific moment, people stop getting defensive. They can see what I am talking about. It becomes a discussion about that moment rather than a judgement about their character.’ This is the power of specificity — it depersonalises the feedback and makes it actionable.
A practical tip: keep a running note during the week of specific observations — both positive and developmental. When it comes time for a feedback conversation, you will have concrete examples rather than fuzzy impressions. This also prevents the recency bias that causes most leaders to focus only on what happened in the last few days.
2. Task and Impact — Connect Behaviour to Outcomes
Once you have described the situation, explain what was at stake and the impact of the behaviour. This is where feedback shifts from observation to insight. People need to understand not just what they did, but why it matters.
Continuing the example above: ‘The product owner walked away without a clear understanding of why the delay happened. As a result, she escalated it to the steering committee as a risk item, which created unnecessary pressure on the team.’ Now the developer understands the chain of consequences. The feedback is not about your personal preference for longer explanations — it is about a tangible business impact.
I have seen this step transform feedback conversations in Jakarta and Singapore alike. When you connect behaviour to impact, you shift from ‘I did not like what you did’ to ‘Here is what happened as a result of what you did.’ The former triggers defensiveness. The latter triggers reflection. One engineering manager I coached started every piece of developmental feedback with, ‘Let me share the impact I observed,’ and told me it was like a magic key that unlocked receptivity in his team.
Be specific about impact at multiple levels: impact on the project, impact on stakeholders, and impact on the individual’s own professional reputation. When people see that you are giving feedback because you care about their career trajectory, not just the project deliverable, they lean in rather than shut down.
3. Alternative — Suggest a Specific, Actionable Path Forward
This is where most feedback conversations fall apart. Leaders describe the problem but leave the solution vague. ‘You need to communicate better’ is not actionable. ‘Next time the product owner asks about a delay, try structuring your response with three elements: what happened, why it happened, and what the revised plan is’ — that is actionable.
The alternative should be specific enough that the person can visualise themselves doing it. I often encourage leaders to frame it as a dialogue. For instance: ‘Imagine the product owner asks you the same question next week. You could say something like: The authentication module is running five days behind our original estimate because we discovered a security dependency we had not accounted for. Here is our revised plan and the new target date. Would you like me to walk through the details? That kind of structured response gives the stakeholder confidence and positions you as someone who is on top of the situation.’
I worked with a team lead in Penang who told me, ‘When my manager gives me a specific alternative, I feel like she is coaching me, not criticising me. It is the difference between being told I am not good enough and being shown how to be better.’ That distinction — coaching versus criticising — is everything. The best feedback makes people feel empowered, not diminished.
Always frame the alternative as one option, not the only option. Say, ‘One approach you might try is…’ rather than ‘You should have done…’ This preserves the receiver’s autonomy and signals that you respect their ability to find their own path forward.
4. Request Input — Make Feedback a Two-Way Conversation
After you have described the situation, the impact, and a suggested alternative, pause. Invite the receiver to share their perspective. This is not a formality — it is essential. There may be context you are missing. The developer might have given a brief answer because the product owner had previously told him she preferred concise updates. You will never know unless you ask.
Try questions like: ‘What is your perspective on that situation?’ or ‘Is there context I might be missing?’ or ‘How does this land with you?’ These questions signal that feedback is a dialogue, not a monologue. They also give you crucial information that may reshape your understanding.
In a coaching session in KL, a director told me about a feedback conversation that completely shifted when he asked for input. He had been ready to give corrective feedback about missed deadlines, but when he asked for the team member’s perspective, he learned that the team member had been covering for a colleague who was dealing with a family emergency — something the director had no idea about. The conversation pivoted from correction to support, and the trust between them deepened significantly.
5. Timeline and Follow-Up — Create Accountability with Care
Feedback without follow-up is just a conversation. Effective feedback includes a clear timeline for revisiting the topic and a commitment to ongoing support. This does not mean micromanaging — it means demonstrating that you are invested in the person’s growth, not just ticking a box.
Close your feedback conversation with something like: ‘Let us revisit this in two weeks. I would love to hear how the next sprint review goes with the new approach. And if you want to practise your stakeholder updates with me beforehand, my door is open.’ This creates gentle accountability while reinforcing that you are on their side.
A senior manager in Singapore adopted this practice and told me, ‘The follow-up conversation is where the real growth happens. The initial feedback plants the seed, but the follow-up is where you see whether it has taken root.’ She was right. Leaders who follow up consistently build a culture where feedback is welcomed because people know it comes with genuine support.
The best feedback does not just tell people what to change — it makes them believe they are capable of changing it.
How to Practice This Week
Identify one person on your team who would benefit from developmental feedback. Before the conversation, write down the specific situation, the impact you observed, and a concrete alternative you can suggest. During the conversation, follow the S.T.A.R.T. framework: describe the Situation, explain the Task and impact, offer an Alternative, Request their input, and agree on a Timeline for follow-up. After the conversation, reflect on how it went. Did the person seem receptive? Did you learn something you did not expect? Practise this once this week, and you will already notice a shift in how feedback lands.
Key Takeaway
Feedback is not about being honest at someone — it is about being honest with them. When you anchor feedback in specific observations, connect it to tangible impact, offer actionable alternatives, and invite dialogue, you transform feedback from something people dread into something they actively seek. In the relationship-driven business cultures of ASEAN, this approach does not just develop individuals — it builds the trust that holds high-performing teams together.
Ready to Transform Your Communication?
Giving effective feedback is one of the most impactful skills a leader can develop, and like any skill, it improves dramatically with structured practice and expert guidance. Our Constructive Feedback & Coaching Skills workshop at Being Specific provides leaders with hands-on practice using real scenarios, personalised coaching, and frameworks you can apply immediately. Visit being-specific.com/contact to find out more and book your session.
