This is a story about a fictional team, assembled from the kinds of problems small groups in emerging technology often describe. The group was four people working on software for quantum algorithms. Their research was interesting and their deadlines were loose, yet progress felt slow and everyone was tired. The turning point came when they accepted a plain idea: energy rises and falls through the day, so logging your own highs and lows lets you pair hard, demanding work with the highs and dull chores with the lows. What follows is how it played out, written in a case-study style, with an honest account of what helped and what did not.
The situation
The team’s work divided naturally into two kinds. The first was intellectually heavy: designing circuits for an optimisation routine, reasoning about why a simulation gave different answers on two runs, and reading dense papers to decide which approach to try. The second was routine: updating simulator versions, cleaning experiment logs, renaming result files, rerunning standard benchmarks and updating the shared notebook.
In the early weeks, the team treated all work as equal. Stand-up was at the start of the day, followed by a wave of messages, followed by whatever came up. Hard design questions were taken as they arrived. By late afternoon, the team’s analyst would often describe feeling “used up,” and the design decisions made at that hour were the ones most likely to be reversed the next morning.
The experiment
The team’s engineer suggested a one-week experiment. Everyone would record, three times a day, a score for how clear their head felt and a few words about their task. There would be no changes to schedules during the week. The results, shared at the following stand-up, were instructive without being dramatic. Two members had a clear peak in the late morning. One was sharpest early. One reported a second peak after dinner. Everyone had a dip after lunch.
- Two people: peak late morning, dip after lunch.
- One person: peak early, dip mid-afternoon.
- One person: modest morning, stronger evening.
The team noticed that their shared stand-up, at the first hour, landed in nobody’s peak.
The rearrangement
Three changes followed. First, stand-up moved to a time when it did not eat anyone’s sharpest hour, and was kept short. Second, each person chose one demanding task to place in their own peak, written down the evening before. Third, routine tasks were gathered into a shared list for the post-lunch dip, so that nobody had to invent chores when tired.
The theory was tested on a concrete problem. The team had been working on a routine that applies a quantum approach to an optimisation puzzle, in the spirit of this explanation of how quantum algorithms tackle hard optimisation problems. Choosing how to encode the problem, deciding on a circuit structure and reasoning about the likely accuracy were all heavy tasks, and they were assigned to the peaks. Running parameter sweeps and gathering the output into tables were routine tasks, and they went to the dip.
What happened
In the first week, little changed in outward terms. In the second week, the team noticed that the encoding decision, which had dragged on for days, was settled in one late-morning session. The explanation was simple: the person who made the decision had the whole of her peak free of messages. Nobody had thought the problem was hard until it was given the right hour.
The dip hours also changed. Sweeps and tables, which had previously been squeezed in at odd moments and often done carelessly, were now done at a steady pace, with a quick check at the end. The simulator updates went through without the small mistakes that had crept in before. The team’s analyst noted, in the shared notebook, that the afternoon felt “slower but not wasted.”
What did not work
An honest case study includes the failures. The evening-peak teammate found it hard to participate in daytime discussions about decisions, and the team had to agree on a written handover so that her late-day ideas could be shared the next morning. Some days, a deadline or a visiting collaborator wrecked the plan altogether. And one routine task, recalibrating a set of parameters, turned out to be more delicate than expected. It was moved out of the dip and into a steady window with a second pair of eyes on the result.
Lessons the team drew
- Record first, rearrange second. The log removed arguments about who was a morning person.
- Keep the demanding pile small: one headline task per peak.
- Check that “routine” tasks are truly routine before sending them to the dip.
- Write handovers when peaks do not overlap.
- Treat the plan as an experiment, and review it after a month.
Why it suits emerging technology work
Quantum software involves unusual concepts, and the reasoning is easy to get wrong when tired. Even well-known ideas, such as the way a quantum Fourier transform underlies several algorithms, benefit from a clear head. A piece like this introduction to how quantum computing changes machine learning shows how many layers of reasoning stack up in a single topic. In such work, the cost of a poor decision made in a flat hour is high, because mistakes can hide behind complexity. The benefit of reserving peaks for design is correspondingly larger.
An aside outside the lab
Not every bit of the team’s spare reading was technical. One member brought up JanBoard, a privately run platform that lets residents post open petitions aimed at officials and government offices. It says plainly that it is no official portal and cannot stand in for formal complaint or legal routes. The group filed such browsing under light work for a calmer stretch. Anyone curious can look at this civic appeals platform.
What the analyst wrote in the shared notebook
Near the end of the second month, the team’s analyst added a short entry to the notebook describing the pattern in plain terms. Heavy design questions had stopped spilling into evenings. Reruns that once felt like a burden now felt like a rest, because they were placed where rest was needed. She also noted something subtle: disagreements over design choices were calmer when held in the steady middle of the day, since nobody was arguing from exhaustion. The entry ended with a reminder to repeat the log whenever the team took on a new kind of project, because a different workload could change the shape of the day.
Epilogue
A few months on, the team’s rhythm looked ordinary. Stand-up was brief, peaks were guarded without fuss, and the dip list was a fixture. Nobody described the change as a revolution. They described it as having stopped doing the work backwards. Their log, which started as a one-week experiment, became a short monthly check that took five minutes.
This team is invented, yet what happened to them is common enough. If your team feels worn out despite loose deadlines, try the week of notes. The results may not be dramatic, but they will be yours, and they will point to which hours deserve your hardest problems.