Nguyễn Đức An

You have an idea, how to translate it to term and value for stakeholder ?

A useful way is to translate every idea into terms the stakeholder optimizes for.

Generic framework

Idea → Impact → Stakeholder Value

Instead of:

• “We should implement feature X.”

Translate to:

• “Feature X reduces onboarding time by 30%, which improves activation rate and reduces support tickets.”

---

By stakeholder

Stakeholder	They care about	Translate your idea into
PM	Business goals, roadmap, user outcomes	Revenue, retention, conversion, adoption, delivery date
Designer	User experience	Clarity, usability, accessibility, consistency, user friction
Engineer	Technical quality	Complexity, maintainability, reliability, scalability
Senior Engineer	Long-term system health	Technical debt, architecture, risk, operational cost
QA	Product correctness	Testability, coverage, defect prevention
DevOps/SRE	Operations	Availability, latency, observability, incident risk
Executive	Business impact	Cost, growth, strategic advantage, risk reduction

---

Translation template

My idea:

• We should use caching.

For PM

• Reduces page load time, improving user retention and conversion.

For Designer

• Creates a smoother user experience with fewer waiting states.

For Engineer

• Reduces database load and improves system performance.

For SRE

• Lowers infrastructure pressure and improves resilience during traffic spikes.

---

Mental model

When communicating, ask:

1. What problem does my idea solve?
2. What metric does that affect?
3. Which stakeholder owns that metric?
4. How would they describe success?

Then speak in their language.

Formula:

• Idea → Problem Solved → Impact → Stakeholder Goal

Example:

• “Implement request caching”
• → reduces repeated DB queries
• → lowers latency by 40%
• → improves user experience (Designer), conversion (PM), and infrastructure efficiency (SRE).

The skill is not just building a good idea; it’s expressing the same idea through different value systems.