There's a specific kind of message that ruins an afternoon. “Hey, can you send a quick update on what you've been working on?” Ten words. And I know, the second I read them, that I'm about to lose the next half hour digging through my own week to answer a question about work I already did.
That's the part that gets me. It isn't the writing. It's the archaeology. I did the work. I know I did the work. But “what did you do this week” has no quick answer, so I open Slack and scroll back through my own messages, open the PRs I merged, check the tickets I moved, and try to reconstruct Tuesday from a calendar invite and a vague feeling. The work took an afternoon. Proving it took another one.
I spend more time reporting the work than anyone spends reading the report.
And that's for one project. If you're on a single thing, with one manager, you can maybe wing it. I'm on three. Two PMs who each care about exactly their slice and nothing else, plus a manager who wants the version that rolls up into his own update. So it isn't one dig, it's three, each a different cut of the same week, each tuned to what that person actually cares about. If you're on more than three, god bless.
And if I don't send it, the chasing starts. A nudge on Thursday, a “just checking in” on Friday, a “no rush!” that means the opposite. Being chased for a status update is its own small humiliation, because the honest reason it's late is never that the work didn't happen. It's that I hadn't found the time to go reconstruct what I already lived.
For a while I blamed the people asking. Then I noticed the obvious. There was nowhere for them to look except me. Every answer about my work had to route through my memory and my afternoon, because I'd never put it anywhere they could see.
The chasing was never really the problem. Being the only place to find my work was.
You'd think the fix is to dump everything into a channel and be done. It isn't. The first PM shouldn't see the second PM's roadmap. Half of what I track is rough, or private, or not mine to announce yet. Different people are allowed to see different slices, and sorting that out by hand, every week, is exactly the tax I kept paying.
Someone I know runs far more than three projects and somehow never seems to get chased. I asked how. She publishes once a week. A short list, each line tagged to the project it belongs to, and she decides who is allowed to see which tag. Her PMs and her manager just look. Nobody pings her, because there is finally something to look at that isn't her.
That isn't a talent for organization. It's a workaround for a tool that didn't exist.
So we built it into Perfolio.
You already capture your work as you go. Updates turns a handful of that into a short published list. You tag each item with the project or person it's for, and you choose exactly who sees what. The first PM gets the first project. The second gets the second. Your manager gets the whole thing, or just the outcomes. You publish once, and each person opens their own view with only the lines you meant for them. No dig. No three rewrites. No 5:30 on a Thursday spent proving Tuesday happened.
It's a push, not a pull. Nobody gets to reach into your log and ask what you did today. Nothing goes out that you didn't publish on purpose. The messy notes, the half finished threads, the work that isn't yours to talk about yet, none of it is visible to anyone. The only thing that leaves is the exact set of lines you chose, for the exact people you chose.
It won't decide what's worth sharing. You still pick every line that goes out. All it kills is the weekly archaeology, and the pile of reminders that show up when the archaeology runs late. You do the work once, you publish it once, and the next time someone wants to know where things landed, they already can.
The work was never the hard part. Finding it again, every week, for everyone who asked, was.