Communication Is Not a Soft Skill: The Most Valuable People Can Explain What to Choose, What to Give Up, and What the Outcome Will Be

During that review meeting, I spoke for a full twenty minutes, analyzing the pros and cons of three options, even listing the potential technical debt in the alternatives. As I flipped through the slides, the technical director across from me asked just one question:

So which one do you recommend?

I suddenly froze.

I said something like "it depends on team resources and priorities," but really I just hadn't chosen. Not because I hadn't thought about it, but because I was afraid of the consequences, afraid of being blamed if I was wrong.

In that moment I realized that communication isn't about how complete your explanation is, but whether you can make something actionable, decisive, and ready to land.

Many people treat communication as a "soft skill," something to work on after the technical work is done and your skills are solid enough.

But what really determines whether someone has influence isn't whether they're articulate, but whether they have the ability to make a choice at a critical moment and explain it convincingly.

Especially at work, no project has a perfect solution. Every decision is made through trade-offs. If you can't clearly explain "why this choice," "what we're giving up," and "how we plan to proceed," how can anyone trust you enough to follow?

Later I understood that my failure was because I only did one thing: listed options. What I didn't do was: make a clear recommendation.

More precisely, I talked about the process but not my preference; I talked about the analysis but not my position; I talked about the details but not how to execute.

Truly weighty communication is never a flat recitation; it's about using a clear path to bring others to a decision.

Later I tried a different way of expressing it:

I lean toward option B. Although the development cycle is a bit longer, it's more maintainable. Considering that demand in this area will keep growing, the upfront investment is worth it. We can still adjust the launch timeline, and I'll sync with the product team to see if we can get two more days of buffer.

After hearing this, the leader didn't ask any more questions. The decision was made that same day, and he even said, "That was very clear."

At that moment I knew that sometimes it's not that you haven't prepared enough, but that you haven't said the part people really want to hear: what you want to do, what you've considered, and what you're prepared to take on.

I've now put together a simple model for myself, and I run through it mentally every time I need to explain something:

First, state your preference clearly. For example, "I suggest we go with option B."

Second, explain the reasons, including the trade-offs: "Although A can launch faster, it will be complex to maintain later, while B, though two days slower, solves the problem once and for all."

Third, lay out the follow-up plan: "This means we need to reassess the timeline, and I'll sync with product to confirm whether the demand schedule can match."

There's no fancy technique in this approach; it's all skeleton.

But it's precisely this skeleton that lets the other person understand clearly, act with confidence, and know how you'll handle things if something goes wrong.

You're not persuading anyone; you're building trust that you have the big picture in mind and will take responsibility for the consequences of execution.

A new hire I was mentoring had his first cross-team communication. He sent a long Slack message with background information and solution analysis, and the other side replied with just one line:

So what do you want us to do?

He asked me if the other side was being too cold. I said no, it's that you finished talking, but you didn't make the matter clear.

Communication isn't about how much you say, but whether the other person knows what to do after listening.

Later he tried adding one sentence:

I suggest you change field X to asynchronous processing to avoid the current blocking issue. The details are in the attachment, and if it works for you, we can deploy tomorrow.

The result? It was settled in ten minutes and live half a day later.

Looking back, many workplace bottlenecks aren't because people are unwilling to cooperate, but because the expression lacks a choice, lacks trade-offs, lacks a next step.

For example, some people say a project is delayed but don't say how they want resources adjusted; some people say the architecture has hidden risks but don't say which point needs to change; some people even finish a long report and the listener sums it up with one sentence: "So what did we talk about today?"

It's not that they lack ability; it's that their expression is missing the most critical thing.

The most valuable expression is one that can take a complex matter and make it so clear that others can act immediately. Not just talking about the process, but daring to give a recommendation; not just being objective, but being able to state a choice; not just finishing and walking away, but having considered all the consequences.

That kind of communication is what a team truly needs.

Someone asked me: Can communication skills be trained?

The answer is of course yes. But it's not about training your tongue; it's about training how to connect your analytical thinking with actual execution.

You need to be clear about what you chose, what you gave up, and what impact it will have, then express it simply, concretely, and responsibly.

You don't need to be a great talker; you just need to be willing to walk all the way to the outcome.

Communication is not an add-on skill; it's a core tool in everyone's work. Those who can clearly explain their choices are more reliable; Those who can articulate trade-offs are more far-sighted; Those who can speak to outcomes are more trustworthy.

So next time someone asks you, "Which one do you recommend?" Don't step back, don't say "it depends." Say it. Which one you choose, why you know it's right, and that you're ready for the next step.