AI problem
The category points you toward AI vendors, models, tools, and benchmarks.
Deconstruct → Observe → Transfer → Synthesize → Create
The world organizes knowledge into disciplines. Problems do not.
D.O.T.S. starts with a perceptual shift: do not let the label attached to a problem decide where you are allowed to look for answers. Deconstruct the label, observe the underlying structure, transfer only what genuinely travels, synthesize for the new context—then create something useful.
Origin line: “Collect Dots. Connect Dots. Create Something New.” That phrase remains part of the idea's lineage. The current public model makes the discipline inside the connection more explicit.
D.O.T.S. is especially useful inside Connect, where the Five Movements ask what relationships, perspectives, structures, and consequences may be missing. It can also be useful on its own for professional, analytical, systems, and cross-disciplinary problems.
The label narrows where you look. The structure expands where you can look.
The category points you toward AI vendors, models, tools, and benchmarks.
The problem becomes broader than the technology attached to it.
Now there are more places to look for principles that may transfer.
What kind of problem is this underneath the label?
Who else has faced a problem with the same underlying structure?
What principle actually travels—and where does the analogy stop?
What must change so the transferred insight fits this context?
Then: CREATE — turn the synthesis into a decision, system, practice, or possibility that fits the new context.
This is the public thesis, not a proprietary implementation manual. The point is disciplined transfer, not clever analogy. CREATE follows D.O.T.S.; it is the outcome stage rather than another letter in the acronym.
A tool developed to understand consumer preferences can become useful in a public planning problem when the deeper structure involves competing configurations, preferences, and tradeoffs.
Technology initiatives are not securities, but leaders still make choices about scarce capital, time horizons, concentration, risk, evidence, and rebalancing.
An AI pilot may look like a technology experiment. At scale, the deeper questions include mission, evidence, readiness, governance, trust, ownership, and the ability to keep deciding as conditions change.
Read the AI paper →A useful analogy is never permission to copy blindly. The discipline is to identify what transfers, what breaks, what must be adapted, and what does not belong.
Do not ask what field a tool belongs to. Ask what problem it can solve.
The book develops this way of seeing through stories, cases, principles, limits, and the deeper discipline of deconstructing, observing, transferring, synthesizing, and creating usefully. The first hard-copy proof is now in review.