<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Ishatization]]></title><description><![CDATA[Ishatization]]></description><link>https://ishatization.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Tue, 17 Nov 2026 18:21:53 GMT</lastBuildDate><atom:link href="https://ishatization.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Why I Finally Stopped Answering “Who’s Free Next Week?” With a Guess]]></title><description><![CDATA[What I learned building a real capacity planning habit for my team There’s a question every manager dreads because the honest answer requires so much…]]></description><link>https://ishatization.hashnode.dev/why-i-finally-stopped-answering-who-s-free-next-week-with-a-guess</link><guid isPermaLink="true">https://ishatization.hashnode.dev/why-i-finally-stopped-answering-who-s-free-next-week-with-a-guess</guid><category><![CDATA[Productivity]]></category><category><![CDATA[SaaS]]></category><category><![CDATA[Time management]]></category><dc:creator><![CDATA[Nusrat Jahan Ishat]]></dc:creator><pubDate>Wed, 03 Jun 2026 10:23:18 GMT</pubDate><content:encoded><![CDATA[<p><em>What I learned building a real capacity planning habit for my team</em></p>
<p>There’s a question every manager dreads because the honest answer requires so much effort to produce: “Can we take on this new project next week?”</p>
<p>For years, answering that question involved a combination of Slack messages, calendar spelunking, and gut instinct. I’d ask around, get a rough sense of who seemed busy, and then make a commitment based on optimism rather than data. Sometimes it worked out. Sometimes it didn’t — and the team paid for it with a brutally overloaded week they could see coming but couldn’t flag in time.</p>
<p>The problem wasn’t the team. It was that there was no single place to look.</p>
<p><strong>Planning Ahead Sounds Obvious. Doing It Well Isn’t.</strong></p>
<p>There’s a meaningful difference between knowing “someone is assigned to Project X” and knowing “Alice has 6 hours allocated on Tuesday and is free for 2 hours on Thursday.” The first is a vague awareness. The second is actionable.</p>
<p>Capacity planning, done properly, gives you the second kind of view. It tells you not what people are nominally working on, but how their time is actually distributed across the week — before the week happens.</p>
<p><strong>How I Plan the Team’s Week Now</strong></p>
<p>My current setup is a weekly and monthly scheduler in UnitLook where I can see every team member’s upcoming work on a single screen. On Monday morning (or ideally Friday afternoon the week before), I open the view, look at who has what planned, and assign any unallocated work for the coming week.</p>
<img src="https://cdn.hashnode.com/uploads/covers/6a1ffd8a957dc1be404d520c/a4f613fb-450a-4edb-8eb6-8b0f5a8876d9.webp" alt="Weekly scheduler — overview of planned work by employee" style="display:block;margin:0 auto" />

<p>The mechanics are simple: click on a day, select the person, enter the project or task and the expected hours. The entry appears as a block in their schedule. They see it immediately in their own view — no separate notification needed, no forwarded email with “please see below.”</p>
<p>The whole team knows what the week looks like. So do I.</p>
<p><strong>The Feature I Didn’t Know I Needed: Overload Detection</strong></p>
<p>Here’s the planning mistake I made more than once: I’d assign work to someone without realising they already had a full day booked. I wasn’t trying to overload them — I genuinely didn’t have visibility into what they already had.</p>
<p>The fix I’ve come to rely on is an automatic capacity alert. When the total planned hours for someone on a given day exceeds their daily limit (typically 8 hours, but adjustable per person), a red indicator appears on their schedule row. I see it immediately, before I’ve committed to anything with a client or stakeholder.</p>
<p>It sounds like a small thing. It isn’t. Catching an overload in the planning stage means I can redistribute the work, push the timeline, or have an honest conversation. Catching it on Wednesday when the person is already underwater means damage control.</p>
<p><strong>Closing the Loop: Planning + Time Tracking Together</strong></p>
<p>Planning in isolation tells you what you intended. Time tracking in isolation tells you what happened. Together, they tell you something more interesting: the gap between the two, and whether that gap is getting smaller over time.</p>
<p>My workflow now runs as a loop:</p>
<blockquote>
<p>Plan the week: assign work and allocate hours</p>
<p>Execute: team works and logs actual time as they go</p>
<p>Review: compare planned vs. actual to refine next week’s estimates</p>
</blockquote>
<p>When someone logs hours on a project they were assigned to in the planner, the entries are automatically matched. There’s no manual reconciliation at the end of the week. The comparison view is just there.</p>
<p><strong>Who This Matters Most For</strong></p>
<p>In my experience, three kinds of teams benefit most from getting capacity planning right:</p>
<p>-&gt; Teams juggling multiple projects simultaneously, where the bottleneck is usually invisible until it’s too late</p>
<p>-&gt; Service companies billing by the hour, where knowing whether you’re available for a new engagement has direct revenue implications</p>
<p>-&gt; Managers who want to protect their team’s focus, not just fill their calendars</p>
<p><strong>Getting Started: Lower the Bar</strong></p>
<p>The advice I’d give anyone starting with capacity planning: don’t try to plan everything perfectly in week one. Start with one week. Spend 15 minutes on Monday blocking out the team’s major assignments. See how it compares to reality by Friday.</p>
<p>The value isn’t in the perfect plan — it’s in having a plan at all, so that deviations are visible and learnable. Over time, your estimates get better. Your commitments get more reliable. Your team gets fewer “can you stay late, sorry” moments.</p>
<p><em>The answer to “who’s free next week” stops being a guess. That’s the whole point.</em></p>
]]></content:encoded></item></channel></rss>