[{"data":1,"prerenderedAt":824},["ShallowReactive",2],{"article-alternates":3,"article-\u002Fen\u002Flifestyle\u002Ffounder-calendar-context-switching-cost-and-time-block-discipline":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":14,"_dir":15,"_draft":16,"_partial":16,"_locale":17,"title":18,"description":19,"publishedAt":20,"modifiedAt":20,"category":15,"i18nKey":4,"tags":21,"readingTime":27,"author":28,"body":29,"_type":818,"_id":819,"_source":820,"_file":821,"_stem":822,"_extension":823},"\u002Fen\u002Flifestyle\u002Ffounder-calendar-context-switching-cost-and-time-block-discipline","lifestyle",false,"","Founder Calendar: Context-Switching Cost and Time-Block Discipline","Transform your calendar into an operational asset with 4-hour deep work blocks, async response windows, and customer meeting cadence.","2026-06-17",[22,23,24,25,26],"deep-work","time-blocking","founder-productivity","async-first","calendar-management",7,"Roibase",{"type":30,"children":31,"toc":802},"root",[32,40,47,52,68,81,88,93,118,136,142,152,157,175,180,186,198,203,308,313,318,324,329,337,360,368,381,389,407,415,423,431,449,454,495,501,506,524,529,535,540,545,579,584,590,595,638,643,653,659,664,781,786,790],{"type":33,"tag":34,"props":35,"children":36},"element","p",{},[37],{"type":38,"value":39},"text","Calendar management is critical for founders — but most treat it as a \"finding empty slots\" problem. The real issue is different: how many times per day are you switching contexts? Moving from a meeting to a code review, then to customer email, then to strategic documentation creates compounding cognitive load. Research shows it takes 23 minutes to re-establish focus after a task switch (UC Irvine, 2021). Eight context switches per day = 3 hours lost. A founder's only capital is attention — your calendar is the architecture of that economy.",{"type":33,"tag":41,"props":42,"children":44},"h2",{"id":43},"context-switching-cost-the-unmeasured-harm",[45],{"type":38,"value":46},"Context-Switching Cost: The Unmeasured Harm",{"type":33,"tag":34,"props":48,"children":49},{},[50],{"type":38,"value":51},"When your calendar shows two consecutive meetings of different types (say, 10:00 performance review, 11:00 product roadmap discussion), you incur a hidden cost: the residual effect of the previous context lingers while you're trying to load the new one. This \"task-switching cost\" is well-researched in literature, yet founder calendars are often filled like a Tetris game without accounting for it.",{"type":33,"tag":34,"props":53,"children":54},{},[55,57,66],{"type":38,"value":56},"Concrete impact: 09:00 customer call, 10:30 team standup, 11:00 budget review. With each transition, working memory gets flushed. Deep work requiring sustained focus (say, drafting a new ",{"type":33,"tag":58,"props":59,"children":63},"a",{"href":60,"rel":61},"https:\u002F\u002Fwww.roibase.com.tr\u002Fen\u002Fbranding",[62],"nofollow",[64],{"type":38,"value":65},"branding strategy",{"type":38,"value":67},") disappears — remaining slots are filled with shallow work (email, Slack, document edits).",{"type":33,"tag":34,"props":69,"children":70},{},[71,73,79],{"type":38,"value":72},"The solution: time-blocking — but not generic blocks. ",{"type":33,"tag":74,"props":75,"children":76},"strong",{},[77],{"type":38,"value":78},"Context-homogeneous blocks.",{"type":38,"value":80}," Within a single day, designate time for \"customer meetings only,\" \"internal strategic documentation only,\" \"code review and engineering calls only.\" By 14:00, you're fully in customer mode and stay there until 17:00.",{"type":33,"tag":82,"props":83,"children":85},"h3",{"id":84},"practical-rule-the-4-hour-deep-work-block",[86],{"type":38,"value":87},"Practical Rule: The 4-Hour Deep Work Block",{"type":33,"tag":34,"props":89,"children":90},{},[91],{"type":38,"value":92},"Eight years at Roibase taught us this: founders need at least 2 uninterrupted 4-hour deep work blocks per week. These fit into morning (08:00–12:00) or afternoon (13:00–17:00) slots. During these blocks:",{"type":33,"tag":94,"props":95,"children":96},"ul",{},[97,103,108,113],{"type":33,"tag":98,"props":99,"children":100},"li",{},[101],{"type":38,"value":102},"Slack is off (DND enabled)",{"type":33,"tag":98,"props":104,"children":105},{},[106],{"type":38,"value":107},"No meetings (calendar shows \"busy\")",{"type":33,"tag":98,"props":109,"children":110},{},[111],{"type":38,"value":112},"No phone calls",{"type":33,"tag":98,"props":114,"children":115},{},[116],{"type":38,"value":117},"Email batch-checked once (e.g., at 12:00)",{"type":33,"tag":34,"props":119,"children":120},{},[121,123,129,131],{"type":38,"value":122},"Four continuous hours falls slightly below Cal Newport's \"professional peak performance\" threshold in ",{"type":33,"tag":124,"props":125,"children":126},"em",{},[127],{"type":38,"value":128},"Deep Work",{"type":38,"value":130}," (he recommends 4–5 hours). But protecting four hours as a founder requires discipline. What happens in these blocks? Strategic documents (annual planning, new business models, technical architecture), complex code writing, new product concepts — work where ",{"type":33,"tag":74,"props":132,"children":133},{},[134],{"type":38,"value":135},"output cannot be delayed, but input cannot tolerate interruption.",{"type":33,"tag":41,"props":137,"children":139},{"id":138},"customer-meeting-cadence-the-batch-processing-principle",[140],{"type":38,"value":141},"Customer Meeting Cadence: The Batch-Processing Principle",{"type":33,"tag":34,"props":143,"children":144},{},[145,147],{"type":38,"value":146},"The second major source of entropy in a founder's calendar is customer meetings scattered across the week. Three to four calls at different times daily puts the day entirely in reactive mode. Alternative: ",{"type":33,"tag":74,"props":148,"children":149},{},[150],{"type":38,"value":151},"cadence-based batching.",{"type":33,"tag":34,"props":153,"children":154},{},[155],{"type":38,"value":156},"Concrete application: Dedicate two specific days (e.g., Tuesday and Thursday) entirely to customer meetings. These days run 09:00–17:00 as consecutive 45-minute slots with 15-minute buffers. Result:",{"type":33,"tag":94,"props":158,"children":159},{},[160,165,170],{"type":33,"tag":98,"props":161,"children":162},{},[163],{"type":38,"value":164},"Monday, Wednesday, Friday remain internal-operations only",{"type":33,"tag":98,"props":166,"children":167},{},[168],{"type":38,"value":169},"Customer expectation is clear: \"Roibase meetings happen Tuesday\u002FThursday\"",{"type":33,"tag":98,"props":171,"children":172},{},[173],{"type":38,"value":174},"Every Tuesday morning, you flip into \"customer mode\" and stay there — zero context switching",{"type":33,"tag":34,"props":176,"children":177},{},[178],{"type":38,"value":179},"Batch processing's second benefit: you spot patterns immediately. Three different customers in one day mention \"first-party data integration,\" and by evening you've drafted a strategic response. If spread across the week, that pattern dies.",{"type":33,"tag":82,"props":181,"children":183},{"id":182},"async-response-window-mail-and-slack-batch-check",[184],{"type":38,"value":185},"Async Response Window: Mail and Slack Batch Check",{"type":33,"tag":34,"props":187,"children":188},{},[189,191,196],{"type":38,"value":190},"Most founders respond to Slack and email throughout the day, calling it \"responsiveness.\" That's not responsive — that's ",{"type":33,"tag":74,"props":192,"children":193},{},[194],{"type":38,"value":195},"reactive",{"type":38,"value":197},". The distinction: responsive means answering within a defined window (e.g., four hours). Reactive means jumping at every notification.",{"type":33,"tag":34,"props":199,"children":200},{},[201],{"type":38,"value":202},"At Roibase, async response windows work like this:",{"type":33,"tag":204,"props":205,"children":206},"table",{},[207,231],{"type":33,"tag":208,"props":209,"children":210},"thead",{},[211],{"type":33,"tag":212,"props":213,"children":214},"tr",{},[215,221,226],{"type":33,"tag":216,"props":217,"children":218},"th",{},[219],{"type":38,"value":220},"Channel",{"type":33,"tag":216,"props":222,"children":223},{},[224],{"type":38,"value":225},"Response Window",{"type":33,"tag":216,"props":227,"children":228},{},[229],{"type":38,"value":230},"Batch-Check Time",{"type":33,"tag":232,"props":233,"children":234},"tbody",{},[235,254,272,290],{"type":33,"tag":212,"props":236,"children":237},{},[238,244,249],{"type":33,"tag":239,"props":240,"children":241},"td",{},[242],{"type":38,"value":243},"Slack (non-urgent)",{"type":33,"tag":239,"props":245,"children":246},{},[247],{"type":38,"value":248},"4 hours",{"type":33,"tag":239,"props":250,"children":251},{},[252],{"type":38,"value":253},"09:00, 13:00, 17:00",{"type":33,"tag":212,"props":255,"children":256},{},[257,262,267],{"type":33,"tag":239,"props":258,"children":259},{},[260],{"type":38,"value":261},"Email",{"type":33,"tag":239,"props":263,"children":264},{},[265],{"type":38,"value":266},"24 hours",{"type":33,"tag":239,"props":268,"children":269},{},[270],{"type":38,"value":271},"12:00, 17:30",{"type":33,"tag":212,"props":273,"children":274},{},[275,280,285],{"type":33,"tag":239,"props":276,"children":277},{},[278],{"type":38,"value":279},"Linear task mention",{"type":33,"tag":239,"props":281,"children":282},{},[283],{"type":38,"value":284},"8 hours",{"type":33,"tag":239,"props":286,"children":287},{},[288],{"type":38,"value":289},"10:00, 16:00",{"type":33,"tag":212,"props":291,"children":292},{},[293,298,303],{"type":33,"tag":239,"props":294,"children":295},{},[296],{"type":38,"value":297},"Emergency (phone)",{"type":33,"tag":239,"props":299,"children":300},{},[301],{"type":38,"value":302},"Immediate",{"type":33,"tag":239,"props":304,"children":305},{},[306],{"type":38,"value":307},"Always available",{"type":33,"tag":34,"props":309,"children":310},{},[311],{"type":38,"value":312},"With this system, your team knows they'll get Slack responses within four hours — acceptable because truly urgent issues trigger a phone call. Twenty-four-hour email windows work for external stakeholders (customers, partners). Internal urgent items use Linear mentions with an eight-hour window.",{"type":33,"tag":34,"props":314,"children":315},{},[316],{"type":38,"value":317},"Result: The founder opens Slack three times daily. Each session is a batch process: read all messages, prioritize, respond, close. No 15 Slack notifications per day.",{"type":33,"tag":41,"props":319,"children":321},{"id":320},"time-block-discipline-the-template-week",[322],{"type":38,"value":323},"Time-Block Discipline: The Template Week",{"type":33,"tag":34,"props":325,"children":326},{},[327],{"type":38,"value":328},"Time-blocking succeeds through consistency — not experimenting with a new strategy each week, but locking a template and respecting it. Roibase's founder calendar template:",{"type":33,"tag":34,"props":330,"children":331},{},[332],{"type":33,"tag":74,"props":333,"children":334},{},[335],{"type":38,"value":336},"Monday:",{"type":33,"tag":94,"props":338,"children":339},{},[340,345,350,355],{"type":33,"tag":98,"props":341,"children":342},{},[343],{"type":38,"value":344},"08:00–12:00: Deep work (strategic planning or complex code)",{"type":33,"tag":98,"props":346,"children":347},{},[348],{"type":38,"value":349},"13:00–14:00: Team standup (async Loom + Linear sync)",{"type":33,"tag":98,"props":351,"children":352},{},[353],{"type":38,"value":354},"14:00–17:00: Internal meeting block (1-on-1s, project reviews)",{"type":33,"tag":98,"props":356,"children":357},{},[358],{"type":38,"value":359},"17:30–18:00: Mail batch check",{"type":33,"tag":34,"props":361,"children":362},{},[363],{"type":33,"tag":74,"props":364,"children":365},{},[366],{"type":38,"value":367},"Tuesday:",{"type":33,"tag":94,"props":369,"children":370},{},[371,376],{"type":33,"tag":98,"props":372,"children":373},{},[374],{"type":38,"value":375},"09:00–17:00: Customer meeting day (45-min slots, 15-min buffers)",{"type":33,"tag":98,"props":377,"children":378},{},[379],{"type":38,"value":380},"17:30–18:30: Convert meeting notes into Linear tasks",{"type":33,"tag":34,"props":382,"children":383},{},[384],{"type":33,"tag":74,"props":385,"children":386},{},[387],{"type":38,"value":388},"Wednesday:",{"type":33,"tag":94,"props":390,"children":391},{},[392,397,402],{"type":33,"tag":98,"props":393,"children":394},{},[395],{"type":38,"value":396},"08:00–12:00: Deep work (technical documents, architecture design)",{"type":33,"tag":98,"props":398,"children":399},{},[400],{"type":38,"value":401},"13:00–15:00: Engineering calls (code review, sprint planning)",{"type":33,"tag":98,"props":403,"children":404},{},[405],{"type":38,"value":406},"15:00–17:00: Async response time (Slack, Linear, mail backlog)",{"type":33,"tag":34,"props":408,"children":409},{},[410],{"type":33,"tag":74,"props":411,"children":412},{},[413],{"type":38,"value":414},"Thursday:",{"type":33,"tag":94,"props":416,"children":417},{},[418],{"type":33,"tag":98,"props":419,"children":420},{},[421],{"type":38,"value":422},"09:00–17:00: Customer meeting day (same format as Tuesday)",{"type":33,"tag":34,"props":424,"children":425},{},[426],{"type":33,"tag":74,"props":427,"children":428},{},[429],{"type":38,"value":430},"Friday:",{"type":33,"tag":94,"props":432,"children":433},{},[434,439,444],{"type":33,"tag":98,"props":435,"children":436},{},[437],{"type":38,"value":438},"08:00–12:00: Deep work (new product concepts, financial models)",{"type":33,"tag":98,"props":440,"children":441},{},[442],{"type":38,"value":443},"13:00–15:00: Weekly retrospective (document in Notion)",{"type":33,"tag":98,"props":445,"children":446},{},[447],{"type":38,"value":448},"15:00–17:00: Next-week planning and calendar review",{"type":33,"tag":34,"props":450,"children":451},{},[452],{"type":38,"value":453},"Key observations:",{"type":33,"tag":94,"props":455,"children":456},{},[457,467,477,487],{"type":33,"tag":98,"props":458,"children":459},{},[460,465],{"type":33,"tag":74,"props":461,"children":462},{},[463],{"type":38,"value":464},"Deep work blocks 3x weekly",{"type":38,"value":466}," (Monday, Wednesday, Friday mornings)",{"type":33,"tag":98,"props":468,"children":469},{},[470,475],{"type":33,"tag":74,"props":471,"children":472},{},[473],{"type":38,"value":474},"Customer meetings concentrated on 2 days",{"type":38,"value":476}," (Tuesday, Thursday)",{"type":33,"tag":98,"props":478,"children":479},{},[480,485],{"type":33,"tag":74,"props":481,"children":482},{},[483],{"type":38,"value":484},"Dedicated async response slot",{"type":38,"value":486}," (Wednesday afternoon)",{"type":33,"tag":98,"props":488,"children":489},{},[490],{"type":33,"tag":74,"props":491,"children":492},{},[493],{"type":38,"value":494},"Different context daily — but homogeneous work within that day",{"type":33,"tag":82,"props":496,"children":498},{"id":497},"block-to-block-buffer-the-15-minute-rule",[499],{"type":38,"value":500},"Block-to-Block Buffer: The 15-Minute Rule",{"type":33,"tag":34,"props":502,"children":503},{},[504],{"type":38,"value":505},"For the template to function, buffers between blocks are critical. At least 15 minutes must separate consecutive meetings. This time is for:",{"type":33,"tag":94,"props":507,"children":508},{},[509,514,519],{"type":33,"tag":98,"props":510,"children":511},{},[512],{"type":38,"value":513},"Processing notes from the previous meeting into Linear",{"type":33,"tag":98,"props":515,"children":516},{},[517],{"type":38,"value":518},"Physical reset (bathroom, water, movement)",{"type":33,"tag":98,"props":520,"children":521},{},[522],{"type":38,"value":523},"Mental loading of the next meeting's context",{"type":33,"tag":34,"props":525,"children":526},{},[527],{"type":38,"value":528},"Without 15-minute buffers, an 8-hour meeting marathon collapses cognitive load. Internal Roibase analysis (2023) showed that on buffer-less meeting days, founder email-response quality dropped 40% (typos, missing info). Adding 15-minute buffers reduced that decline to 12%.",{"type":33,"tag":41,"props":530,"children":532},{"id":531},"async-first-culture-reducing-calendar-dependency",[533],{"type":38,"value":534},"Async-First Culture: Reducing Calendar Dependency",{"type":33,"tag":34,"props":536,"children":537},{},[538],{"type":38,"value":539},"Time-blocking's long-term sustainability depends on team adoption of async-first work culture. If your team reflexively schedules synchronous meetings for everything, your template fractures constantly.",{"type":33,"tag":34,"props":541,"children":542},{},[543],{"type":38,"value":544},"At Roibase, async-first works like this:",{"type":33,"tag":546,"props":547,"children":548},"ol",{},[549,559,569],{"type":33,"tag":98,"props":550,"children":551},{},[552,557],{"type":33,"tag":74,"props":553,"children":554},{},[555],{"type":38,"value":556},"Loom video + Linear comment:",{"type":38,"value":558}," Team member has a topic? Record a 3-minute Loom explaining the problem, attach it to a Linear task. Founder watches after their deep work block ends, replies with another Loom. No sync meeting needed.",{"type":33,"tag":98,"props":560,"children":561},{},[562,567],{"type":33,"tag":74,"props":563,"children":564},{},[565],{"type":38,"value":566},"Notion RFC (Request for Comment):",{"type":38,"value":568}," For strategic decisions, founder writes an RFC document, shares it with the team. Team adds async comments within 48 hours. One 30-minute sync meeting follows for final decision. Previously, this was a 2-hour brainstorm.",{"type":33,"tag":98,"props":570,"children":571},{},[572,577],{"type":33,"tag":74,"props":573,"children":574},{},[575],{"type":38,"value":576},"Slack thread discipline:",{"type":38,"value":578}," Every Slack message lives in a thread. Main channel stays clean. During batch checks, founder scans only @ mentions. Threads get reviewed when time allows.",{"type":33,"tag":34,"props":580,"children":581},{},[582],{"type":38,"value":583},"This culture embeds in 6–8 months. The first three months, teams resist (\"how can we decide without a meeting?\"). But when async documents produce results, adoption accelerates. Roibase saw a 35% meeting reduction from 2024–2025, yet decision speed improved (Linear average time-to-close dropped from 4.2 days to 3.1).",{"type":33,"tag":41,"props":585,"children":587},{"id":586},"decision-mechanism-the-calendar-review-ritual",[588],{"type":38,"value":589},"Decision Mechanism: The Calendar Review Ritual",{"type":33,"tag":34,"props":591,"children":592},{},[593],{"type":38,"value":594},"Creating a template isn't enough — dedicate Friday afternoon to a 1-hour \"calendar review.\" In this session, check:",{"type":33,"tag":94,"props":596,"children":597},{},[598,608,618,628],{"type":33,"tag":98,"props":599,"children":600},{},[601,606],{"type":33,"tag":74,"props":602,"children":603},{},[604],{"type":38,"value":605},"Deep work block protected for next week?",{"type":38,"value":607}," If a customer requests a new call Tuesday morning, decline or reschedule to Tuesday afternoon.",{"type":33,"tag":98,"props":609,"children":610},{},[611,616],{"type":33,"tag":74,"props":612,"children":613},{},[614],{"type":38,"value":615},"Batch-processing principle violated?",{"type":38,"value":617}," Did an internal meeting seep into Tuesday (customer day)? Move it to Wednesday.",{"type":33,"tag":98,"props":619,"children":620},{},[621,626],{"type":33,"tag":74,"props":622,"children":623},{},[624],{"type":38,"value":625},"Buffers intact?",{"type":38,"value":627}," Is there 15 minutes between consecutive calls? Reschedule if not.",{"type":33,"tag":98,"props":629,"children":630},{},[631,636],{"type":33,"tag":74,"props":632,"children":633},{},[634],{"type":38,"value":635},"Async-first breached?",{"type":38,"value":637}," Did someone request \"let's talk now\" and grab a slot? Convert to async RFC.",{"type":33,"tag":34,"props":639,"children":640},{},[641],{"type":38,"value":642},"Do this review solo, 30 minutes. Log output in a Notion doc, share with the team. Example:",{"type":33,"tag":644,"props":645,"children":647},"pre",{"code":646},"## 2026-06-23 Week Calendar Review\n\n✅ Deep work protected: 3 blocks in place\n❌ Thursday 15:00 engineering call spilled into customer day → moved to Wednesday\n✅ Buffers maintained\n⚠️ Next week Friday morning: customer escalation → deep work shifted to 13:00\n",[648],{"type":33,"tag":649,"props":650,"children":651},"code",{"__ignoreMap":17},[652],{"type":38,"value":646},{"type":33,"tag":41,"props":654,"children":656},{"id":655},"measurable-results-attention-economy-roi",[657],{"type":38,"value":658},"Measurable Results: Attention Economy ROI",{"type":33,"tag":34,"props":660,"children":661},{},[662],{"type":38,"value":663},"How do you measure time-blocking success? Roibase tracks these:",{"type":33,"tag":204,"props":665,"children":666},{},[667,688],{"type":33,"tag":208,"props":668,"children":669},{},[670],{"type":33,"tag":212,"props":671,"children":672},{},[673,678,683],{"type":33,"tag":216,"props":674,"children":675},{},[676],{"type":38,"value":677},"Metric",{"type":33,"tag":216,"props":679,"children":680},{},[681],{"type":38,"value":682},"Measurement",{"type":33,"tag":216,"props":684,"children":685},{},[686],{"type":38,"value":687},"Target",{"type":33,"tag":232,"props":689,"children":690},{},[691,709,727,745,763],{"type":33,"tag":212,"props":692,"children":693},{},[694,699,704],{"type":33,"tag":239,"props":695,"children":696},{},[697],{"type":38,"value":698},"Deep work hours\u002Fweek",{"type":33,"tag":239,"props":700,"children":701},{},[702],{"type":38,"value":703},"Calendar export, tag analysis",{"type":33,"tag":239,"props":705,"children":706},{},[707],{"type":38,"value":708},"≥12 hours",{"type":33,"tag":212,"props":710,"children":711},{},[712,717,722],{"type":33,"tag":239,"props":713,"children":714},{},[715],{"type":38,"value":716},"Meetings\u002Fweek",{"type":33,"tag":239,"props":718,"children":719},{},[720],{"type":38,"value":721},"Google Calendar report",{"type":33,"tag":239,"props":723,"children":724},{},[725],{"type":38,"value":726},"≤15 meetings",{"type":33,"tag":212,"props":728,"children":729},{},[730,735,740],{"type":33,"tag":239,"props":731,"children":732},{},[733],{"type":38,"value":734},"Avg. block length",{"type":33,"tag":239,"props":736,"children":737},{},[738],{"type":38,"value":739},"Manual tracking (Notion)",{"type":33,"tag":239,"props":741,"children":742},{},[743],{"type":38,"value":744},"≥90 minutes",{"type":33,"tag":212,"props":746,"children":747},{},[748,753,758],{"type":33,"tag":239,"props":749,"children":750},{},[751],{"type":38,"value":752},"Async resolution %",{"type":33,"tag":239,"props":754,"children":755},{},[756],{"type":38,"value":757},"Linear: % tasks without \"sync meeting\" tag",{"type":33,"tag":239,"props":759,"children":760},{},[761],{"type":38,"value":762},"≥60%",{"type":33,"tag":212,"props":764,"children":765},{},[766,771,776],{"type":33,"tag":239,"props":767,"children":768},{},[769],{"type":38,"value":770},"Context switches\u002Fday",{"type":33,"tag":239,"props":772,"children":773},{},[774],{"type":38,"value":775},"Calendar export: distinct tag count",{"type":33,"tag":239,"props":777,"children":778},{},[779],{"type":38,"value":780},"≤5 switches",{"type":33,"tag":34,"props":782,"children":783},{},[784],{"type":38,"value":785},"In 2025, Roibase's founder averaged 14.2 deep work hours\u002Fweek (target: 12), 12.8 meetings\u002Fweek (target: 15), 67% async resolution (target: 60). Consistent template adherence achieved these numbers.",{"type":33,"tag":787,"props":788,"children":789},"hr",{},[],{"type":33,"tag":34,"props":791,"children":792},{},[793,795,800],{"type":38,"value":794},"Your founder calendar isn't a \"slot-finding problem\" — it's ",{"type":33,"tag":74,"props":796,"children":797},{},[798],{"type":38,"value":799},"attention-economy optimization",{"type":38,"value":801},". Every slot is an investment decision: where does this hour go? Ignore context-switching costs and three hours of your eight-hour day vanish. With time-block discipline, async-first culture, and cadence-based batching, you recapture that loss. Build the template, review it every Friday, stay disciplined for eight weeks — your calendar becomes an operational asset.",{"title":17,"searchDepth":803,"depth":803,"links":804},3,[805,809,812,815,816,817],{"id":43,"depth":806,"text":46,"children":807},2,[808],{"id":84,"depth":803,"text":87},{"id":138,"depth":806,"text":141,"children":810},[811],{"id":182,"depth":803,"text":185},{"id":320,"depth":806,"text":323,"children":813},[814],{"id":497,"depth":803,"text":500},{"id":531,"depth":806,"text":534},{"id":586,"depth":806,"text":589},{"id":655,"depth":806,"text":658},"markdown","content:en:lifestyle:founder-calendar-context-switching-cost-and-time-block-discipline.md","content","en\u002Flifestyle\u002Ffounder-calendar-context-switching-cost-and-time-block-discipline.md","en\u002Flifestyle\u002Ffounder-calendar-context-switching-cost-and-time-block-discipline","md",1782079487615]