EN
/
RU
Current Theme: Dark
Blue
A methodology of performative productivity — creating the appearance of intense work while producing minimal real output. A blend of expectation-management strategy and activity-simulation tactics.
A person who practices Dojo techniques regularly, skillfully simulating productivity while conserving energy and avoiding overload. A Dojer skillfully balances minimal effort with maximum perceived activity.
A state in which a person is actively performing Dojo: delivering visible signals of work, maintaining motion, and sustaining the illusion of progress
A state in which a person is actively performing Dojo: delivering visible signals of work, maintaining motion, and sustaining the illusion of progress. "Please don’t interrupt — his Dojo is in progress."
A state of intentional productivity simulation; controlled and active Dojo performance.
To bring a task to a natural Dojo-compliant conclusion — it becomes irrelevant, outdated, cancelled, or quietly closed without real work. "The feature was endojoed after the business shifted priorities."
To inadequately perform Dojo, failing to sustain the appearance of progress or activity. "He tried to dojo the presentation but underdodjoed and got asked for real results."
To unintentionally spread Dojo behavior to others, causing a cascade. Occurs when Dojo becomes contagious inside a team. "The whole department got redojoed after that planning meeting."
To apply Dojo excessively — overcomplicating processes, adding layers of pseudo-activity, or generating more simulation than necessary. "She completely overdojoed the reporting flow."
The personal growth path of a Dojer: from discovering Dojo principles to mastering advanced forms of performative productivity.
A gathering where discussion replaces progress. Its purpose is not to make decisions but to simulate alignment, synchronization, and forward motion.
A work item designed or maintained primarily for visibility, motion, and progress signaling, rather than actual completion.
A time-boxed cycle dedicated to generating maximum visible activity with minimum actual output.
An informative-looking message crafted to signal progress without revealing — or requiring — any real progress.
A document or message created to summarize activity signals rather than actual results. Its primary function is to convert Dojo into written form, giving the illusion of structured progress.
A classification assigned to tasks based not on urgency or business value, but on their Dojo potential — the ability to generate continuous signals of progress without requiring actual completion.
A repeating cycle of activity in which Dojo reinforces more Dojo, creating sustained simulation with no natural endpoint.
A visible indicator of Dojo activity, such as typing, mouse movements, or file changes. It is used to sustain the appearance of progress.
A feature that exists in narrative before it exists in reality. A Dojo Feature is a declared capability that is discussed, planned, demonstrated, and referenced long before—or instead of—being fully implemented. Its primary value lies in roadmap presence, presentation slides, and stakeholder alignment rather than actual usage.
A requirement designed to exist, not to be fulfilled. A Dojo Requirement is a formally stated need that is intentionally vague, expandable, or internally flexible. It enables continuous discussion and reinterpretation while preventing definitive completion. Its purpose is to sustain process, not guide execution.
Criteria that validate agreement, not completion. Dojo Acceptance Criteria define when a feature or task is considered acceptable without requiring it to be complete, correct, or usable. They focus on alignment, acknowledgment, or presentation rather than measurable outcomes.
A UI element that never behaves as expected. Any attempt to fix its behavior inevitably breaks a different, previously working part of the system related to the checkbox. Over time, the checkbox becomes untouchable, surrounded by warnings, comments, and meetings, and is ultimately accepted as “working by design.”
An intentionally empty or near-empty document created solely to exist. Its purpose is not to be read or used, but to be referenced, linked, or mentioned if someone asks for documentation—under the implicit assumption that no one ever will.
A code commit created with a single purpose: to justify a future follow-up comment or commit that removes or reverts it. Typically minimal in scope—often a one-line change or a comment—it exists primarily to demonstrate activity rather than deliver lasting value.
A restructuring activity focused on reorganizing code, structure, or documentation without improving functionality, performance, or maintainability in any measurable way. Its primary purpose is to demonstrate technical diligence, reset discussions, and justify future work rather than to resolve underlying problems.
An urgent change applied to address a highly visible issue while leaving the root cause untouched. It restores surface stability long enough to satisfy stakeholders, with the implicit understanding that a more permanent fix will be discussed later — usually indefinitely.
A critical and dangerous condition where an entire team is in Dojo Mode simultaneously. This results in zero real productivity.