Choose focus length for real client work

Step 1: Name one reviewable deliverable The classic twenty-five minute Pomodoro is a teaching default, not a law for client work. A focus block is a timed promise to one named deliverable. The useful question is whether you produced something a client can review. "Draft the pricing section" can be reviewed. "Work on the proposal" cannot. If you cannot picture the file that will exist when the block ends, you have a topic, and topics expand until the day is gone. Home boundaries for that first block sit in protect focus when you work from home. The day that surrounds the blocks sits in structure a remote workday. When the setup cost makes twenty-five minutes the wrong tool, the arithmetic is in when a 25-minute Pomodoro is too short. Example, assumptions stated. The primary deliverable is a draft of the pricing section in a client proposal, reviewable by 13:00. You are not designing the whole proposal. You are producing options a client can mark up. TimeBlockWhat the block is for09:00 to 09:4545 minutesOutline pricing options A and B, including the constraints09:50 to 10:00BreakStand up. Do not open chat10:00 to 10:4545 minutesWrite option A with sample numbers10:50 to 11:05Sweep15 minutes in the client channel11:10 to 11:5545 minutesWrite option B and the recommendation12:00 to 12:2525 minutesPaste into the shared doc and write one decision question Evidence at 12:25 is a shared-doc link and one clear ask. Three 45-minute blocks are 135 minutes, plus a 25-minute paste, which is 160 minutes aimed at one section. The morning from 09:00 to 12:25 is 205 minutes of clock time. About 45 minutes went to the break and the sweep. Protect the first two blocks. In the example the sweep is at 10:50, after two drafting blocks, and it ends. Log the blocks. Stop when the stop condition is met. Extra unpaid polishing is scope leak. Step 2: Price the block length from setup time Match the length to the cost of starting, not to a streak you want to keep. WorkLength to tryWhy this lengthBug triage or mail triage15 to 25 minutesFeedback is fast and setup is cheapWriting, design, or coding40 to 50 minutesRebuilding context is expensiveA meetingDo not time the meeting as a blockTimebox the agenda insteadAdmin and invoicing25 minutesThese tasks invite over-polishAn estimate or a proposal section25 to 40 minutesName the section, not "the proposal"Debugging50 to 90 minutesEvery ping forces a rebuild If setup costs eight minutes or more every time you restart, a twenty-five minute block is training you to quit during the useful part. Lengthen to 40 or 50 minutes. For hard debugging, lengthen toward 90. Do not abandon structure and call the rest of the day "flow." Run the setup tax with stated assumptions. Reopening the file, finding the sentence, and rebuilding the model takes 8 minutes. A 25-minute block with one setup leaves 17 minutes of work. The work ratio is 17 divided by 25, which is 68 percent. A chat ping that forces a second setup inside the same block burns another 8 minutes. You then have 16 minutes of setup and 9 minutes of work. The work ratio falls to 9 divided by 25, which is 36 percent. You "did a Pomodoro" and produced a paragraph. A 50-minute block with one setup leaves 42 minutes of work. The work ratio is 42 divided by 50, which is 84 percent. Same person, same task, different length. Now scale it to a real drafting need. Assume you need 180 minutes of actual writing, not 180 minutes of clock time. On short blocks at 17 minutes net, 180 divided by 17 is about 10.6 blocks. Call it 11. Each cycle is 25 minutes plus a 5-minute break, so 30 minutes. Eleven cycles are 330 minutes, which is 5 hours and 30 minutes of clock time, for 11 times 17, or 187 minutes of writing. On long blocks at 42 minutes net, 180 divided by 42 is about 4.3 blocks. Call it 5. Each cycle is 50 minutes plus a 10-minute break, so 60 minutes. Five cycles are 5 hours of clock time, and 5 times 42 is 210 minutes of writing. You spent less clock time and got more drafting than the short-timer plan. The short timer carries more setup. Use 25 minutes for triage and invoicing. Change the default for drafting and debugging. The longer treatment is in when a 25-minute Pomodoro is too short. Stand up on the break. Match the break to the block so the recovery is real and the chat stays closed. Block lengthBreak15 to 25 minutes3 to 5 minutes, standing, water40 to 50 minutes8 to 12 minutes, no chat90 minutes of debugging15 minutes away from the screen Stand up and leave chat closed. Count blocks against the hours on your real calendar. Decide when the timer stays, lengthens, or goes away The timer is a boundary. When the work is already bounded, a second clock is noise. SituationChoiceNamed deliverable, quiet morningKeep the timed blocksSetup costs eight minutes or more at every restartLengthen to 40 or 50 minutes, or 90 for hard debuggingPairing, or a conversation that has to stay continuousSkip the timer and timebox the agendaExploration with no delivery targetSkip the timer and set a stop conditionA day packed with meetingsOne short delivery block in the longest gapIncident responseSkip the timer. It will only add noise Label exploration when you skip the clock. "Stop when three headline options are written" is a stop condition. "Work on the brand until I am tired" is not. You can do untimed work. You still need an end that is not exhaustion. If the named deliverable is blocked mid-block, stop. Waiting on a client, a wrong environment, or missing access will not improve if you stare at the remaining minutes. Write one park line with the next action and the blocker, then switch to an item on the waiting list. Do not spend the rest of the tomato on fake motion. Start a new named block when the unblock arrives. Before you mark a block complete, check for a reviewable artifact or a park note. If neither exists, the block was motion. Put morning triage in a short window or after the first deep block, not in an open-ended warm-up. Example, assumptions stated: calls at 09:30, 11:00, and 14:00, and the longest open stretch is 13:00 to 13:40. Use that 40 minutes for one named slice. If no gap reaches 25 minutes, say so in the status note and move the deliverable. Step 3: Park the thread before you switch clients Several clients multiply switching cost. It shows up as reopened files and half-written replies, which is what real cost of context switching is about. Batch one client's deep blocks before you open another's chat. Do not alternate every twenty-five minutes because badges arranged the day. When you switch, park the current block in one line: next action, and the open question. Change the task label first. Keep an "up next" list of at most five items. Do not switch mid-block for curiosity. Example park note, assumptions stated: "Proposal: next is to paste option B numbers. Open question is the client's discount cap." That line is enough to restart without rereading the morning. Price the switches. Assume re-entry costs 12 minutes. That 12 is a planning figure. Replace it with a sample you time yourself, on a normal morning, from "I opened the other project" to "I am editing again." Four client switches in a morning, at 12 minutes each, are 48 minutes. That is almost two short blocks spent remembering where you were. Two switches, because you batched client A for two blocks and then moved once to client B, cost 24 minutes. You bought back 24 minutes, which is another 25-minute block or half of a 50-minute drafting block. If the day is mostly switching, shrink the plan. One primary outcome, one secondary outcome, one communication window. Four clients can still mean one primary client for deep work that day, not four partial depths. Example, assumptions stated, a four-client Tuesday. Client A gets two morning blocks. Client B gets one after lunch. Client C gets a 15-minute sweep. Client D gets a status note, and blocks tomorrow. Replies all morning and a heroic evening mean you never chose a primary. If you promised eight blocks and the calendar holds five, renegotiate while the week can still absorb it. You do not owe yourself unpaid evening blocks. Pair the log with end-of-day status updates when a client expects a daily note. The status is the public evidence. The block count stays in your log. Step 4: Budget blocks before you promise a date Rough-count blocks before Monday so you do not promise a Friday delivery that needs twelve unnamed hours. DeliverablePlanning questionA 1,500-word postHow many 45-minute drafts, plus one edit block?Landing-page copyIs it one block per section?A bug fixDo you need a repro block, a fix block, and a verify block?A proposalOutline block, numbers block, polish block: which of these is the promise? Example, assumptions stated. The client wants a six-section proposal by Thursday. You estimate 8 blocks of 40 minutes. That is 320 minutes of timed work, or 5 hours and 20 minutes, before breaks. The calendar shows 5 free blocks. Five times 40 is 200 minutes. You are short 120 minutes, which is three more 40-minute blocks. Compare free blocks with the estimate. Five divided by eight is 0.625, or 62.5 percent. If free blocks are under about 70 percent of the estimate, renegotiate the date or the scope before you start pretending. Seventy percent of eight blocks is 5.6. You have 5, so you are under the line. On Tuesday, not on Thursday night, move the delivery to Monday or cut the promise. If one section is one block, five free blocks might be an outline, three sections, and a paste into the shared doc. Promise three sections, not six. Say that on Tuesday, while the client can still choose which three matter. Map the week so the blocks have a home. DayDefaultMondayEstimate blocks for the week's primary deliverables. Protect the morning for the primary clientTuesday to ThursdayMorning blocks for deep delivery. Client chat twice in the dayFridayWrap-up blocks, invoicing, and parking notes for next week If a client breaks the first blocks with quick calls, move those calls to a standing afternoon window and say so in writing. When the hours you can sell and the rate you quote diverge, go back to calculate a freelance hourly rate. Weekly outcomes sit in plan a week of remote work. Example, assumptions stated, a mixed full day at the lengths from step 2. WindowLengthOutcome08:30 to 09:2050 minutesFixed-fee milestone: flow A wireframe09:30 to 10:2050 minutesFlow A annotations and open questions10:30 to 10:5525 minutesRetainer: triage tickets A, B, and C11:00 to 11:2525 minutesClient mail, inside the published window13:00 to 13:5050 minutesFixed-fee work: flow B14:00 to 14:2525 minutesInvoice line and park notes for tomorrow Three 50-minute blocks are 150 minutes. The three short blocks are 75 minutes. Timed work is 225 minutes, or 3 hours and 45 minutes, before lunch and the gaps. Sixteen short timers would be 16 times 25, which is 400 minutes, and this calendar does not hold that. Quote the day you can actually hold. Five-line block plan template