The most useful management tool I run is a list of things I have no authority over. It is a cross-team dependency board, somewhere north of 150 items, and every one of them is owned by a peer product manager or a team that does not report to me and never will. "Influence without authority" is a phrase people say in interviews. The mechanism behind it almost never gets described, so here is mine.
What Goes on the Board
| Column | Rule |
|---|---|
| The dependency | One sentence: what I need from whom, or what they need from me. Both directions live on the same board |
| Owner | A named person. Never a team, never a role. A team cannot be late |
| Date | The date the owner said, in their words, not the date I hoped for |
| Status | As the owner last reported it. Never inferred from the date, never inferred from silence |
| Blocked behind it | What cannot move until this does, so the cost of slipping is visible to the person slipping |
The status column is the whole discipline. It is theirs, not mine. A board where I fill in "probably fine" because nothing has changed is a board full of my guesses, and the first time a guess is wrong the board loses its authority with everyone who reads it. The rule is the same one I apply to data: never infer a status from a date. Ask, record what they said, and show it.
The Cadence Is the Authority
Weekly. Same format, same day, same distribution, at more than one depth: a short version for people who need the shape, a per-team version for the owners, the full board for anyone who wants it. The update goes to everyone on it, which means every owner sees every other owner's rows.
That visibility is the entire lever. I cannot order anyone on the board to do anything. What I can do is make it public among peers when a row has said "no update" for three weeks, and nobody wants to be that row in front of the other owners. It is not escalation. Escalation spends a favor. Visibility spends nothing and works every week.
Why It Only Works Without Authority
If I could order these things done, I would get compliance and a false status. People report accurately to a board that cannot punish them, because the only thing the board offers is that it is also how they find out what is coming at them. Many of the rows are things other teams need from mine. The board is reciprocal or it is nothing. A dependency board run by someone with authority becomes a status report to the boss, and status reports to the boss are optimistic by construction.
What Automation Changed
The board used to be a chore. Chasing 150 owners for a sentence each is the kind of work that makes a product manager quietly stop doing it, and a board that stops being updated is worse than no board, because it is still trusted. Now the weekly rollup is generated from real signals, the calendar, the mail, the ticket system, and never from dates. I do not write the update. I review it, correct it, and send it. The context-capture task I described a few weeks ago, sorting expiring messages into what I owe and what is owed to me, is the same board at the scale of one person.
None of this is sophisticated. A list, a named owner, a status in their words, a weekly rhythm, and an audience of peers. The set of 150 things is not owned by anyone. Keeping the set honest is the job.