BOTTLENECK: Specifications, Raw Protocol, and the Anatomy of an On-Demand Physical Release

The 300-Page Illusion

The modern business publishing industry is built on a single structural inefficiency: justifying a 25-dollar cover price by padding a single ten-word insight into three hundred pages of narrative fluff.

Authors take an elementary operational axiom, wrap it in anecdotal case studies about Fortune 500 CEOs, add arbitrary 2x2 consulting matrices, and stretch the layout across twelve repetitive chapters. The result is pure waste (muda). Readers spend six hours processing filler to extract what could have been communicated in four seconds. In systems architecture and operations research, this is the exact definition of artificial Work in Progress (WIP)—accumulating non-value-added material simply to create the illusion of substance.

BOTTLENECK was engineered as an antidote to this pattern. It is an operational manifesto, a physical art piece, and a zero-WIP production experiment published in hardcover across 11 languages.

The Raw Protocol

Operational reality is uncompromising: system throughput is determined exclusively by the capacity of its single constraining node.

Optimizing any part of a pipeline outside the bottleneck yields zero global throughput increase. It merely inflates work-in-progress, congests intermediate buffers, increases lead time, and hides structural root causes under piles of unfinished inventory.

The protocol condenses operations research, queueing theory, and the Theory of Constraints (TOC) into three non-negotiable directives:

1. Find where the flow gets stuck.
2. Relieve that node.
3. Stop every other machine from flooding the floor with intermediate inventory.

Close the book. Go fix the process.

Global Translation Matrix

The manifesto is laid out across 11 language nodes, preserving precise manufacturing and operational terminology across industrial regions:

{
  "protocol": "BOTTLENECK",
  "version": "1.0",
  "author": "Bekzhan Ramazanov",
  "uri": "[https://ramazanov.cz/bottleneck](https://ramazanov.cz/bottleneck)",
  "isbn": "978-1-291-91491-7",
  "translations": {
    "en": {
      "language": "English",
      "statement": "Find where the flow gets stuck. Relieve that node. Stop every other machine from flooding the floor with intermediate inventory."
    },
    "de": {
      "language": "Deutsch",
      "statement": "Finde heraus, wo der Fluss stockt. Entlaste diesen Knoten. Hindere alle anderen Maschinen daran, die Halle mit Zwischenbeständen zu überfluten."
    },
    "fr": {
      "language": "Français",
      "statement": "Identifiez le point de blocage du flux. Déchargez ce nœud. Empêchez toutes les autres machines d'inonder l'atelier avec des stocks intermédiaires."
    },
    "es": {
      "language": "Español",
      "statement": "Encuentra dónde se atasca el flujo. Alivia ese nodo. Evita que las demás máquinas inunden la planta con inventario intermedio."
    },
    "it": {
      "language": "Italiano",
      "statement": "Trova il punto in cui il flusso si blocca. Alleggerisci quel nodo. Impedisci a tutte le altre macchine di inondare l'officina con scorte intermedie."
    },
    "pl": {
      "language": "Polski",
      "statement": "Znajdź miejsce, w którym przepływ się blokuje. Odciąż ten węzeł. Powstrzymaj pozostałe maszyny przed zalewaniem hali zapasami w toku."
    },
    "cz": {
      "language": "Čeština",
      "statement": "Najdi místo, kde se tok zasekává. Odlehči tomuto uzlu. Zabraň všem ostatním strojům zaplavovat halu rozpracovanou výrobou."
    },
    "ru": {
      "language": "Русский",
      "statement": "Найди, где застревает поток. Разгрузи этот узел. Запрети остальным машинам заваливать цех промежуточным хламом."
    },
    "zh": {
      "language": "简体中文",
      "statement": "找出流程停滞的瓶颈。为该节点减负。制止其他所有设备用在制品积压淹没车间。"
    },
    "ja": {
      "language": "日本語",
      "statement": "フローが滞っているボトルネックを特定せよ。その負荷を軽減せよ。他のすべての設備が仕掛品で現場を溢れさせるのを停止せよ。"
    },
    "ko": {
      "language": "한국어",
      "statement": "흐름이 막히는 병목 지점을 찾아라. 해당 노드의 부하를 해소하라. 다른 모든 장비가 현장을 재공품으로 채우지 못하도록 중단시켜라."
    }
  }
}

Physical Hardware Specifications

The publication deliberately uses physical presence to cut through digital noise. A browser tab is closed in milliseconds; a rigid hardcover on an executive’s desk remains an immovable physical reminder.

Trim Size:             6.00 x 9.00 in (US Trade / 152 x 229 mm)
Bleed Envelope:        6.25 x 9.25 in (158.75 x 234.95 mm)
Margins / Safety:      0.125 in bleed offset + 0.900 in interior safety
Cover Construction:    Case Wrap Hardcover (Rigid binder's board)
Cover Finish:          Ultra-matte lamination
Interior Paper Stock:  60# White Uncoated (approx. 90 g/m² offset)
Interior Color:        Standard Black & White (Single-pass 100% K ink)
Page Count:            Exactly 32 pages
List Price:            32.00 EUR (1.00 EUR per page)
ISBN:                  978-1-291-91491-7
Fulfillment Network:   Lulu POD -> Ingram Content Group -> Amazon Global

The Automated Build Pipeline

Traditional publishing relies on heavy desktop publishing suites, manual prepress operators, and weeks of editorial email chains. This project replaced that entire pipeline with an automated web-to-print workflow:

Source Layout: Written entirely in semantic HTML5 and vanilla CSS utilizing @page declarations and CSS Flexbox for geometric alignment.
Typography Engine: Built using variable OpenType weights of Inter for Latin text, Noto Sans for CJK coverage, and JetBrains Mono for technical metadata.
Prepress Compiling: Rendered directly through a headless browser environment to maintain strict pixel-to-millimeter fidelity and generate print-ready PDF assets with geometric bleed margins.
Distribution Automation: Pushed directly through API-driven print-on-demand networks, bypassing physical warehousing, inventory carrying costs, and upfront print runs.

Known Production Errata: The Font Engine Bottleneck

During the physical proof inspection in Prague, an unexpected typographic artifact was discovered: several lowercase t characters and bold uppercase R headers featured small dotted circle glyphs (◌, Unicode U+25CC) physically printed directly above them.

Root Cause Analysis

The bug occurred at the intersection of browser-based PDF generation and industrial print RIP (Raster Image Processor) hardware:

The Google Fonts build of Inter contains OpenType GPOS/GSUB lookup tables designed to position combining diacritical marks (e.g., carons and accents for Czech/Slovak orthography like ť and ř).
When exporting the print layout via headless browser printing, the underlying system engine subsetted the font while stripping the combining mark definitions, leaving the positional anchors exposed.
In screen viewers like Preview or Acrobat, these orphaned anchors are silently ignored. However, the industrial Adobe PDF Print Engine running at the print facility strictly follows ISO OpenType rendering rules. When encountering an open anchor with missing glyph associations, it automatically prints the universal fallback symbol for a broken mark: the dotted circle (◌).

Resolution Verdict

Rather than halting distribution, re-exporting vectorized curves, paying an additional proof fee, and introducing a two-week pipeline delay, the version was approved immediately.

In a book titled BOTTLENECK focused on eliminating intermediate delays and identifying operational constraints, a hardware printing defect produced by an unexpected software dependency is the ultimate proof of its own thesis. The artifact remains permanently etched into the first edition.

Acquisition & Distribution

Physical copies are produced strictly on demand. Zero warehouse stock exists anywhere in the world.

Amazon: Indexed worldwide under ISBN 978-1-291-91491-7 (US, UK, DE, FR, IT, ES, JP).
Direct Order: Available directly through the Lulu Bookstore with global shipping.