Remote collaboration
Comment Threads or a Single Status Field: A Support Team Trial
The support team had 41 open comment threads on one policy page and no reliable way to say whether the…
Remote work, measured
Every remote workflow tested on a live deadline
Tool reviews and team workflows written from inside the project, not from the feature page. Each piece ends with the template we actually shipped.
A short brief each month: one workflow, the tool that carried it, and the numbers that changed. No launch posts.
One email a month. A reply cancels it.Latest field notes
Six most recent
Meeting culture
Decision Meetings Without a Deck: Forty Tests in One Quarter
Forty decision meetings ran without slides, and the median time to a decision fell from 46 minutes to 19. The…
Remote collaboration
What Happens When a Remote Team Stops Using a Shared Inbox
The shared inbox took 1,900 messages a month, and 38 percent of them were internal notes that never needed to…
Workspace setup
Noise Floors in Shared Housing: What a Meter Shows Over Three Weeks
The quietest hour in a shared flat measured 34 decibels and the loudest measured 71, and the loudest hour was…
Team operations
Team Charters: Writing One That Is Read After Month Two
Six team charters were written in one quarter, and four of them were unread after two months, measured by the…
Team operations
Performance Reviews Without a Rating Scale: One Cycle Tested
A review cycle without numeric ratings produced longer written feedback and a shorter calibration meeting: 90 minutes against four hours…
Editor picks
Read these firstHow a review gets made
Four steps, same order every time
01
Pick one workflow
One job that repeats weekly, and one tool that claims to own it. Nothing wider than that.
02
Run it live
The tool goes into a shipping project with a real client date, for two full weeks.
03
Count the friction
Manual steps, handoffs and pings get logged in a spreadsheet next to the work itself.
04
Publish the template
Whatever survived the fortnight is written up as a template anyone can copy that day.
andy rodman
Ten years of distributed teams, first as a project lead and now writing down what the tools promise versus what the week allows. Based in Lisbon, working across four time zones.
More about the deskThe monthly brief, with the template attached
Each issue carries one workflow teardown, the spreadsheet or doc template behind it, and a short list of what changed in the tools covered so far.
No forwarding, no list sharing. Reply once to leave.