How One Small Team Fixed Drift by Rereading Goals Each Month

How One Small Team Fixed Drift by Rereading Goals Each Month

Nobody in this tale exists, yet the situation will ring true for many small business teams. It follows a team of five who ran a modest online service and, like most groups, wrote down their goals at the start of each year. The interesting part is not the goals themselves but what happened to them: nothing. They sat in a shared document, untouched, while the business around them changed. The case study below shows how a monthly goal reread, a plain sit-down of under an hour, repaired that quietly.

The situation: a goals document nobody opened

At the start of the year the team had agreed on six goals. Two concerned customer growth, one concerned an internal tool migration, one concerned a content calendar, one concerned hiring a part-timer, and one was a vague promise to “improve operations”. Everyone nodded, the document was saved, and work resumed.

By spring, the team lead noticed an odd pattern. People were busy, yet when asked what they were working toward, answers differed. The designer was polishing pages for the content calendar. The developer was fixing a migration that, it turned out, the company had half decided to cancel. Nobody was being lazy. They were each following a goal that had been true in January and was only partly true now.

The turning point: one awkward meeting

The trigger was a short review where the team lead projected the original document on a screen and read the goals aloud. Silence followed. Two of the goals plainly no longer made sense, because a supplier change had removed the reason for the migration. Another goal depended on a hire that had been postponed. The team lead did not scold anyone; they simply asked, “Which of these would we write again today?”

Only three of the six survived that question. The group agreed on a rule right there: on the first working Monday of every month, they would reread the goals together and sort each into keep, adjust or drop. No slides, no scoring, a fixed forty-minute limit, and one person taking notes.

Month one: the first reread

The first session was clumsy. People argued about wording, and the vague operations goal ate ten minutes. But the structure held. The migration goal was dropped, with a short written reason so nobody would wonder later. The hiring goal was adjusted from “hire a part-timer” to “decide whether a part-timer is needed by the end of next quarter”, which matched reality much better. The content calendar was kept as it stood.

The note-taker recorded one extra line at the bottom: what had changed since the last reading. That line became the habit’s memory. By month three it read like a small diary of the business, covering a supplier switch, a quiet season, and a new customer segment.

Month three: the payoff

By the third reread, something practical had shifted. The team stopped starting work that had no living goal behind it. When a request arrived, someone would ask, “Which goal does this serve?” and if no goal fit, they either added one at the next reread or declined the request. The developer reported, with visible relief, that the week had fewer surprise reversals.

The team also found it easier to talk about priorities with each other. Because everyone had read the same list within the same month, there was no private version of the plan living in someone’s head. When the designer and the developer disagreed about sequencing, they reopened the list instead of arguing from memory.

Where the team looked for ideas

Rereading goals is a good time to ask whether something new belongs on the list. The team kept a loose habit of reading widely during that session. One member brought in a post about choosing technology solutions for a growing business, and it prompted a useful question about whether their tool goals matched their size. Another brought a piece on joining web, cloud and intelligent tools for growth, which they treated as a prompt rather than a plan.

A third member, who dabbled in aviation as a hobby, mentioned that the website of an online learning platform for aviation professionals, AirCrewU, presents itself as an independent platform. Nothing was adopted from that site. It merely illustrated a point they liked: be honest in writing about what a document does and does not claim, including your own goals.

What the team did differently afterward

Over the following months the group refined the routine. These are the changes that stuck:

  • Fewer goals. The list shrank to four. A longer list simply made the reread slower and the discussion shallower.
  • Each goal got a plain-language test. Could a new colleague read the sentence and know what to do on Monday? If not, it was rewritten.
  • Dropped goals went into a short archive. The note-taker kept them in a separate section, so revisiting a dropped idea was easy and nobody felt a drop was permanent.
  • One owner per goal. Not a boss, just the person who spoke first about it at each reread.

Setbacks and slips

Not every month went well. During month four, a manager from another department sat in and tried to turn the reread into a status report, with progress bars and percentages. The meeting ran long and the energy fell. The team lead steered back: the reread asks only whether each goal still fits, not how far along it is. Progress belongs elsewhere, in the weekly routine the team already had.

In month five the session was skipped because of a deadline, and the following month two goals had silently gone stale again. The team treated that as data. The reread is cheapest when it is regular, and the cost of skipping it is paid back with interest in confusion. They moved the session to a time that deadlines rarely touched.

Why the small size helped

A team of five has an advantage here: everyone can fit around one table, and a decision made at the reread takes effect by lunchtime. Larger organisations can still borrow the idea by running the session per team rather than company-wide. The principle scales down gracefully, because the only real requirement is that the people doing the work are the same people reading the list. When the authors and the readers are different groups, goals tend to harden into slogans.

The practical lesson

The lesson for a small business is unglamorous. Goals are guesses made on a certain date. Circumstances shift, suppliers change, people leave, and customers behave differently than predicted. A monthly reread is a cheap way to notice the gap before it widens. It does not require software or a consultant, only a list, a calendar slot and the willingness to say, “We would not choose this today.”

How to copy the routine

If you want to try this with your own team, start small. Pick the first working Monday of next month, set a timer for forty minutes, and bring the current goals list. Read each goal aloud. For every one, ask whether you would write it again today, and sort it into keep, adjust or drop. Record the reason for each drop and one line about what has changed in the business. Close the meeting when the timer rings, however lively the debate.

After three months, look back at the notes. Most teams find that the notes tell a clearer story of their business than any formal report, and that fewer people are working on goals that quietly expired. That, more than any dramatic reset, is what makes the habit worth keeping.