Every manager of a creative team has felt the pull. A deadline is close, nothing visible has changed for two days, and the instinct is to check in. Then check in again. Then ask for a quick update on the channel, a screen share, a status line in the tracker by end of day.

It feels like control. It is the opposite. Developers, designers, writers and product people do their best work in long, uninterrupted stretches of thinking. Every check-in breaks that stretch, and every request to show progress pushes people to produce something that looks like progress instead of something that is.

Activity is not output

Micromanagement measures the wrong thing. Hours online, messages answered, commits pushed and tickets moved are all activity. They are easy to watch and they say very little about whether the work is good, whether it ships, or whether it solves the customer’s problem.

Creative people notice when they are being judged on activity. The best ones leave. The rest learn to perform busyness, which is the most expensive habit a small team can pick up.

You cannot supervise someone into having a good idea. You can only agree what good looks like and make room for them to get there.

Trade supervision for commitments

The alternative is not to look away. It is to move the conversation from how people work to what they will deliver, and to write it down.

  • Agree a small number of clear commitments in each one-on-one: what will exist in two weeks that does not exist today.
  • Let the person decide how and when they do the work in between.
  • Ask for evidence at the next review, not a running commentary: the demo, the design, the document.
  • Mark each commitment done, partly done or missed, talk about why, and carry what is open into the next fortnight.

This gives the manager more certainty than daily check-ins ever did, because the record is specific and it accumulates. After three or four reviews you can see who reliably delivers, where work gets stuck and which commitments were unrealistic from the start.

Add a checkpoint, not a camera

Two weeks is a long time when something is going wrong. A single checkpoint halfway through the cycle catches most problems early: on day six, show a working piece, an early draft or a pull request. One agreed moment replaces the dozens of interruptions that micromanagement creates.

What managers get back

Managers who stop supervising get their own time back, and their one-on-ones change character. Instead of reconstructing what happened, the meeting starts from a shared record and moves straight to what matters: what is next, what is in the way and what support is needed.

That is the idea behind Tenellus. Every commitment is kept on the books, so trust is earned in the open and nobody needs to be watched to be accountable.