Data, Users, APIs: The 3 Pillars of Effective Digital Transformation
Last updated: November 12, 2025 Read in fullscreen view
- 28 Oct 2023
The GOLDEN Rules of Software Engineering 47/593 - 18 Oct 2020
How to use the "Knowns" and "Unknowns" technique to manage assumptions 38/1089 - 14 Oct 2021
Stream Story - Low land stream or fast moving stream? 31/634 - 13 Oct 2021
What is Bug Convergence? Why is it important for User Acceptance Testing (UAT)? 28/759 - 08 Dec 2021
What Are The 4 Types of Maintenance Strategies? 25/1146 - 05 May 2021
TIGO Magic Scale - PoC tool for you to apply dichotomous thinking before submitting RFP 25/344 - 01 Oct 2020
Fail fast, learn faster with Agile methodology 24/1047 - 13 Dec 2020
Move fast, fail fast, fail-safe 22/325 - 14 Oct 2021
Advantages and Disadvantages of Time and Material Contract (T&M) 22/865 - 13 May 2022
IT Training and Development: The most effective options for upskilling IT staff 21/1146 - 02 Dec 2022
3 Levels of Quality in KANO Analysis Model 21/1120 - 18 Aug 2022
What are the consequences of poor requirements with software development projects? 20/274 - 06 Feb 2021
Why fail fast and learn fast? 20/451 - 12 Jan 2026
Why YouTube Content Is the New Resume: Building Trust and Expertise Even Without Views 20/33 - 01 Mar 2023
Bug Prioritization - What are the 5 levels of priority? 18/236 - 23 Sep 2021
INFOGRAPHIC: Top 9 Software Outsourcing Mistakes 17/439 - 11 Oct 2021
10 Myths About Low-End Project Management Software 16/340 - 10 Nov 2022
Poor Code Indicators and How to Improve Your Code? 16/231 - 11 Jul 2022
Cost benefit analysis for software development 16/726 - 19 Oct 2021
Is gold plating good or bad in project management? 15/816 - 19 Apr 2021
7 Most Common Time-Wasters For Software Development 14/556 - 08 Oct 2022
KPI - The New Leadership 12/603 - 31 Oct 2021
Tips to Fail Fast With Outsourcing 12/392 - 08 Jan 2024
Ask Experts: Explicitation/Implicitation and Elicitation; two commonly used but barely unraveled concepts 12/327 - 12 May 2025
Tech for Non-Techies: How to Understand IT Without Writing a Single Line of Code 12/48 - 10 Dec 2023
Pain points of User Acceptance Testing (UAT) 11/452 - 28 Dec 2021
8 types of pricing models in software development outsourcing 10/437 - 17 Feb 2022
Prioritizing Software Requirements with Kano Analysis 10/304 - 05 Jan 2024
Easy ASANA tips & tricks for you and your team 10/201 - 11 Jan 2024
What are the Benefits and Limitations of Augmented Intelligence? 10/478 - 12 Mar 2024
How do you create FOMO in software prospects? 9/167 - 03 Jul 2022
Occam’s Razor and the Art of Software Design 9/505 - 01 Mar 2024
(AI) Artificial Intelligence Terms Every Beginner Should Know 7/303 - 03 Nov 2022
Questions and answers about Kano Model 7/864 - 01 Oct 2020
Handling tight project deadlines as a business analyst 7/331 - 06 Nov 2019
How to Access Software Project Size? 6/249 - 14 Mar 2024
Why should you opt for software localization from a professional agency? 6/140 - 26 Dec 2023
Improving Meeting Effectiveness Through the Six Thinking Hats 6/254 - 12 Apr 2025
How to Ask Powerful Questions Like Socrates 5/34 - 14 Feb 2024
Early BA Engagement: “Earning” Pre-Project Work 3/156
“Near the Data, Close to the User, Connected by API”
A modern reflection on the ancient wisdom of “Nhất cận giang, nhì cận thị, tam cận lộ”
🧾The Old Wisdom, Reimagined
In traditional Vietnamese and Chinese culture, people used to say:
“Nhất cận giang, nhì cận thị, tam cận lộ”
(First, live near the river. Second, near the market. Third, near the road.)
It was ancient real-estate wisdom — a way to choose prosperous land. Living near a river meant life and abundance.
Near a market meant trade and opportunity. Near a road meant connection and growth.
Now, in the digital age, this timeless truth still applies — but not to land, rather to software.
1. First, Near the Data — the River of Digital Life
In the digital world, data is water. Without data, software is a dry field — no growth, no harvest.
The first rule of building software for digital transformation is simple:
“Where does the data flow from, and where does it flow to?”
A successful system must connect directly to real data sources — from customer behavior, operations, transactions, or sensors. The closer your software is to the stream of data, the more alive it becomes.
Without data, it’s just a stagnant pond — clean on the surface, empty underneath.
2. Second, Close to the User — the Digital Marketplace
Just as ancient merchants thrived by setting up shop near busy markets, modern software thrives by staying close to its users.
You can’t build software in isolation and expect people to adapt. You must go to the “market” — where real users click, complain, and comment. Only then can you see what truly matters to them.
The best digital products are born from constant feedback loops. They evolve with users, just like merchants refine their goods to keep loyal customers coming back.
3. Third, Connected by API — the Digital Highway
In the past, being near a road meant easier trade and travel. Today, being “near the API” means your software
can integrate, expand, and connect within the digital ecosystem.
Without APIs, your app becomes an isolated house in the forest — no path in, no path out.
In digital transformation, success doesn’t come from standalone apps but from networks of systems that talk to each other. APIs are the highways of the digital economy — they connect you to partners, platforms, and possibilities.
Conclusion
Digital transformation isn’t about building another piece of software. It’s about choosing the right digital location — where data flows, users interact, and systems connect.
So remember the modern version of our ancestors’ wisdom:
- Near the Data — to stay alive.
- Close to the User — to stay relevant.
- Connected by API — to stay scalable.
Companies that master all three will thrive in the digital age — just like the prosperous riverside towns of old, where every stream, road, and market came together to create lasting prosperity.










Link copied!
Recently Updated News