β€Ή

Design review: answering pushback on cost and risk

Architect Β· Tech lead
0/8

🎬 In a design review the architect challenges the cost and risk of the proposed design, the tech lead explains the trade-off with data and a fallback, and they agree to validate on a small scope first.

Architect
Before we approve this, I want to understand why we need a queue in the middle.
Tech lead
Because the PLC drops data when the network blips. The queue is what makes the pipeline reliable.
Architect
That adds one more component to operate. What is the cost?
Tech lead
Two days of setup, and about ten minutes a week to operate it.
Architect
And if the queue itself goes down?
Tech lead
We keep the local cache as a fallback, so the line can still report for two hours.
Architect
Fine. I would rather validate it on one line before rolling it out.
Tech lead
Agreed. I will add it as an action item with the line three pilot next week.
All dialogues Status review: scope creep and the delay β€Ί

🎬 More dialogues in this deck

2 Status review: scope creep and the delay πŸ‘€ Project manager Γ— Business owner Β· 8 lines β€Ί

πŸ“š Keep going

πŸ’¬ 25 sentence patterns Every sentence from the dialogues, ready to reuse β€Ί 🎧 Listen and repeat Per-sentence playback Β· 0.8x slow Β· loop β€Ί

❓ FAQ

How should I practise this dialogue?

Play it once with continuous mode to get the rhythm, then switch to role play and take Architect or Tech lead, and finally compare with the standard lines.

What are the small notes under some lines for?

They explain why the line is phrased that way: tense, fixed collocations or tone. That is more useful than memorising the sentence alone.

Can I listen without reading?

Use continuous play: the current line is highlighted and scrolled into view, so you can follow the conversation hands-free.

Work English - scenario-based vocabulary and phrases Β· Sunzhongwei Β· More online tools

© 2026 sunzhongwei.com