[{"data":1,"prerenderedAt":526},["ShallowReactive",2],{"article-alternates":3,"article-\u002Ffr\u002Flifestyle\u002Ffounder-calendar-context-switching-time-blocking":13},{"i18nKey":4,"paths":5},"lifestyle-002-2026-08",{"de":6,"en":7,"es":8,"fr":9,"it":10,"ru":11,"tr":12},"\u002Fde\u002Flifestyle\u002Ffounder-calendar-context-switching-costs-time-blocking-discipline","\u002Fen\u002Flifestyle\u002Ffounder-calendar-context-switching-cost-time-block-discipline","\u002Fes\u002Flifestyle\u002Fcalendario-founder-costo-cambio-contexto-disciplina-time-block","\u002Ffr\u002Flifestyle\u002Ffounder-calendar-context-switching-time-blocking","\u002Fit\u002Flifestyle\u002Fcalendario-del-fondatore-context-switching-e-disciplina-del-time-blocking","\u002Fru\u002Flifestyle\u002Ffounder-calendar-context-switching-cost-time-blocking-discipline","\u002Ftr\u002Flifestyle\u002Ffounder-calendar-baglam-anahtarlama-maliyeti-ve-time-block-disiplini",{"_path":9,"_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":520,"_id":521,"_source":522,"_file":523,"_stem":524,"_extension":525},"lifestyle",false,"","Founder Calendar: Context Switching Cost and Time-Block Discipline","A measurable time architecture with 4-hour deep work blocks, customer meeting cadence, and async response windows for operational efficiency.","2026-08-03",[21,22,23,24,25],"time-blocking","deep-work","founder-productivity","async-first","context-switching",8,"Roibase",{"type":29,"children":30,"toc":502},"root",[31,39,52,59,64,69,81,88,93,99,104,109,212,217,227,233,238,244,256,261,296,312,318,330,335,341,353,358,392,404,410,422,427,433,438,471,476,481,487,492,497],{"type":32,"tag":33,"props":34,"children":35},"element","p",{},[36],{"type":37,"value":38},"text","Calendar management is not the solution to the problem—it is the problem itself. The average founder switches context 11 times per day (2023 RescueTime data). Each switch costs an average of 23 minutes of lost focus. A day is not 8 hours, but 8 fragmented 30-minute slots. The enemy of operational efficiency is not empty calendar blocks, but random fills.",{"type":32,"tag":33,"props":40,"children":41},{},[42,44,50],{"type":37,"value":43},"Roibase has grown with founder\u002Foperator team culture for 8+ years. We anchored the calendar to a single principle: ",{"type":32,"tag":45,"props":46,"children":47},"strong",{},[48],{"type":37,"value":49},"a time block is a commitment, and commitments are measured",{"type":37,"value":51},". A 4-hour deep work block, customer meeting cadence, async response window—these are not \"ideal work routines,\" but operational parameters of the firm. This piece shows how those parameters are set.",{"type":32,"tag":53,"props":54,"children":56},"h2",{"id":55},"context-switching-hidden-operational-cost",[57],{"type":37,"value":58},"Context switching: hidden operational cost",{"type":32,"tag":33,"props":60,"children":61},{},[62],{"type":37,"value":63},"Context switching is the reloading of working memory in the brain. When you move from a Linear card to Figma, then to a customer email, the previous context is purged from the cache each time. Regaining the same concentration level on return takes 15–25 minutes.",{"type":32,"tag":33,"props":65,"children":66},{},[67],{"type":37,"value":68},"The typical founder calendar is not structured around this. Morning 09:00 meeting, 10:00 code review, 11:00 sales call, 12:00 Slack catch-up. Each slot a different cognitive mode: strategic, technical, communicative, reactive. The end-of-day feeling of \"nothing got done\" comes from here—you actually worked 8 hours, but never spent more than 2 on any one thing.",{"type":32,"tag":33,"props":70,"children":71},{},[72,74,79],{"type":37,"value":73},"The solution: ",{"type":32,"tag":45,"props":75,"children":76},{},[77],{"type":37,"value":78},"thematic blocking",{"type":37,"value":80},". Stack tasks that stay in the same cognitive mode consecutively. For example: Monday morning 09:00–13:00 = code\u002Fdesign sprint review + product backlog. Tuesday morning = customer calls + proposals. Wednesday morning = strategic writing (roadmap, blog, investor update). Each block 4 hours—to stay above the deep work threshold.",{"type":32,"tag":82,"props":83,"children":85},"h3",{"id":84},"measurement-time-to-context-load",[86],{"type":37,"value":87},"Measurement: time-to-context-load",{"type":32,"tag":33,"props":89,"children":90},{},[91],{"type":37,"value":92},"Track context switches with RescueTime or Toggl. Target: under 3 per day. 3 switches = 4 day blocks (morning, midday, afternoon, evening). 4 blocks = maximum 4 cognitive modes. If you're switching 8+ times daily, your calendar reflects others' priorities, not yours.",{"type":32,"tag":53,"props":94,"children":96},{"id":95},"_4-hour-deep-work-block-architecture-of-uninterrupted-focus",[97],{"type":37,"value":98},"4-hour deep work block: architecture of uninterrupted focus",{"type":32,"tag":33,"props":100,"children":101},{},[102],{"type":37,"value":103},"Deep work became popular with Cal Newport's 2016 book, but its executable form lives in a specific calendar placement. 4 hours is not arbitrary—literature shows optimal focus spans 90–120 minute cycles with breaks, scaling to 4 hours (Ultradian Rhythm hypothesis).",{"type":32,"tag":33,"props":105,"children":106},{},[107],{"type":37,"value":108},"At Roibase, a deep work block looks like this:",{"type":32,"tag":110,"props":111,"children":112},"table",{},[113,137],{"type":32,"tag":114,"props":115,"children":116},"thead",{},[117],{"type":32,"tag":118,"props":119,"children":120},"tr",{},[121,127,132],{"type":32,"tag":122,"props":123,"children":124},"th",{},[125],{"type":37,"value":126},"Slot",{"type":32,"tag":122,"props":128,"children":129},{},[130],{"type":37,"value":131},"Duration",{"type":32,"tag":122,"props":133,"children":134},{},[135],{"type":37,"value":136},"Content",{"type":32,"tag":138,"props":139,"children":140},"tbody",{},[141,160,178,195],{"type":32,"tag":118,"props":142,"children":143},{},[144,150,155],{"type":32,"tag":145,"props":146,"children":147},"td",{},[148],{"type":37,"value":149},"09:00–10:30",{"type":32,"tag":145,"props":151,"children":152},{},[153],{"type":37,"value":154},"90 min",{"type":32,"tag":145,"props":156,"children":157},{},[158],{"type":37,"value":159},"Focus task (code, design, writing)",{"type":32,"tag":118,"props":161,"children":162},{},[163,168,173],{"type":32,"tag":145,"props":164,"children":165},{},[166],{"type":37,"value":167},"10:30–10:45",{"type":32,"tag":145,"props":169,"children":170},{},[171],{"type":37,"value":172},"15 min",{"type":32,"tag":145,"props":174,"children":175},{},[176],{"type":37,"value":177},"Break (walk, coffee—not screens)",{"type":32,"tag":118,"props":179,"children":180},{},[181,186,190],{"type":32,"tag":145,"props":182,"children":183},{},[184],{"type":37,"value":185},"10:45–12:15",{"type":32,"tag":145,"props":187,"children":188},{},[189],{"type":37,"value":154},{"type":32,"tag":145,"props":191,"children":192},{},[193],{"type":37,"value":194},"Same context or related task",{"type":32,"tag":118,"props":196,"children":197},{},[198,203,207],{"type":32,"tag":145,"props":199,"children":200},{},[201],{"type":37,"value":202},"12:15–12:30",{"type":32,"tag":145,"props":204,"children":205},{},[206],{"type":37,"value":172},{"type":32,"tag":145,"props":208,"children":209},{},[210],{"type":37,"value":211},"Buffer (short Slack check, emails, block closure)",{"type":32,"tag":33,"props":213,"children":214},{},[215],{"type":37,"value":216},"Total 4 hours—210 minutes net focus, 30 minutes breaks. Once the block ends, the day's production is done. Afternoon is meetings, async response, admin. Real output happened 09:00–12:30.",{"type":32,"tag":33,"props":218,"children":219},{},[220,225],{"type":32,"tag":45,"props":221,"children":222},{},[223],{"type":37,"value":224},"Critical rule:",{"type":37,"value":226}," No interrupts inside the block. Slack off, email off, phone silent. Calendar marked \"Busy\" (auto-decline active). If something urgent comes up, they open a Linear card; you check it when the block ends. Without this discipline, 4 hours drops to 2.5.",{"type":32,"tag":82,"props":228,"children":230},{"id":229},"is-one-deep-work-block-per-day-enough",[231],{"type":37,"value":232},"Is one deep work block per day enough?",{"type":32,"tag":33,"props":234,"children":235},{},[236],{"type":37,"value":237},"Yes. Because achieving 4 uninterrupted hours daily is already a stretch for most founders. 2023 Asana study: the average knowledge worker manages 1.5 hours of deep work per day. If you're hitting 4, you're already in the top 10%. The goal is not two blocks, but protecting one with discipline.",{"type":32,"tag":53,"props":239,"children":241},{"id":240},"customer-meeting-cadence-predictable-interaction-rhythm",[242],{"type":37,"value":243},"Customer meeting cadence: predictable interaction rhythm",{"type":32,"tag":33,"props":245,"children":246},{},[247,249,254],{"type":37,"value":248},"Customer meetings are not scattered—they run on ",{"type":32,"tag":45,"props":250,"children":251},{},[252],{"type":37,"value":253},"cadence",{"type":37,"value":255},". Cadence = predictable rhythm. Example: Tuesday and Thursday 14:00–17:00 = customer slots. No meetings other days.",{"type":32,"tag":33,"props":257,"children":258},{},[259],{"type":37,"value":260},"This structure delivers three benefits:",{"type":32,"tag":262,"props":263,"children":264},"ol",{},[265,276,286],{"type":32,"tag":266,"props":267,"children":268},"li",{},[269,274],{"type":32,"tag":45,"props":270,"children":271},{},[272],{"type":37,"value":273},"Context preserved:",{"type":37,"value":275}," Customer mode is a separate cognitive mode. Instead of writing code Tuesday morning then pivoting to sales calls in the afternoon, Tuesday becomes an \"outward-facing day\" entirely.",{"type":32,"tag":266,"props":277,"children":278},{},[279,284],{"type":32,"tag":45,"props":280,"children":281},{},[282],{"type":37,"value":283},"Customer clarity:",{"type":37,"value":285}," Instead of \"When are you free?\" you offer \"Tuesday 15:00 or Thursday 14:30.\" Uncertainty drops.",{"type":32,"tag":266,"props":287,"children":288},{},[289,294],{"type":32,"tag":45,"props":290,"children":291},{},[292],{"type":37,"value":293},"Measurable capacity:",{"type":37,"value":295}," 6 hours of customer meetings per week = 4–5 calls on average. Beyond that, an SDR or account manager steps in.",{"type":32,"tag":33,"props":297,"children":298},{},[299,301,310],{"type":37,"value":300},"Roibase uses this structure in ",{"type":32,"tag":302,"props":303,"children":307},"a",{"href":304,"rel":305},"https:\u002F\u002Fwww.roibase.com.tr\u002Ffr\u002Fbranding",[306],"nofollow",[308],{"type":37,"value":309},"branding & brand identity",{"type":37,"value":311}," engagements too. A brand sprint runs in a 3-day block; customer workshops are Tuesday–Wednesday–Thursday morning slots. The founder does 1 hour prep + 2 hours workshop daily, all in the same context. Sprint ends, then 2 weeks of async comms, then the next sprint begins.",{"type":32,"tag":82,"props":313,"children":315},{"id":314},"response-time-sla-the-async-window-rule",[316],{"type":37,"value":317},"Response time SLA: the async window rule",{"type":32,"tag":33,"props":319,"children":320},{},[321,323,328],{"type":37,"value":322},"Communication outside meetings must be async. Define a ",{"type":32,"tag":45,"props":324,"children":325},{},[326],{"type":37,"value":327},"response window",{"type":37,"value":329},": for instance, 4 hours. A message received at 09:00 is answered by 13:00. One arriving at 15:00 gets a response the next morning at 10:00.",{"type":32,"tag":33,"props":331,"children":332},{},[333],{"type":37,"value":334},"Broadcast this window in your Slack status: \"Async mode — 4h response time.\" Teams adapt, clients adapt. Genuinely urgent work comes via Linear or phone (and the definition of urgent should itself be narrow—\"deploy today\" is urgent; \"is tomorrow's call okay?\" is not).",{"type":32,"tag":53,"props":336,"children":338},{"id":337},"time-block-discipline-commitment-and-measurement",[339],{"type":37,"value":340},"Time-block discipline: commitment and measurement",{"type":32,"tag":33,"props":342,"children":343},{},[344,346,351],{"type":37,"value":345},"Time-blocking is not just drawing boxes on a calendar. Every block is a ",{"type":32,"tag":45,"props":347,"children":348},{},[349],{"type":37,"value":350},"commitment",{"type":37,"value":352},"—you will do that work in that window. Work that cannot be committed does not enter a block; it waits in the backlog.",{"type":32,"tag":33,"props":354,"children":355},{},[356],{"type":37,"value":357},"Discipline rules:",{"type":32,"tag":359,"props":360,"children":361},"ul",{},[362,372,382],{"type":32,"tag":266,"props":363,"children":364},{},[365,370],{"type":32,"tag":45,"props":366,"children":367},{},[368],{"type":37,"value":369},"Block starts with clarity:",{"type":37,"value":371}," Not \"software development,\" but \"Linear #234 Stripe webhook integration.\" By block end, the task is complete or 80%+ done.",{"type":32,"tag":266,"props":373,"children":374},{},[375,380],{"type":32,"tag":45,"props":376,"children":377},{},[378],{"type":37,"value":379},"No overrun:",{"type":37,"value":381}," A 4-hour block is 4 hours. If it won't finish, it rolls to a different block tomorrow. Stretching blocks to 5–6 hours increases cognitive load and kills efficiency.",{"type":32,"tag":266,"props":383,"children":384},{},[385,390],{"type":32,"tag":45,"props":386,"children":387},{},[388],{"type":37,"value":389},"Weekly retrospective:",{"type":37,"value":391}," Friday afternoon, 30 minutes—which blocks held, where did interrupts happen, what will you fix?",{"type":32,"tag":33,"props":393,"children":394},{},[395,397,402],{"type":37,"value":396},"Measure: ",{"type":32,"tag":45,"props":398,"children":399},{},[400],{"type":37,"value":401},"block completion rate",{"type":37,"value":403},". Target 80%+. If you planned 20 blocks for the week, 16 should be fully done. Below 60% means your calendar, not your commitment, is miscalibrated—you're being too optimistic.",{"type":32,"tag":82,"props":405,"children":407},{"id":406},"the-discipline-of-blank-space-buffer-blocks",[408],{"type":37,"value":409},"The discipline of blank space: buffer blocks",{"type":32,"tag":33,"props":411,"children":412},{},[413,415,420],{"type":37,"value":414},"Do not fill the calendar to 100%. Leave at least 4 hours per week as ",{"type":32,"tag":45,"props":416,"children":417},{},[418],{"type":37,"value":419},"buffer blocks",{"type":37,"value":421},"—unplanned, for reactive work. Customer email, a bug surfaced in Linear, an urgent team question—these land in the buffer.",{"type":32,"tag":33,"props":423,"children":424},{},[425],{"type":37,"value":426},"Without buffer blocks, every interrupt eats into a deep work block. With buffer, you can say \"this goes in the buffer\" and protect deep work.",{"type":32,"tag":53,"props":428,"children":430},{"id":429},"async-first-culture-systemic-meeting-lessness",[431],{"type":37,"value":432},"Async-first culture: systemic meeting-lessness",{"type":32,"tag":33,"props":434,"children":435},{},[436],{"type":37,"value":437},"Async-first means \"treat synchronous communication as a last resort.\" At Roibase, a meeting request works like this:",{"type":32,"tag":262,"props":439,"children":440},{},[441,451,461],{"type":32,"tag":266,"props":442,"children":443},{},[444,449],{"type":32,"tag":45,"props":445,"children":446},{},[447],{"type":37,"value":448},"Open a Linear card first:",{"type":37,"value":450}," Write the topic, add context, list alternative solutions.",{"type":32,"tag":266,"props":452,"children":453},{},[454,459],{"type":32,"tag":45,"props":455,"children":456},{},[457],{"type":37,"value":458},"Async discussion:",{"type":37,"value":460}," Team comments on the card over 24 hours. Most issues resolve here.",{"type":32,"tag":266,"props":462,"children":463},{},[464,469],{"type":32,"tag":45,"props":465,"children":466},{},[467],{"type":37,"value":468},"Meeting:",{"type":37,"value":470}," Only if async didn't resolve it—then a 30-minute call. But the meeting must have a pre-written agenda (card linked).",{"type":32,"tag":33,"props":472,"children":473},{},[474],{"type":37,"value":475},"Result: Roibase averages 3 meetings per week across a 12-person team. Peer firms run 15–20 (Atlassian 2024 data). Time-blocking without async culture does not work—because every meeting breaks a block.",{"type":32,"tag":33,"props":477,"children":478},{},[479],{"type":37,"value":480},"The async response window is part of this: if an answer arrives in 4 hours, nobody suggests \"quick call?\" They write, wait, move on.",{"type":32,"tag":53,"props":482,"children":484},{"id":483},"closing-calendar-design-is-strategy-design",[485],{"type":37,"value":486},"Closing: calendar design is strategy design",{"type":32,"tag":33,"props":488,"children":489},{},[490],{"type":37,"value":491},"A founder's calendar reflects operational strategy. No deep work blocks on the calendar means no product\u002Fengineering strategy. No customer meeting cadence means your sales pipeline is reactive. No async window means your team culture is interrupt-driven.",{"type":32,"tag":33,"props":493,"children":494},{},[495],{"type":37,"value":496},"At Roibase, calendar design is part of onboarding. A new founder or lead joins and spends the first week building their own time-block structure, week two running a retrospective, week three hitting 80%+ block completion. This discipline has held for 8 years because it is measured.",{"type":32,"tag":33,"props":498,"children":499},{},[500],{"type":37,"value":501},"Look at your calendar for next week. How many 4-hour uninterrupted blocks? Which days cluster customer calls? What is your async response time? If you cannot answer, your calendar owns you, not the reverse. To fix it, start here: block one 4-hour window this week, protect it, measure it, repeat.",{"title":16,"searchDepth":503,"depth":503,"links":504},3,[505,509,512,515,518,519],{"id":55,"depth":506,"text":58,"children":507},2,[508],{"id":84,"depth":503,"text":87},{"id":95,"depth":506,"text":98,"children":510},[511],{"id":229,"depth":503,"text":232},{"id":240,"depth":506,"text":243,"children":513},[514],{"id":314,"depth":503,"text":317},{"id":337,"depth":506,"text":340,"children":516},[517],{"id":406,"depth":503,"text":409},{"id":429,"depth":506,"text":432},{"id":483,"depth":506,"text":486},"markdown","content:fr:lifestyle:founder-calendar-context-switching-time-blocking.md","content","fr\u002Flifestyle\u002Ffounder-calendar-context-switching-time-blocking.md","fr\u002Flifestyle\u002Ffounder-calendar-context-switching-time-blocking","md",1785967483203]