Tell me about a time you disagreed with a stakeholder

🎯 Leadership Principles Demonstrated

• Earn Trust - Data-driven approach, took concerns seriously
• Customer Obsession - 200M users, performance critical
• Dive Deep - Comprehensive benchmarking
• Have Backbone - Professional pushback with evidence
• Bias for Action - Finally investigated properly after 4 requests

📖 Full STAR Answer (2.5 minutes)

Situation (30 seconds)

At LINE, the entire Design team (based in Korea) persistently requested we use Lottie animations instead of APNG for the Event Effect feature (full-screen birthday celebrations for 200M users). They asked 4 times over 6 months in weekly stakeholder meetings.

Their arguments were compelling:

• Better visual quality from After Effects
• Simpler workflow (no After Effects → APNG conversion)
• Smaller file sizes (text-based JSON vs bitmap frames)
• Industry standard: "Facebook and Instagram use it!"

My initial response was "NO" - we were busy, didn't support Lottie yet, based on assumptions not data. But after the 4th request, I realized: I owed them proper investigation, not assumption-based rejections.

Task (25 seconds)

I needed to:

1. Thoroughly benchmark Lottie vs APNG with actual data
2. Make fair evaluation - maybe they were right!
3. Present findings clearly to non-technical stakeholders
4. Propose solution addressing their workflow concerns

The goal: Data-driven decision everyone could accept.

Action (85 seconds)

Investigation (Few Days)

I conducted comprehensive benchmarking:

Devices Tested:

• Emulator, high-spec, low-spec, LINE's top-used device models
• Real full-screen celebration animations (4 seconds)

Metrics Measured:

• File size, memory usage, CPU usage, battery impact, performance

Tools: Android Profiler with screenshots + annotations for non-technical stakeholders

The Shocking Results

Key Finding: Lottie consumed 8x more memory (40MB vs 5MB) and drained battery with continuous rendering.

I was hoping Lottie would work (would solve memory issues), but data showed otherwise.

Presentation to Stakeholders

I prepared:

1. Wiki page - all data documented
2. Android Profiler screenshots with annotations
3. Simple explanations - "40MB = loading 10 full-resolution photos continuously"

Not just "NO" but "HERE'S HOW WE MAKE APNG WORK FOR YOU":

Design team's worry: Creating multiple resolution APNG files

My solution:

• Showed high-end device APNG works well on low-end devices
• Proposed server-side scaling tool if multiple resolutions needed
• Simplified their workflow, met requirements, better performance

Result (30 seconds)

✅ Design team accepted the data-driven decision

✅ No one argued with comprehensive benchmarking

✅ Designers stopped requesting Lottie

✅ Relationship strengthened - they saw I took concerns seriously

✅ Future collaboration improved - they now ask for my technical input earlier in design phase

✅ Avoided 8x memory overhead (40MB → 5MB) for 200M users

✅ Workflow simplified with server-side scaling proposal

Key Learning: "Take stakeholder requests seriously, not assumptions-based rejections. Saying 'no' 3 times based on assumptions damaged credibility. Data-driven investigation built trust."

💡 Key Phrases to Practice

• "Design team asked 4 times over 6 months - I initially said NO based on assumptions, not data"
• "I realized I owed them proper investigation. Maybe they were right!"
• "Comprehensive benchmarking showed 8x memory difference - 40MB vs 5MB"
• "I was hoping Lottie would work, but data showed otherwise"
• "I didn't just say NO - I proposed workflow improvements for APNG"
• "Relationship strengthened - now they ask for my input earlier"

🎤 Delivery Tips

⏰ Time: Situation: 30s | Task: 25s | Action: 85s | Result: 30s

✅ DO:

• Emphasize "4 times over 6 months" - shows persistence
• Admit "I should have investigated sooner" - humility
• Highlight "8x memory difference" - dramatic
• Show you HOPED Lottie would work - openness
• Mention workflow improvements - not just rejection

❌ DON'T:

• Make designers sound unreasonable
• Sound like the hero
• Get too technical about Lottie rendering
• Forget relationship outcome

❓ Key Follow-Up Questions & Answers

Q1: "Why did it take 4 times to investigate?"

Answer:

"Honest answer: resource constraints and priorities. We were busy with other projects and didn't support Lottie yet, so I initially dismissed it.

But when we hit the 500MB memory issue with APNG, I realized I needed to properly investigate alternatives rather than just saying no. That's when I made time to do it right.

Looking back, I should have investigated sooner - it would have saved months of back-and-forth. This taught me: when stakeholders have persistent concerns, invest time to validate them properly, don't dismiss based on assumptions.

The principle: Stakeholder persistence often signals genuine pain points. Take them seriously enough to investigate thoroughly."

Q2: "What if Design team insisted on Lottie despite your data?"

Answer:

"I would have escalated with additional evidence:

1. Real user impact data - battery drain tests on actual devices
2. Performance on lowest-spec supported devices
3. Propose limited pilot with A/B testing to measure real impact

But the key is: I built enough trust through thorough investigation that they trusted my recommendation.

If fundamental disagreement remained, I'd:

• Commit to their decision professionally
• Document technical risks clearly
• Implement with extra monitoring

However, data-driven approach prevents most disagreements. When both sides see the same objective evidence, decisions become easier.

The principle: Build trust through thoroughness. Data creates shared reality. Respect final decision even if you disagree."

Q3: "How do you handle disagreements with non-technical stakeholders?"

Answer:

"Three principles:

1. Take Concerns Seriously

They usually have good reasons even if specific solution won't work. Design team genuinely wanted better workflow - that concern was valid.

2. Use Data and Simple Visualizations

• Android Profiler screenshots with annotations
• Simple explanations: "40MB = 10 photos loaded continuously"
• Visual graphs, not just numbers

3. Always Propose Alternatives

Don't just say "no" without solutions. I showed APNG could work well on low-end devices + proposed server-side scaling.

Example from this story:

Design team wanted Lottie → I showed data → proposed APNG + workflow improvements → they accepted.

The principle: Saying 'no' without solutions damages relationships. Data + alternatives = collaborative decision-making."

Q4: "How did this improve future collaboration?"

Answer:

"The thoroughness fundamentally changed our working relationship:

Before:

• Design team felt I wasn't listening (3 rejections)
• They had to push repeatedly
• Felt like adversarial relationship

After:

• They started asking for technical input EARLIER in design phase
• They trusted my technical judgment on future decisions
• Collaboration became proactive, not reactive

Specific Example:

Few months later, Design proposed complex animation transitions. Instead of designing fully then asking if possible, they:

• Shared early mockups
• Asked "Is this technically feasible?"
• I provided quick prototypes showing performance trade-offs
• We co-designed solution together

Result: Better designs that were both beautiful AND performant.

The principle: Taking stakeholder concerns seriously - even when you ultimately disagree - builds trust that improves ALL future collaboration."

📊 Story Strength: 9.5/10 ⭐⭐⭐⭐⭐

Why This Is Strong:

• ✅ Persistent stakeholder pressure (4 times over 6 months)
• ✅ Data-driven decision making
• ✅ Humility ("I should have investigated sooner")
• ✅ Comprehensive benchmarking across devices
• ✅ 8x dramatic difference
• ✅ Proposed alternatives (workflow improvements)
• ✅ Improved future collaboration

🎯 Practice Checklist

• [ ] Can explain "4 times over 6 months" naturally
• [ ] Can articulate "8x memory difference" clearly
• [ ] Can emphasize "I hoped it would work" (openness)
• [ ] Can describe workflow improvements proposed
• [ ] Can emphasize improved future collaboration
• [ ] Practiced 4 follow-up questions
• [ ] Timed at 2.5 minutes

📚 Full Version: /mnt/project/10_Design_Collaboration_Lottie_vs_APNG.md

Remember: Google values data-driven decision making AND collaborative stakeholder relationships. This story proves you can do both! 🚀