{"id":1399,"date":"2026-11-18T09:20:00","date_gmt":"2026-11-18T09:20:00","guid":{"rendered":"https:\/\/bhaso.com\/blog\/?p=1399"},"modified":"2026-11-18T09:20:00","modified_gmt":"2026-11-18T09:20:00","slug":"small-team-energy-matched-workday","status":"publish","type":"post","link":"https:\/\/bhaso.com\/blog\/small-team-energy-matched-workday\/","title":{"rendered":"How a Four-Person Team Matched Tasks to Energy Levels"},"content":{"rendered":"<p>Business technology advice usually arrives as a list of platforms to buy. This article takes a different route: a composite story about a small software-services team that stopped trying to squeeze more hours out of its week and instead began matching tasks to energy levels. The company, the people and the numbers here are illustrative; the situation, however, will look familiar to any group of professionals who run on laptops and deadlines.<\/p>\n<h2>The setting: a four-person product team under strain<\/h2>\n<p>Picture a team of four building an internal reporting tool for a mid-sized distributor. There is a product owner, two developers and an operations analyst. Their calendar was dense with meetings scattered through the whole day, and the backlog kept growing. Everyone was working long hours, yet the product owner noticed that the most important design questions were always answered badly, usually late in the afternoon.<\/p>\n<p>The analyst, who kept the team&#8217;s task board, proposed an experiment. For two weeks, each person would record, three times a day, how alert they felt. No one would change their workload yet. The goal was only to see whether alertness followed a pattern that the team could plan around.<\/p>\n<h2>What the two weeks of notes revealed<\/h2>\n<p>The data was unglamorous but clear. One developer thought most sharply in the early morning and faded steeply after lunch. The other developer was the opposite, slow to start and strongest from mid-afternoon into the evening. The product owner peaked mid-morning. The analyst was steadiest across the day but dipped visibly in the early afternoon, as did most of the group.<\/p>\n<p>Three observations shaped what happened next:<\/p>\n<ul>\n<li>Meetings were consuming the strongest hours for three of the four people, because stand-ups and reviews had been scheduled when the room was free rather than when people were sharp.<\/li>\n<li>The routine work, such as updating tickets, bumping dependency versions and cleaning up test data, was being done in the same windows as the hardest design thinking, simply because the board listed tasks in the order they had been created.<\/li>\n<li>Most defects found in review came from work done in the personal slump of whoever wrote it.<\/li>\n<\/ul>\n<h2>The change: a two-column board<\/h2>\n<p>Rather than adopt a new tool, the team altered how it read its existing board. Each card received one of two tags, <em>sharp<\/em> or <em>steady<\/em>. Sharp cards were tasks that required invention or careful judgement: designing a data model, untangling a reconciliation bug, writing a tricky migration. Steady cards were jobs that could be completed on partial attention: ticket grooming, documentation touch-ups, routine upgrades and chasing approvals.<\/p>\n<p>Each person then listed their own strong hours and weaker hours on a shared page. When picking up work, they drew from the sharp column during strong hours and the steady column during weaker ones. The early-bird developer owned morning design work; the late-riser took over code review in the afternoon, a task that rewards patient reading. Meetings were consolidated into the narrow slot where all four had at least moderate focus, and the rest of the day was left for individual work.<\/p>\n<h2>Results the team could actually point to<\/h2>\n<p>The team did not publish dramatic claims, and neither should this article. What the members reported was modest and specific. Reviews went faster because the right person read the right code at the right time. The product owner stopped making big scoping decisions at the end of the day and began making them mid-morning, with fewer reversals the next week. The analyst noticed that routine upgrades, once dreaded, were completed almost without comment when placed in the post-lunch dip.<\/p>\n<p>There were costs, too. The team had to be honest about its own rhythms, and that took some trust. One developer admitted he was far less productive before ten than he had pretended. Another found that his preferred schedule clashed with a client&#8217;s reporting window. These conflicts were resolved by trading shifts of work, not by abandoning the idea.<\/p>\n<h2>An example day before and after<\/h2>\n<p>Before the experiment, the product owner&#8217;s Tuesday looked like this: a status meeting at nine, a vendor call at ten-thirty, a backlog review after lunch, and a scoping decision squeezed in at four, when attention had thinned. After the change, the status meeting moved into the shared window, the vendor call became a short asynchronous exchange, and the scoping decision was given the mid-morning hour that used to vanish into calls. The backlog review, a task that mostly involves reading and sorting, slid into the early-afternoon dip where it fits comfortably.<\/p>\n<p>For the operations analyst, the shift was subtler. Reconciling the distributor&#8217;s weekly exports against the reporting tool is delicate work, since one misplaced column can ripple through every chart. It moved to the analyst&#8217;s steadiest block, while formatting the output and emailing the summary moved to the end of the day. Nothing about the tasks changed; only the order did.<\/p>\n<h2>Objections the team raised<\/h2>\n<p>Not everyone was convinced at first. One developer worried that labelling tasks would turn into micromanagement. The team answered by keeping the tags self-assigned: each person decided for themselves what counted as sharp work. Another member feared that clients would see the shared meeting window as inflexible. In practice, clients cared far more about reliable replies than about the precise hour, and the team simply published its window so expectations were clear.<\/p>\n<h2>How this connects to planning for growth<\/h2>\n<p>The story also illustrates a broader point about digital growth. Teams often plan capacity in headcount and hours, but capacity also has a quality dimension: the same hour of work carries different value depending on who does it and when. A planning conversation framed around <a href=\"https:\/\/bhaso.com\/blog\/driving-success-how-bhaso-com-powers-digital-growth-planning\/\">how a business maps out its digital growth<\/a> should therefore include a question that rarely appears on a roadmap: which of our tasks need our sharpest people at their sharpest?<\/p>\n<p>The same applies to money. The finance-minded reader may recognise that wasteful hours, like leaking spending, are easier to spot once tracked. Our related discussion of <a href=\"https:\/\/bhaso.com\/blog\/mastering-modern-cash-flow-how-to-spot-spending-leaks-protect-digital-payments-and-extend-runway\/\">finding spending leaks and stretching a company&#8217;s runway<\/a> uses a similar mindset, only with cash rather than attention as the scarce resource.<\/p>\n<p>And for teams still deciding how to structure product work, the piece on <a href=\"https:\/\/bhaso.com\/blog\/strategic-insights-for-product-led-growth-maximizing-success-with-bhaso-com\/\">building growth around the product itself<\/a> offers a useful frame for deciding which work deserves the premium hours.<\/p>\n<h2>A note on civic life, kept brief<\/h2>\n<p>Professionals often juggle community concerns alongside their jobs. One example of an online venue for that is <a href=\"https:\/\/janboard.com\/\">JanBoard, an independent site that lets residents file appeals, visible to the public, to elected representatives and public offices<\/a>, and which states plainly that it is not a government site. Whatever the venue, the energy principle holds: draft a careful message when your mind is clear, and leave tidy-up work for a quieter hour.<\/p>\n<h2>Lessons to carry into your own team<\/h2>\n<ol>\n<li><strong>Measure before changing.<\/strong> Two weeks of simple notes beat any assumption about who works best when.<\/li>\n<li><strong>Label the work, not the people.<\/strong> A card is sharp or steady regardless of who picks it up; the person&#8217;s rhythm decides when.<\/li>\n<li><strong>Move meetings deliberately.<\/strong> Group them into a shared window instead of letting them scatter through peak hours.<\/li>\n<li><strong>Review at the right time.<\/strong> Code, contracts and copy should be checked by someone who is alert, not merely available.<\/li>\n<li><strong>Revisit quarterly.<\/strong> Rhythms shift with seasons, workloads and life events, so the map needs refreshing.<\/li>\n<\/ol>\n<h2>Where the story leaves the team<\/h2>\n<p>Six months on, the composite team still keeps its two-tag board. The tags have become shorthand in conversation: someone will say that a task is &#8220;steady&#8221; and everyone understands that it can wait for the afternoon. The meetings are shorter, the backlog is no smaller, but the team reports that the work feels less like a scramble. That change in feel is, in the end, what matching tasks to energy offers: not more hours, but better use of the ones you have.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A composite story of a small product team that tagged work as sharp or steady and scheduled it around each person&#8217;s real peaks and dips.<\/p>\n","protected":false},"author":6,"featured_media":1400,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[166],"tags":[],"class_list":["post-1399","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-business-technology"],"_links":{"self":[{"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/posts\/1399","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/comments?post=1399"}],"version-history":[{"count":1,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/posts\/1399\/revisions"}],"predecessor-version":[{"id":1485,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/posts\/1399\/revisions\/1485"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/media\/1400"}],"wp:attachment":[{"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/media?parent=1399"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/categories?post=1399"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/tags?post=1399"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}