IT Projects: Why We Recommend Diagnosing Before Building Systems

Ask About the Business First, Then the Technology

The value of IT modernization ultimately shows up in the business: one less round of duplicate data entry, anomalies caught earlier, and real numbers that managers can actually see. If you start by comparing system features, it's easy to carry existing processes into the new system as-is — no efficiency gain, just a new interface.

What We Look at During the Diagnosis Phase

• Who maintains each existing system and dataset, and which source of truth governs the master data
• Which steps still rely on spreadsheets, WeChat messages, or word of mouth
• The metrics that truly need to be measured, and why they can't be obtained today
• On-site conditions, network constraints, and how frontline staff actually work

Build in Phases

The output of a diagnosis isn't a thick report — it's a verifiable roadmap: Phase 1 fixes the single most painful step and closes the data loop; Phase 2 then connects upstream and downstream. Each phase has clear acceptance criteria, so investment can be validated and priorities adjusted as needed.

Reuse what you can, phase what you can. Let the system grow with the business instead of betting everything on one shot.