The wall
Evelyn keeps a piece of paper on the wall of her office. It is a printed grid: four columns, one for each region the office moves through in any given month, and a row for each of the next thirty days. Inside each cell is a person, a meeting, a flight number, or a deliverable. Looking at the grid is the only way to see the operating cadence as a single object.
The wall exists because nothing else worked. The shared calendar collapsed the moment the company hit eight time zones. The travel platform showed cities and flights but didn't show the shape of what was happening on either side of each leg. The project tracker showed deliverables but not the trade-offs between them. The wall is the integration layer. Everyone in the principal's office uses it. Nobody outside the principal's office knows it exists.
"There's a calendar, and then there's the shape of the calendar. Those are different objects, and the second one is the one that breaks when nobody is paying attention."
External commitments
Beyond the operating company, the principal's office carries the calendar weight of multiple external commitments. The cadences are non-negotiable and only sometimes compatible. Each one lives on a different rhythm; none of them adapts to the others.
Evelyn's job is to find the compatibility. She talks, in general terms, about the trade-off she made earlier this year when one of those rhythms shifted by a week and forced an unplanned arc through several cities. She rebuilt the month's grid in a single afternoon, with help from two peers at other companies — both of whom she has known long enough to call on a Sunday.
Systems she built when nobody told her to
The wall is one of three systems Evelyn built in her first year that did not appear on her job description. The second is the quiet brief — a one-page document she sends the principal every Sunday evening that summarizes the week ahead in a specific voice and a specific structure. The third is the after-action log — a running record of every trip's last-minute changes, with a line of context next to each one so that a future principal's-office hire can pattern-match.
"None of this is in my job description," she says. "All of it is the reason the office runs."
"The mark of the job done well is that ninety percent of the decisions inside the principal's office happen quietly. The principal sees the ten percent that needs them."
What she'd outsource
The closer: what part of your job would you outsource if a vendor existed?
"The ground side of every leg of every trip," Evelyn says. "I currently have a different driver coordinator in every city. None of them know what the others are doing. None of them know that the trip is part of a longer arc. I'd buy the vendor that knew all of it. I don't know if that vendor exists."
Topics covered
- The wall: how Evelyn integrates four time zones into a single visible object
- External commitments and the trade-offs between non-negotiable rhythms
- The quiet brief, the after-action log, and the systems built without a mandate
- The international peer network that runs alongside the company