The work nobody hired you to do

Every May 1st we mark a history of people demanding better conditions. The 8-hour day. Fair pay. The right not to be worn down by work that never ends.

The modern version is quieter. It shows up as a Friday afternoon reconstructing where the week went, a Monday chasing approvals that should have closed Tuesday, a project postmortem where the hours don't match the invoice and nobody's quite sure why.

Most growing teams have accepted this as part of the job, but it doesn't have to be.

Your team is busy. But busy doing what?

There's the work you were hired to do, and then there's everything around it. The proposal, the campaign, the client call. That's visible work.

Then there's the other stuff. Chasing a timesheet. Pulling numbers from one tool into another. Sending the same approval request twice because the first one got buried in an email. None of it shows up on an invoice, and all of it takes time.

The 4 places friction hides

1. Tasks without a home

When reminders are how work moves forward, it usually means tasks are scattered across email, Slack, and a project tool that not everyone opens every day. Nothing is lost exactly, it's just nowhere reliable. So someone has to chase, and chasing becomes part of the job description.

2. Approvals that require three tabs

A leave request should take 30 seconds. It takes longer when the request lives in one place and the team calendar is somewhere else entirely. The manager has to piece it all together before giving an answer, and by the time they do, two or three follow-up messages have already been sent.

3. Time logged from memory

Most people don't log hours as they work. They batch it on Friday afternoon, or Sunday evening before the week starts, pulling together what they can remember.

The hours get logged, but what gets logged is a rough reconstruction. Over a month, across a team, those gaps quietly distort project margin and client invoices in ways that are hard to trace back to anything specific.

4. Reports assembled by hand

At the end of the month, someone needs to know how things went. That information exists, spread across the project tool, the time tracker, the spreadsheet, and the finance system. Pulling it into something coherent takes a few hours, and by then the decisions it should have informed have already been made.

It compounds as you grow

At five people, informal coordination works. You see the team, you catch things early. The wheels come off somewhere between 12 and 20 people, when the team is too big for informal coordination but too small to justify a dedicated ops hire.

So the director does it. The same person running client relationships and business development is also the one tracking who has the company laptop, chasing the missing timesheets, and checking whether the SaaS subscription that nobody's using is still being paid for.

What it looks like when it actually works

The clearest sign that a team's operations are working well is that nobody's really talking about operations. Work moves forward without a lot of coordination around it. People know what they're supposed to be doing, managers have the context they need to make quick decisions, and the end of the month doesn't feel like an archaeology project. The overhead is still there, it's just light enough that it stops being something anyone notices.

Getting there doesn't require tearing down the entire stack. It usually comes down to finding one place where the work and everything around it actually connects.

Pistacio is built for exactly the kind of team this post is about. For a growing agency where the director is also the one running ops, it brings together time tracking, task management, leave and expense approvals, asset and subscription registers, and project reporting in a single workspace.