How Leaders Value Speed Over Cost: Real‑World IT Decision‑Making Lessons

-1-

The chairman's Mac broke, and the secretary sent it to the IT department. Network admin Z noticed a missing key and could only replace the keyboard, quoting a repair price of 2000. Z thought it was too expensive and tried to glue the key instead, raising doubts about the fix and emphasizing that the leader cared more about quick repair, time, and efficiency than the cost.

-2-

The general manager, who had experience in Western companies, asked the IT department to adopt a certain system. I assigned the task to the IT network team. After a week, I asked for progress. Z reported that they had set up a test environment full of bugs, contacted three vendors (two by phone with limited information), and noted a sales rule that revealing the company name during quotation could lock the price. One vendor, contacted via QQ, provided an online test environment but it still had many bugs and only allowed single‑user login, making testing impossible. I suggested purchasing an online paid course for the team to become familiar with the system before inviting a vendor to install a test environment at the branch. I asked, “Please tell me the key point.”

-3-

The general manager came to my office, patted my shoulder, and said his mother was ill, so he would be away and asked me to manage the ongoing IT projects. Noticing he was already wearing a windbreaker, I assumed he was about to leave. I decided to give a two‑minute report. My desk faced a large project progress board. I told him that MES2 would finish all functional development by October 20 and then move to production testing. I mentioned that we needed a colleague in Beijing to help the supplier conduct a test, as the cost of traveling from Zhenjiang was high. I reassured him that other projects were proceeding normally. The key message was to report the leader’s most concerned projects and assure him that everything else was under control.

-4-

There are two essential criteria for judging whether a task is done well. First, the task itself must be done well: high quality, no shortcuts, thorough completion, comprehensive consideration, and on‑time delivery without delay or excessive early completion. Second, interpersonal relationships must improve: the team should have better synergy, more mature processes, mutual recognition, and a willingness to cooperate again in the future. Mastering both leads to thriving in a company, though I personally prefer focusing on doing the work well.

-5-

Every workday is a form of training. Whether you are a slash‑youth, a freelancer, or any professional, reliability means you can complete any assigned task well, repeatedly. Work is about completing tasks one by one. Doing each task well is “training.” Learning micro‑economics teaches cost‑benefit analysis; studying structural thinking helps you present conclusions first; understanding DISC helps you communicate with D‑type leaders by focusing on what they care about; mastering PPT improves workplace reporting; and knowledge‑management builds core competitiveness.

-6-

After ten years of work, I feel like I’m constantly “interning.” Don’t settle for merely finishing tasks—the minimum you’re paid for. Aim to do them well to gain extra benefits. Don’t hide strategic laziness with tactical diligence. Being busy is like fighting with a stick on a battlefield; consider switching to cavalry for greater efficiency. The same eight‑hour workday can either result in slowly killing one “enemy” or charging forward and defeating many.

END.