The CTO wants a list

Shadow Li Na first. She's the steady senior engineer; her questions are short and practical: "Whatever slows you down." Then take Eric's part. He's anxious at the start and more confident as the list grows. Stress the numbers that make his case: "forty minutes", "two hours, twenty people".

1. EricLi Na, did you get the email from the new CTO?
2. Li NaThe one asking every engineer to send her a list? Yes. What are you going to write?
3. EricI don't know. I'm worried it's a trap. New bosses love to replace everything.
4. Li NaShe's been here three days. She's trying to get up to speed, not replace us.
5. EricThen why bring someone on board from outside? Why not promote someone here in Shenzhen?
6. Li NaBecause the board wants us to ship faster, and she's done that before.
7. EricOkay. So what goes on the list?
8. Li NaWhatever slows you down. What would you fix if you had a free month?
9. EricThe build system. It takes forty minutes to test one small change.
10. Li NaForty minutes? Put that at the top.
11. EricAnd the legacy code in the thermostat app. Nobody who wrote it still works here.
12. Li NaGood. That's two. Anything that isn't technical?
13. EricThe weekly status meeting. Two hours, twenty people, and three of them talk.
14. Li NaI'm not sure you should say that to the CTO in her first week.
15. EricYou told me to be honest.
16. Li NaHonest, yes. Maybe say the meeting could be shorter, instead of counting who talks.
17. EricFine. Three points, polite version. If she fixes the build system, I'll forgive her anything.
18. Li NaWrite that sentence, too. People like knowing what would make you happy.