[{"data":1,"prerenderedAt":813},["ShallowReactive",2],{"article-alternates":3,"article-\u002Fde\u002Flifestyle\u002Fgruender-kalender-kontext-wechsel-kosten-zeitblockierung":13},{"i18nKey":4,"paths":5},"lifestyle-002-2026-06",{"de":6,"en":7,"es":8,"fr":9,"it":10,"ru":11,"tr":12},"\u002Fde\u002Flifestyle\u002Fgruender-kalender-kontext-wechsel-kosten-zeitblockierung","\u002Fen\u002Flifestyle\u002Ffounder-calendar-context-switching-cost-time-blocking-discipline","\u002Fes\u002Flifestyle\u002Fcalendario-del-fundador-costo-del-cambio-de-contexto-y-disciplina-de-bloqueo-de-tiempo","\u002Ffr\u002Flifestyle\u002Fcalendrier-fondateur-cout-commutation-contexte-discipline-timeblocking","\u002Fit\u002Flifestyle\u002Fcalendario-fondatore-context-switching-time-block","\u002Fru\u002Flifestyle\u002Fkalendar-osnovatelja-kontekstnoye-perekljucheniye-i-vremennye-bloki","\u002Ftr\u002Flifestyle\u002Ffounder-calendar-baglam-anahtarlama-maliyeti-ve-time-block-disiplini",{"_path":6,"_dir":14,"_draft":15,"_partial":15,"_locale":16,"title":17,"description":18,"publishedAt":19,"modifiedAt":19,"category":14,"i18nKey":4,"tags":20,"readingTime":26,"author":27,"body":28,"_type":807,"_id":808,"_source":809,"_file":810,"_stem":811,"_extension":812},"lifestyle",false,"","Gründer-Kalender: Kontextwechsel-Kosten und Zeitblock-Disziplin","4-Stunden-Deep-Work-Blöcke, asynchrone Response-Fenster und Customer-Meeting-Cadence: Den Kalender zur operativen Ressource umgestalten.","2026-06-17",[21,22,23,24,25],"deep-work","time-blocking","founder-productivity","async-first","calendar-management",9,"Roibase",{"type":29,"children":30,"toc":791},"root",[31,39,46,51,67,80,87,92,117,129,135,146,151,169,174,180,192,197,302,307,312,318,323,331,354,362,375,383,401,409,417,425,443,448,491,497,502,520,525,531,536,541,575,580,586,591,634,639,649,655,660,777,782,786],{"type":32,"tag":33,"props":34,"children":35},"element","p",{},[36],{"type":37,"value":38},"text","Kalenderführung ist für Gründer lebenswichtig — aber die meisten sehen darin nur ein \"freie Slots finden\"-Problem. Das eigentliche Problem ist anders: Wie oft wechselst du täglich den Kontext? Von einem Meeting zum Code Review, dann zur Kundenmail, anschließend zum strategischen Dokument — die kognitive Last steigt exponentiell. Die Forschung zeigt: Nach einem Aufgabenwechsel dauert es 23 Minuten, die Aufmerksamkeit wiederherzustellen (UC Irvine, 2021). 8 Kontextwechsel pro Tag = 3 Stunden Verlust. Das einzige Kapital eines Gründers ist Aufmerksamkeit — der Kalender ist die Architektur dieser Aufmerksamkeitsökonomie.",{"type":32,"tag":40,"props":41,"children":43},"h2",{"id":42},"kontextwechsel-kosten-der-unmessbare-schaden",[44],{"type":37,"value":45},"Kontextwechsel-Kosten: Der unmessbare Schaden",{"type":32,"tag":33,"props":47,"children":48},{},[49],{"type":37,"value":50},"Siehst du im Kalender zwei aufeinanderfolgende Meetings verschiedenen Typs (z.B. 10:00 Performance Review, 11:00 Product Roadmap), zahlst du einen Preis: Der Nachwirkungseffekt des vorigen Kontexts wirkt noch nach, während du den neuen laden willst. Dieser \"task-switching cost\" ist in der Literatur gut erforscht — aber Gründer-Kalender werden meist wie ein \"Tetris-Spiel\" gefüllt, ohne diese Kosten zu berücksichtigen.",{"type":32,"tag":33,"props":52,"children":53},{},[54,56,65],{"type":37,"value":55},"Konkreter Effekt: Morgens 09:00 Kundengespräch, 10:30 Team Stand-up, 11:00 Budget Review — bei jedem Wechsel wird der Kurzspeicher gelöscht. Tiefgründige Arbeit (z.B. einen neuen ",{"type":32,"tag":57,"props":58,"children":62},"a",{"href":59,"rel":60},"https:\u002F\u002Fwww.roibase.com.tr\u002Fde\u002Fbranding",[61],"nofollow",[63],{"type":37,"value":64},"Markenstrategie",{"type":37,"value":66},"-Entwurf) bleibt undone — weil die restlichen Slots bereits mit flacher Arbeit (Mail, Slack, Dokument-Tweaks) belegt sind.",{"type":32,"tag":33,"props":68,"children":69},{},[70,72,78],{"type":37,"value":71},"Die Lösung: Time-Blocking — aber nicht generische Blöcke, sondern ",{"type":32,"tag":73,"props":74,"children":75},"strong",{},[76],{"type":37,"value":77},"kontexthomogene Blöcke",{"type":37,"value":79},". Innerhalb eines Tages nur \"Kundengespräche\" oder nur \"interne strategische Dokumentation\" oder nur \"Code Review + Engineering Meetings\" reservieren. So startest du um 14:00 im reinen \"Kunden-Modus\" und bleibst bis 17:00 in demselben Denkrahmen.",{"type":32,"tag":81,"props":82,"children":84},"h3",{"id":83},"praktische-regel-4-stunden-deep-work-block",[85],{"type":37,"value":86},"Praktische Regel: 4-Stunden-Deep-Work-Block",{"type":32,"tag":33,"props":88,"children":89},{},[90],{"type":37,"value":91},"Roibases 8 Jahre Erfahrung zeigen: Ein Gründer braucht wöchentlich mindestens 2 × 4-Stunden-Deep-Work-Blöcke ohne Unterbrechung. Diese Blöcke sollten in Zeiten wie 08:00-12:00 oder 13:00-17:00 liegen. Während dieser Zeit:",{"type":32,"tag":93,"props":94,"children":95},"ul",{},[96,102,107,112],{"type":32,"tag":97,"props":98,"children":99},"li",{},[100],{"type":37,"value":101},"Slack geschlossen (DND-Modus an)",{"type":32,"tag":97,"props":103,"children":104},{},[105],{"type":37,"value":106},"Keine Meetings (Calendar-Block als \"busy\")",{"type":32,"tag":97,"props":108,"children":109},{},[110],{"type":37,"value":111},"Keine Telefonanrufe",{"type":32,"tag":97,"props":113,"children":114},{},[115],{"type":37,"value":116},"Mail nur in Batch (z.B. einmalig um 12:00)",{"type":32,"tag":33,"props":118,"children":119},{},[120,122,127],{"type":37,"value":121},"4 Stunden ununterbrochene Arbeit liegt unter der \"professional peak performance\"-Schwelle, die Cal Newport in \"Deep Work\" nennt (er empfiehlt 4-5 Stunden). Aber in der Realität eines Gründers ist selbst 4 Stunden eine Disziplin-Leistung. Was macht man in diesen Blöcken? Strategische Dokumente (Jahresplanung, neues Geschäftsmodell, technische Architektur-Skizzen), komplexes Code-Schreiben, neues Produkt-Konzept-Design — also ",{"type":32,"tag":73,"props":123,"children":124},{},[125],{"type":37,"value":126},"Output, der nicht aufgeschoben werden kann, aber auch nicht unterbrechbar ist",{"type":37,"value":128},".",{"type":32,"tag":40,"props":130,"children":132},{"id":131},"customer-meeting-cadence-batch-processing-prinzip",[133],{"type":37,"value":134},"Customer-Meeting-Cadence: Batch-Processing-Prinzip",{"type":32,"tag":33,"props":136,"children":137},{},[138,140,145],{"type":37,"value":139},"Die zweite große Entropie-Quelle in Gründer-Kalendern sind Kundengespräche. Wenn täglich 3-4 Meetings zu unterschiedlichen Zeiten eingebucht sind, wird der ganze Tag reaktiv. Alternative: ",{"type":32,"tag":73,"props":141,"children":142},{},[143],{"type":37,"value":144},"Cadence-basiertes Batching",{"type":37,"value":128},{"type":32,"tag":33,"props":147,"children":148},{},[149],{"type":37,"value":150},"Praktische Umsetzung: 2 Wochentage (z.B. Dienstag und Donnerstag) komplett Kundengesprächen widmen. Diese Tage sind von 09:00-17:00 als aufeinanderfolgende Slots strukturiert (jedes Gespräch 45 Minuten, 15 Minuten Puffer dazwischen). Dadurch:",{"type":32,"tag":93,"props":152,"children":153},{},[154,159,164],{"type":32,"tag":97,"props":155,"children":156},{},[157],{"type":37,"value":158},"Montag, Mittwoch, Freitag bleiben komplett intern",{"type":32,"tag":97,"props":160,"children":161},{},[162],{"type":37,"value":163},"Customer-Erwartung wird klar: \"Roibase-Gespräche sind Di\u002FDo\"",{"type":32,"tag":97,"props":165,"children":166},{},[167],{"type":37,"value":168},"Der Gründer schaltet jeden Dienstag früh in \"Kunden-Modus\" und schaltet erst abends aus — kein Kontextwechsel",{"type":32,"tag":33,"props":170,"children":171},{},[172],{"type":37,"value":173},"Der zweite Vorteil des Batch-Processing: Du kannst Muster aus aufeinanderfolgenden Gesprächen sofort erkennen. Wenn 3 verschiedene Kunden am selben Tag \"First-Party-Data-Integration\" erwähnen, schreibst du abends ein strategisches Dokument dazu. Wären die Gespräche über die Woche verteilt, würde dieses Pattern verloren gehen.",{"type":32,"tag":81,"props":175,"children":177},{"id":176},"async-response-window-mail-und-slack-batch-check",[178],{"type":37,"value":179},"Async Response Window: Mail und Slack Batch Check",{"type":32,"tag":33,"props":181,"children":182},{},[183,185,190],{"type":37,"value":184},"Die meisten Gründer versuchen, tagsüber auf Slack und Mail zu antworten, um \"reaktionsschnell\" zu wirken. Das ist nicht reaktionsschnell, sondern ",{"type":32,"tag":73,"props":186,"children":187},{},[188],{"type":37,"value":189},"reaktiv",{"type":37,"value":191},". Der Unterschied: Reaktionsschnell heißt, innerhalb eines Fensters zu antworten (z.B. 4 Stunden). Reaktiv heißt, bei jeder Benachrichtigung zu springen.",{"type":32,"tag":33,"props":193,"children":194},{},[195],{"type":37,"value":196},"Bei Roibase funktioniert das Async Response Window so:",{"type":32,"tag":198,"props":199,"children":200},"table",{},[201,225],{"type":32,"tag":202,"props":203,"children":204},"thead",{},[205],{"type":32,"tag":206,"props":207,"children":208},"tr",{},[209,215,220],{"type":32,"tag":210,"props":211,"children":212},"th",{},[213],{"type":37,"value":214},"Kanal",{"type":32,"tag":210,"props":216,"children":217},{},[218],{"type":37,"value":219},"Response Window",{"type":32,"tag":210,"props":221,"children":222},{},[223],{"type":37,"value":224},"Batch-Check-Zeit",{"type":32,"tag":226,"props":227,"children":228},"tbody",{},[229,248,266,284],{"type":32,"tag":206,"props":230,"children":231},{},[232,238,243],{"type":32,"tag":233,"props":234,"children":235},"td",{},[236],{"type":37,"value":237},"Slack (nicht urgent)",{"type":32,"tag":233,"props":239,"children":240},{},[241],{"type":37,"value":242},"4 Stunden",{"type":32,"tag":233,"props":244,"children":245},{},[246],{"type":37,"value":247},"09:00, 13:00, 17:00",{"type":32,"tag":206,"props":249,"children":250},{},[251,256,261],{"type":32,"tag":233,"props":252,"children":253},{},[254],{"type":37,"value":255},"Mail",{"type":32,"tag":233,"props":257,"children":258},{},[259],{"type":37,"value":260},"24 Stunden",{"type":32,"tag":233,"props":262,"children":263},{},[264],{"type":37,"value":265},"12:00, 17:30",{"type":32,"tag":206,"props":267,"children":268},{},[269,274,279],{"type":32,"tag":233,"props":270,"children":271},{},[272],{"type":37,"value":273},"Linear Task-Mention",{"type":32,"tag":233,"props":275,"children":276},{},[277],{"type":37,"value":278},"8 Stunden",{"type":32,"tag":233,"props":280,"children":281},{},[282],{"type":37,"value":283},"10:00, 16:00",{"type":32,"tag":206,"props":285,"children":286},{},[287,292,297],{"type":32,"tag":233,"props":288,"children":289},{},[290],{"type":37,"value":291},"Notfall (Anruf)",{"type":32,"tag":233,"props":293,"children":294},{},[295],{"type":37,"value":296},"Sofort",{"type":32,"tag":233,"props":298,"children":299},{},[300],{"type":37,"value":301},"Immer verfügbar",{"type":32,"tag":33,"props":303,"children":304},{},[305],{"type":37,"value":306},"In diesem Setup weiß das Team: Wenn ihr Slack-Nachrichten sendet, antwortet der Gründer in 4 Stunden. Das reicht — denn bei echtem Notfall ruft man an. Für Mail ist ein 24-Stunden-Fenster auch für externe Stakeholder (Kunden, Partner) akzeptabel. Intern kritische Themen laufen über Linear mit @ mentions, dort ist auch ein 8-Stunden-Fenster üblich.",{"type":32,"tag":33,"props":308,"children":309},{},[310],{"type":37,"value":311},"Ergebnis: Der Gründer öffnet Slack nur 3× täglich. Bei diesen 3 Öffnungen liest er alle Nachrichten im Batch, priorisiert und antwortet. Damit vermeidet er 15 Slack-Checks pro Tag.",{"type":32,"tag":40,"props":313,"children":315},{"id":314},"time-block-disziplin-template-wochenstruktur",[316],{"type":37,"value":317},"Time-Block-Disziplin: Template-Wochenstruktur",{"type":32,"tag":33,"props":319,"children":320},{},[321],{"type":37,"value":322},"Der Erfolg von Time-Blocking liegt in der Konsistenz — nicht jede Woche eine neue Strategie, sondern ein Template etablieren und ihm treu bleiben. Roibases Gründer-Kalender-Template sieht so aus:",{"type":32,"tag":33,"props":324,"children":325},{},[326],{"type":32,"tag":73,"props":327,"children":328},{},[329],{"type":37,"value":330},"Montag:",{"type":32,"tag":93,"props":332,"children":333},{},[334,339,344,349],{"type":32,"tag":97,"props":335,"children":336},{},[337],{"type":37,"value":338},"08:00-12:00: Deep Work (strategische Planung oder komplexe Software)",{"type":32,"tag":97,"props":340,"children":341},{},[342],{"type":37,"value":343},"13:00-14:00: Team Stand-up (async Loom Video + Linear Sync)",{"type":32,"tag":97,"props":345,"children":346},{},[347],{"type":37,"value":348},"14:00-17:00: Internal-Meeting-Block (1-on-1s, Project Reviews)",{"type":32,"tag":97,"props":350,"children":351},{},[352],{"type":37,"value":353},"17:30-18:00: Mail Batch Check",{"type":32,"tag":33,"props":355,"children":356},{},[357],{"type":32,"tag":73,"props":358,"children":359},{},[360],{"type":37,"value":361},"Dienstag:",{"type":32,"tag":93,"props":363,"children":364},{},[365,370],{"type":32,"tag":97,"props":366,"children":367},{},[368],{"type":37,"value":369},"09:00-17:00: Customer-Meeting-Tag (45min Slots, 15min Buffer)",{"type":32,"tag":97,"props":371,"children":372},{},[373],{"type":37,"value":374},"17:30-18:30: Meeting-Notizen in Linear Tasks konvertieren",{"type":32,"tag":33,"props":376,"children":377},{},[378],{"type":32,"tag":73,"props":379,"children":380},{},[381],{"type":37,"value":382},"Mittwoch:",{"type":32,"tag":93,"props":384,"children":385},{},[386,391,396],{"type":32,"tag":97,"props":387,"children":388},{},[389],{"type":37,"value":390},"08:00-12:00: Deep Work (technische Dokumente, Architektur-Design)",{"type":32,"tag":97,"props":392,"children":393},{},[394],{"type":37,"value":395},"13:00-15:00: Engineering Meetings (Code Reviews, Sprint Planning)",{"type":32,"tag":97,"props":397,"children":398},{},[399],{"type":37,"value":400},"15:00-17:00: Async Response Time (Slack, Linear, Mail Backlog)",{"type":32,"tag":33,"props":402,"children":403},{},[404],{"type":32,"tag":73,"props":405,"children":406},{},[407],{"type":37,"value":408},"Donnerstag:",{"type":32,"tag":93,"props":410,"children":411},{},[412],{"type":32,"tag":97,"props":413,"children":414},{},[415],{"type":37,"value":416},"09:00-17:00: Customer-Meeting-Tag (gleiches Format wie Dienstag)",{"type":32,"tag":33,"props":418,"children":419},{},[420],{"type":32,"tag":73,"props":421,"children":422},{},[423],{"type":37,"value":424},"Freitag:",{"type":32,"tag":93,"props":426,"children":427},{},[428,433,438],{"type":32,"tag":97,"props":429,"children":430},{},[431],{"type":37,"value":432},"08:00-12:00: Deep Work (neues Produkt-Konzept, Finanzmodell)",{"type":32,"tag":97,"props":434,"children":435},{},[436],{"type":37,"value":437},"13:00-15:00: Weekly Retrospective (Notion-Dokumentation)",{"type":32,"tag":97,"props":439,"children":440},{},[441],{"type":37,"value":442},"15:00-17:00: Nächste Woche planen, Calendar Review",{"type":32,"tag":33,"props":444,"children":445},{},[446],{"type":37,"value":447},"Auffällige Punkte in diesem Template:",{"type":32,"tag":93,"props":449,"children":450},{},[451,461,471,481],{"type":32,"tag":97,"props":452,"children":453},{},[454,459],{"type":32,"tag":73,"props":455,"children":456},{},[457],{"type":37,"value":458},"Deep Work 3× pro Woche",{"type":37,"value":460}," (Mo, Mi, Fr morgens)",{"type":32,"tag":97,"props":462,"children":463},{},[464,469],{"type":32,"tag":73,"props":465,"children":466},{},[467],{"type":37,"value":468},"Customer Meetings in 2 Tage komprimiert",{"type":37,"value":470}," (Di, Do)",{"type":32,"tag":97,"props":472,"children":473},{},[474,479],{"type":32,"tag":73,"props":475,"children":476},{},[477],{"type":37,"value":478},"Eigenes Slot für Async Response",{"type":37,"value":480}," (Mi nachmittags)",{"type":32,"tag":97,"props":482,"children":483},{},[484,489],{"type":32,"tag":73,"props":485,"children":486},{},[487],{"type":37,"value":488},"Täglich unterschiedlicher Kontext",{"type":37,"value":490}," — aber an dem Tag homogene Arbeit",{"type":32,"tag":81,"props":492,"children":494},{"id":493},"block-puffer-die-15-minuten-regel",[495],{"type":37,"value":496},"Block-Puffer: Die 15-Minuten-Regel",{"type":32,"tag":33,"props":498,"children":499},{},[500],{"type":37,"value":501},"Für ein funktionierendes Template ist der Buffer zwischen Blöcken kritisch. Zwischen zwei aufeinanderfolgenden Meetings sollte mindestens 15 Minuten Platz sein. Diese Zeit dient dazu:",{"type":32,"tag":93,"props":503,"children":504},{},[505,510,515],{"type":32,"tag":97,"props":506,"children":507},{},[508],{"type":37,"value":509},"Notizen des vorigen Meetings in Linear zu verarbeiten",{"type":32,"tag":97,"props":511,"children":512},{},[513],{"type":37,"value":514},"Toilette, Wasser trinken (physischer Reset)",{"type":32,"tag":97,"props":516,"children":517},{},[518],{"type":37,"value":519},"Mentalen Kontext des nächsten Meetings laden",{"type":32,"tag":33,"props":521,"children":522},{},[523],{"type":37,"value":524},"Ohne 15-Minuten-Buffer führt ein 8-Stunden-Meeting-Marathon zu Zusammenbruch der kognitiven Last. Roibases interne Analyse von 2023 zeigte: An Tagen ohne Buffer sank die Qualität der Abend-Mail-Antworten des Gründers um 40% (mehr Tippfehler, fehlende Informationen). Mit 15-Minuten-Buffer fiel dieser Rückgang auf 12%.",{"type":32,"tag":40,"props":526,"children":528},{"id":527},"async-first-kultur-kalender-abhängigkeit-reduzieren",[529],{"type":37,"value":530},"Async-First-Kultur: Kalender-Abhängigkeit reduzieren",{"type":32,"tag":33,"props":532,"children":533},{},[534],{"type":37,"value":535},"Die langfristige Nachhaltigkeit von Time-Blocking hängt davon ab, dass das Team eine Async-First-Arbeitskultur übernimmt. Wenn das Team bei jedem Thema reflexartig \"lass uns sofort ein Meeting machen\" sagt, wird der Gründer-Template ständig unterbrochen.",{"type":32,"tag":33,"props":537,"children":538},{},[539],{"type":37,"value":540},"Bei Roibase funktioniert Async-First so:",{"type":32,"tag":542,"props":543,"children":544},"ol",{},[545,555,565],{"type":32,"tag":97,"props":546,"children":547},{},[548,553],{"type":32,"tag":73,"props":549,"children":550},{},[551],{"type":37,"value":552},"Loom Video + Linear Comment:",{"type":37,"value":554}," Wenn ein Team-Mitglied ein Thema ansprechen will, nimmt es zunächst ein 3-Minuten-Loom-Video auf, erklärt das Problem und hängt es an einen Linear Task. Der Gründer schaut das Video nach seinem Deep-Work-Block, antwortet wieder per Loom. Synchrones Meeting entfällt.",{"type":32,"tag":97,"props":556,"children":557},{},[558,563],{"type":32,"tag":73,"props":559,"children":560},{},[561],{"type":37,"value":562},"Notion RFC (Request for Comment):",{"type":37,"value":564}," Für strategische Entscheidungen schreibt der Gründer ein RFC-Dokument, teilt es mit dem Team. Das Team kommentiert asynchron innerhalb von 48 Stunden. Dann ein einziges 30-Minuten-Meeting zur finalen Entscheidung. Vorher liefen solche Diskussionen in 2-Stunden-Brainstorm-Sessions.",{"type":32,"tag":97,"props":566,"children":567},{},[568,573],{"type":32,"tag":73,"props":569,"children":570},{},[571],{"type":37,"value":572},"Slack Thread-Disziplin:",{"type":37,"value":574}," Jede Slack-Nachricht läuft in Threads. Der Haupt-Channel bleibt sauber, der Gründer checkt bei Batch-Checks nur @ mentions. Thread-Inhalte liest er, wenn Zeit ist.",{"type":32,"tag":33,"props":576,"children":577},{},[578],{"type":37,"value":579},"Diese Kultur etabliert sich in 6-8 Monaten. Die erste Woche sagt das Team noch \"aber ohne Meeting können wir nicht entscheiden\", aber nach async-Dokumenten-Ergebnissen adaptiert es sich. Bei Roibase sank die Meeting-Anzahl 2024-2025 um 35%, aber die Entscheidungsgeschwindigkeit stieg (durchschnittliche Time-to-Close in Linear von 4,2 auf 3,1 Tage).",{"type":32,"tag":40,"props":581,"children":583},{"id":582},"entscheidungsmechanismus-calendar-review-routine",[584],{"type":37,"value":585},"Entscheidungsmechanismus: Calendar-Review-Routine",{"type":32,"tag":33,"props":587,"children":588},{},[589],{"type":37,"value":590},"Ein Template zu bauen reicht nicht — jeden Freitag nachmittag sollte 1 Stunde \"Calendar Review\" stattfinden. Diese Review prüft:",{"type":32,"tag":93,"props":592,"children":593},{},[594,604,614,624],{"type":32,"tag":97,"props":595,"children":596},{},[597,602],{"type":32,"tag":73,"props":598,"children":599},{},[600],{"type":37,"value":601},"Bleibt der Deep-Work-Block der nächsten Woche geschützt?",{"type":37,"value":603}," Wenn ein Kunde um ein neues Meeting Montagmorgen bittet, lehne ab oder verschiebe auf Dienstag.",{"type":32,"tag":97,"props":605,"children":606},{},[607,612],{"type":32,"tag":73,"props":608,"children":609},{},[610],{"type":37,"value":611},"Wurde das Batch-Processing-Prinzip verletzt?",{"type":37,"value":613}," Ist ein Internal Meeting in den Dienstag (Customer-Tag) gerutscht? Falls ja, verschiebe auf Mittwoch.",{"type":32,"tag":97,"props":615,"children":616},{},[617,622],{"type":32,"tag":73,"props":618,"children":619},{},[620],{"type":37,"value":621},"Sind Buffer vorhanden?",{"type":37,"value":623}," Hat jedes Meeting 15 Minuten Puffer? Falls nicht, reschedule.",{"type":32,"tag":97,"props":625,"children":626},{},[627,632],{"type":32,"tag":73,"props":628,"children":629},{},[630],{"type":37,"value":631},"Wurde Async-First verletzt?",{"type":37,"value":633}," Hat jemand \"lass uns sofort reden\" gesagt und einen Slot reserviert? Konvertiere zu Async-RFC.",{"type":32,"tag":33,"props":635,"children":636},{},[637],{"type":37,"value":638},"Dieser Review läuft solo vom Gründer, dauert 30 Minuten. Das Ergebnis geht in ein Notion-Dokument und wird mit dem Team geteilt. Beispiel-Output:",{"type":32,"tag":640,"props":641,"children":643},"pre",{"code":642},"## 2026-06-23 Woche Calendar Review\n\n✅ Deep Work geschützt: 3 Blöcke im Plan\n❌ Do 15:00 Engineering-Meeting in Customer-Tag gerutscht → auf Mi verschoben\n✅ Buffer alle vorhanden\n⚠️ Nächste Woche Fr morgen: Customer Escalation → Deep Work auf 13:00 verschoben\n",[644],{"type":32,"tag":645,"props":646,"children":647},"code",{"__ignoreMap":16},[648],{"type":37,"value":642},{"type":32,"tag":40,"props":650,"children":652},{"id":651},"messbare-ergebnisse-aufmerksamkeitsökonomie-roi",[653],{"type":37,"value":654},"Messbare Ergebnisse: Aufmerksamkeitsökonomie-ROI",{"type":32,"tag":33,"props":656,"children":657},{},[658],{"type":37,"value":659},"Wie misst man den Erfolg von Time-Blocking? Roibases Metriken:",{"type":32,"tag":198,"props":661,"children":662},{},[663,684],{"type":32,"tag":202,"props":664,"children":665},{},[666],{"type":32,"tag":206,"props":667,"children":668},{},[669,674,679],{"type":32,"tag":210,"props":670,"children":671},{},[672],{"type":37,"value":673},"Metrik",{"type":32,"tag":210,"props":675,"children":676},{},[677],{"type":37,"value":678},"Messmethode",{"type":32,"tag":210,"props":680,"children":681},{},[682],{"type":37,"value":683},"Ziel",{"type":32,"tag":226,"props":685,"children":686},{},[687,705,723,741,759],{"type":32,"tag":206,"props":688,"children":689},{},[690,695,700],{"type":32,"tag":233,"props":691,"children":692},{},[693],{"type":37,"value":694},"Deep-Work-Stunden\u002FWoche",{"type":32,"tag":233,"props":696,"children":697},{},[698],{"type":37,"value":699},"Calendar Export, Tag-Analyse",{"type":32,"tag":233,"props":701,"children":702},{},[703],{"type":37,"value":704},"≥12 Stunden",{"type":32,"tag":206,"props":706,"children":707},{},[708,713,718],{"type":32,"tag":233,"props":709,"children":710},{},[711],{"type":37,"value":712},"Meetings pro Woche",{"type":32,"tag":233,"props":714,"children":715},{},[716],{"type":37,"value":717},"Google Calendar Report",{"type":32,"tag":233,"props":719,"children":720},{},[721],{"type":37,"value":722},"≤15 Meetings",{"type":32,"tag":206,"props":724,"children":725},{},[726,731,736],{"type":32,"tag":233,"props":727,"children":728},{},[729],{"type":37,"value":730},"Durchschn. Block-Länge",{"type":32,"tag":233,"props":732,"children":733},{},[734],{"type":37,"value":735},"Manuelle Notiz (Notion)",{"type":32,"tag":233,"props":737,"children":738},{},[739],{"type":37,"value":740},"≥90 Minuten",{"type":32,"tag":206,"props":742,"children":743},{},[744,749,754],{"type":32,"tag":233,"props":745,"children":746},{},[747],{"type":37,"value":748},"Async Resolution %",{"type":32,"tag":233,"props":750,"children":751},{},[752],{"type":37,"value":753},"Linear Tasks: \"sync-meeting\"-Tag Anteil",{"type":32,"tag":233,"props":755,"children":756},{},[757],{"type":37,"value":758},"≥60%",{"type":32,"tag":206,"props":760,"children":761},{},[762,767,772],{"type":32,"tag":233,"props":763,"children":764},{},[765],{"type":37,"value":766},"Kontextwechsel pro Tag",{"type":32,"tag":233,"props":768,"children":769},{},[770],{"type":37,"value":771},"Calendar Export, verschiedene Tag-Anzahl",{"type":32,"tag":233,"props":773,"children":774},{},[775],{"type":37,"value":776},"≤5 Wechsel",{"type":32,"tag":33,"props":778,"children":779},{},[780],{"type":37,"value":781},"2025 lag Roibases Gründer bei durchschnittlich 14,2 Stunden Deep Work pro Woche (Ziel 12), 12,8 Meetings (Ziel 15), 67% Async Resolution (Ziel 60). Diese Zahlen entstanden durch konsistente Template-Nutzung.",{"type":32,"tag":783,"props":784,"children":785},"hr",{},[],{"type":32,"tag":33,"props":787,"children":788},{},[789],{"type":37,"value":790},"Der Gründer-Kalender ist kein \"freie Plätze suchen\"-Problem, sondern **Aufmerksamkeitsökonomie",{"title":16,"searchDepth":792,"depth":792,"links":793},3,[794,798,801,804,805,806],{"id":42,"depth":795,"text":45,"children":796},2,[797],{"id":83,"depth":792,"text":86},{"id":131,"depth":795,"text":134,"children":799},[800],{"id":176,"depth":792,"text":179},{"id":314,"depth":795,"text":317,"children":802},[803],{"id":493,"depth":792,"text":496},{"id":527,"depth":795,"text":530},{"id":582,"depth":795,"text":585},{"id":651,"depth":795,"text":654},"markdown","content:de:lifestyle:gruender-kalender-kontext-wechsel-kosten-zeitblockierung.md","content","de\u002Flifestyle\u002Fgruender-kalender-kontext-wechsel-kosten-zeitblockierung.md","de\u002Flifestyle\u002Fgruender-kalender-kontext-wechsel-kosten-zeitblockierung","md",1782079489067]