Academic Paper

Design Science Research

"The Organizational Schema Theory: Test-Driven Business Design"

Dmitry Zharnikov, 2026 / ~7,800 words / DSR methodology (Hevner et al. 2004)

Introduces Organizational Schema Theory as a reverse-design TDD methodology where customer experience goals function as acceptance tests for business operations. The DSR artifact is the methodology itself, demonstrated through the Spectra Coffee reference implementation.

Prior Art

The framework builds on and differentiates from existing work in business process management, quality management, and software engineering:

Approach What It Does What Orgschema Adds
BPMN / Petri nets Model workflow sequences Multi-level validation hierarchy + perception traceability
ISO 9001 QMS Quality management system certification Continuous certification (commit hash, not annual audit)
IaC (Terraform, Ansible) Infrastructure as code Backward traceability to customer experience justification
Service blueprinting Map customer touchpoints Machine-readable, testable, version-controlled
TDD (software) Test-first development Applied to business operations, not just code
Toyota Production System Operational standardization Schema/data separation + digital-native specification
Viable System Model Recursive organizational cybernetics Specification-level detail + automated validation

The Convergence Thesis

Organizational Schema Theory and Spectral Brand Theory are two projections of a single system:

The interface between them is defined by an 8x6 activation matrix: which operational levels activate which SBT dimensions. The forward path (operations to perception) and reverse path (desired perception to required operations) are both formalized.

Neither framework is complete alone. SBT without orgschema is descriptive but not actionable. Orgschema without SBT is actionable but ungrounded.

Methodology

The paper follows Design Science Research methodology (Hevner et al. 2004, extended DSR). The artifact is the methodology itself, not the demo. Evaluation criteria:

Criterion Evidence
Feasibility Spectra Coffee: 26 YAML files, 6 products, full cascade, CI/CD passing
Novelty 10-entry prior art comparison. No existing work combines multi-level TDD + perception traceability + version control
Utility Fork, validate, certify operations from a commit hash
Generalizability Schema/data separation: methodology is publishable, parameters are competitive moat