Sunday Notes: The Workflows Your Team Runs But Never Writes Down
Every team I've talked to this week has a few workflows that live nowhere.
The Friday-afternoon check-in someone reconstructs from chat history. The ChatGPT prompt that "really works" that one person on the team quietly rewrites every other Tuesday. The invoice-reconciliation pass that eats 40 minutes because half the week never got logged.
This week I had three separate conversations land on the same thing: the most expensive workflows on a team are the ones that aren't captured anywhere.
Two patterns, same shape
The conversations were in different worlds — freelancers and agencies on one side, marketing/sales/support teams on the other — but the underlying pattern was identical.
Pattern 1: time that vanishes.
Freelancers and small agencies kept describing the same loop. Work happens. Tracking gets postponed. Friday becomes a reconstruction exercise. The invoice goes out for less than the week actually was.
The instinct is "I need more discipline." The fix is usually different: remove the moment where tracking becomes a decision. That's the entire bet behind FillTheTimesheet — automated tracking so the timesheet mostly fills itself and Friday afternoon stops being detective work.
Pattern 2: prompts that vanish.
Marketing, sales, HR, and support teams kept describing a different version of the same loop. Someone writes a prompt that works beautifully. They use it for three weeks. It disappears into chat history. Three months later, someone else on the team writes a very similar prompt from scratch, often worse than original.
That's the loop PromptShip was built for — a shared library of prompts your team can actually find again. One-click into ChatGPT, Claude, or Gemini. No "wait, what was the prompt Sarah used for that thing?"
What I actually wanted to say this week
Different markets. Different buyers. Same underlying problem.
Valuable work happens. The artifact never gets captured. The cost shows up later as the same work being done again somewhere else by someone else.
The teams I see compounding fastest aren't necessarily working harder or hiring better. They've just lowered the friction of capture — the moment between "this worked" and "this is now reusable."
That's almost never a glamorous feature. It's also almost always the thing that turns one-month users into one-year users.
A question for you
What's one piece of "invisible work" on your team right now? Something useful that's happening, but living entirely in someone's head or someone's chat history?
Genuinely curious which loops other people are stuck in.
Sunday notes from The Speed Engineer. More long-form writing on Medium.
Top comments (0)