This is Hamamoto from TIMEWELL.
When DX initiatives come up in internal discussions, terms like "PoC," "agile," and "DevOps" start flying around meeting rooms, and it can be hard to keep up. DX isn't fundamentally about deploying tools — it's about transforming how the business operates. But without understanding the terminology, it's difficult to participate in those discussions.
This glossary covers 40 essential terms for anyone involved in DX projects, organized so that non-technical readers can build working familiarity with each concept.
Contents
- DX and Transformation Fundamentals
- AI and Data
- Development Methods and Processes
- Infrastructure and Cloud
- Organization and People
- Summary
Looking for AI training and consulting?
Learn about WARP training programs and consulting services in our materials.
DX and Transformation Fundamentals
DX (Digital Transformation) — Scanning paper to PDF is not DX. DX means redesigning business processes, business models, and organizational culture with digital technology as the foundation. Japan's Ministry of Economy, Trade and Industry raised the "2025 Cliff" issue in 2018, accelerating corporate initiatives, but as of 2026, companies that have reached their DX goals remain a minority.
Digitization — Converting analog information into digital data. Scanning documents to PDF, entering handwritten daily reports into Excel. This is the first step toward DX, but digitization alone does not constitute DX.
Digitalization — Using digital technology to improve and automate business processes. Replacing stamp-based approvals with workflow systems, migrating paper order forms to an e-commerce platform. This is the step after digitization.
The 2025 Cliff — A problem flagged in the Ministry of Economy, Trade and Industry's 2018 DX report. The analysis projected that failure to modernize aging core systems (legacy systems) could generate economic losses of up to ¥12 trillion annually after 2025. As of 2026, many companies are still mid-transition.
Legacy System — An older information system that has been in use for many years. Mainframes and COBOL-based systems are the classic examples, but ERPs implemented more than a decade ago also qualify. The challenge: critical business operations depend on these systems, making migration difficult.
PoC (Proof of Concept) — You've probably been in a meeting where someone said "let's start with a PoC." It means a small-scale test to verify whether a new technology or idea is feasible before full implementation. A necessary step — but "PoC fatigue" has become a serious problem where organizations run repeated proofs of concept without ever reaching deployment. If verification has become an end in itself, that's a sign to stop and ask what's blocking the next step.
RPA (Robotic Process Automation) — Software robots that handle repetitive rule-based tasks — data entry, email sorting, form generation — 24 hours a day without complaint. Many companies use RPA as an entry point into DX, because it produces visible results quickly and builds organizational confidence in automation.
IoT (Internet of Things) — Connecting everyday objects — appliances, factory equipment, vehicles — to the internet to collect and use data. Sensor monitoring of factory equipment to predict failures, collecting soil data from agricultural fields to automate irrigation. The value is in using the data, not just collecting it.
AI and Data
AI (Artificial Intelligence) — The broad category of technology enabling computers to perform tasks that require human-like judgment and reasoning. Applications include image recognition, voice recognition, text generation, and demand forecasting. In DX, AI is a tool — deploying AI is not the goal in itself.
Machine Learning (ML) — Technology that allows computers to automatically learn patterns from data. Feed in large volumes of sales data, and the system builds a model that forecasts future demand. Unlike conventional programming where a programmer writes each rule explicitly, machine learning finds the rules in the data.
Deep Learning — A subset of machine learning that uses multi-layered neural networks modeled on the structure of the human brain. It has produced dramatic accuracy improvements in image recognition and natural language processing, driving the recent AI boom.
Natural Language Processing (NLP) — Technology that enables computers to understand and generate human language. Used in chatbots, translation, and automatic meeting summarization. ChatGPT and Claude are both products of NLP technology.
Computer Vision — Technology that enables computers to understand the content of images and video. Used in factory defect detection, facial recognition, and obstacle identification in autonomous vehicles.
Big Data — More than just large volumes of data — the value is in how it's used. Social media posts, IoT sensor logs, and POS sales data become useful when analyzed to produce insights for business decisions. Data stored and never analyzed is a cost, not an asset.
Data Lake — Large-scale storage that holds both structured data (tables) and unstructured data (text, images) in its original form without transformation. Serves as a "reservoir" for accumulating data before you know exactly what analysis you'll want to run.
ETL (Extract, Transform, Load) — The process of extracting data from source systems, transforming and cleaning it, and loading it into a target system. Used when integrating data scattered across multiple systems.
BI Tool (Business Intelligence Tool) — Software that visualizes accumulated data in charts and dashboards for business decision-making. Tableau, Power BI, and Looker are leading examples. Usable without deep data analysis expertise.
You might think development methodology doesn't concern you if you're not an engineer. But understanding agile and DevOps is necessary to understand how DX projects are structured — and these terms come up constantly in vendor conversations.
Development Methods and Processes
Agile — The opposite of the traditional waterfall approach of "design everything before building anything." Agile runs short 1-4 week cycles of planning, development, and testing, building toward completion incrementally. Because it adapts to changing requirements, agile has become the dominant approach for DX projects.
Scrum — One specific agile framework. Defined roles — Product Owner, Scrum Master, development team — work through repeated development cycles called "sprints" of 1-4 weeks.
Sprint — One development cycle in Scrum. In a two-week sprint, the team might complete "login feature implementation"; the next two weeks they tackle "dashboard functionality." Work is delivered in these incremental units.
DevOps — A culture and practice that integrates software development (Development) and operations (Operations), enabling faster and more stable delivery from code to production. As of 2026, "AIOps" — using AI to automate DevOps processes — is becoming common.
CI/CD (Continuous Integration / Continuous Delivery) — The practice of frequently integrating code changes (CI) and automatically testing and deploying them to production (CD). Automating manual release processes enables faster release cycles and earlier bug detection.
API (Application Programming Interface) — Think of it as an ordering counter at a restaurant. The customer (Software A) places an order at the counter (API), and the kitchen (Software B) returns the dish (data). Weather apps can access meteorological data. E-commerce sites can process payments. All of this works because APIs connect them. In DX, you will always need to integrate multiple systems — understanding APIs is a practical necessity.
One practical note: selecting a tool that doesn't expose an API means you'll be stuck if you later want to connect it to other systems. Asking "does this have an API, and what can it access?" during tool selection is a small habit with significant long-term consequences.
Microservices — An architectural approach that builds one large system as a collection of independent smaller services. Separating "user management," "order processing," and "inventory management" means changes to one component don't ripple through the entire system.
Low-Code / No-Code — Tools and methods that enable application development with minimal or no programming knowledge. The foundation for "citizen development" — where frontline business staff build their own tools without IT department involvement.
Now infrastructure — more technical territory, but the distinction between cloud and on-premises directly affects business decisions, so the concepts are worth understanding.
Infrastructure and Cloud
Cloud — Using IT resources — servers, storage, software — via the internet, paying as you go, rather than purchasing and managing physical servers. AWS, Azure, and GCP are the major providers. Lower upfront costs and the ability to scale as needed are the primary advantages.
Cloud Native — Systems and applications designed from the ground up for cloud environments, using containers, microservices, and auto-scaling to maximize cloud advantages.
SaaS / PaaS / IaaS — Three categories of cloud service delivery. SaaS (software delivered as a service), PaaS (development platform delivered as a service), IaaS (infrastructure delivered as a service) — moving from SaaS to IaaS increases user flexibility but also management responsibility. The "SaaS and Cloud Glossary" covers these in detail.
Container — Think of it as a moving box. Containers package an application together with everything it needs to run. Move the box to any environment and it works the same way, eliminating the classic problem of "works on my machine but not in production." Docker is the standard tool.
Kubernetes (K8s) — A system for efficiently managing large numbers of containers — automating placement, load balancing, and automatic recovery from failures. Originally from Google, it has become the de facto standard for cloud-native development.
Edge Computing — "Process locally, report centrally." Rather than sending all data to the cloud for processing, edge computing handles data at or near its source — factory equipment, retail terminals. Particularly valuable where millisecond response times matter, as in autonomous vehicles.
Organization and People
DX Talent — DX talent is not only "people who can program." It includes people who can map a path from business problems to digital solutions, people who can bridge between departments, and leaders who can communicate strategy to executive teams. The shortage of this talent is severe, and internal development is urgent. TIMEWELL's AI consulting service WARP designs DX talent development programs tailored to each company's specific gaps.
To be direct: the definition of "DX talent" varies significantly from company to company. Job postings that say "DX talent wanted" often don't communicate what they actually need. The realistic starting point is defining the specific roles your organization requires.
CoE (Center of Excellence) — An internal specialist team responsible for driving DX and AI adoption. They consolidate knowledge, spread best practices, and support individual departments. In large enterprises, these are often structured as "DX Promotion Office" or "AI Adoption Division."
Digital Literacy — The foundational ability to understand digital technologies and data, and apply them to business work. Not about being able to program — about being able to judge "what digital tools could address this business problem."
Reskilling — Learning new skills for a different role or function. In the DX context, primarily refers to acquiring digital skills. Government support programs have expanded, with subsidy eligibility broadened further in the 2026 fiscal year.
Change Management — The practice of planning and managing organizational transformation to minimize resistance and ensure adoption. Because DX involves changes in work practices and organizational culture — not just technology — change management capability often determines whether a project succeeds or stalls.
Summary
AI and DX terminology mixes technical and organizational concepts, which can be confusing. Organizing it around three questions helps: What needs to change? How will it change? Who will change it?
Key points to take away:
- DX is not IT deployment — it is the transformation of business models and organizational culture
- PoC to validate at small scale, agile to build incrementally — this is the foundational DX approach
- RPA, AI, and IoT are means to DX, not the end goal
- Cloud-native and microservices are the mainstream architecture for modern systems
- Technology alone is insufficient — talent development (reskilling) and change management are both necessary
TIMEWELL's AI consulting service WARP supports DX advancement from AI strategy development through DX talent development. If "I understand the terms now but don't know where to start for my organization" describes your situation, see the WARP training program overview for both executive-level and frontline approaches.
