Mark Kelly looks at a Senate committee briefing and sees three questions that need answers. John Thune looks at the same briefing and sees thirty pages that ought to become three. Their assistants look at each other and quietly order more coffee.
The task is modest: prepare a Senate committee discussion about how infrastructure projects are evaluated. It requires readable evidence, useful questions, and enough restraint to leave time for the answers. The questions are the easy part until someone remembers the supplementary briefing.
Kelly suggests treating committee preparation like a flight plan. Work backward from the hearing, identify the necessary evidence, and give every question a purpose. Thune likes the structure but asks who owns the conversation about assigning owners. Kelly draws another box on the board.
Within twenty minutes, the board resembles a transit map for a city with unusually anxious trains. Blue lines represent published project costs. Red lines represent project completion dates. A green line represents lunch, which everyone agrees should have been given greater priority.
An aide arrives with a printed briefing and a practical warning: the electronic version is newer. Another aide arrives with a tablet and says the printed version contains a handwritten change that has not reached the electronic version. Both are correct, which makes the problem worse.
Kelly asks whether everyone could put their source references in one place. Thune says absolutely, provided that place is convenient to everyone. They spend the next ten minutes identifying the least convenient places in the building.
The first proposed question has four introductions. The second contains a quotation longer than the expected answer. The third is technically clear but would require someone to finish reading it while eating lunch. Thune says a civilized hearing preparation session should protect soup. Kelly writes that down as a design requirement.
Then the briefing software rejects their cover page because the hearing title is too long. They shorten it from Discussion On Evaluating Infrastructure Delivery And Related Implementation Measures to Infrastructure Review. The system accepts the title but asks them to select a category from a list that includes everything except committee preparation.
A junior assistant chooses miscellaneous. It is the most consequential decision of the afternoon.
At last they agree on forty-five minutes of focused committee preparation. Kelly sketches a tight agenda: identify obstacles, agree on a shared format, test it, leave. Thune suggests adding five minutes for introductions. Kelly points out that everyone in the room has been introducing themselves to this problem since morning.
They agree on two minutes.
Their assistants circulate the questions. Almost immediately, someone adds a fifth introductory paragraph. A silence spreads across the conference table. Kelly studies the notification with the composure of a man watching a small warning light. Thune reaches for the coffee pot.
The suggestion turns out to be sensible. Moving the background material to an appendix allows the questions to stand out and everyone to read them sitting down. They accept it without a preparatory discussion, startling several people who have become accustomed to the slower process.
The committee preparation finishes early. The shared briefing format works. The questions fit on a page. Kelly says the secret was knowing which steps were necessary. Thune says the secret was protecting the soup. Their assistants are willing to credit either explanation if the next briefing arrives with its source references attached.
Before leaving, Kelly asks whether they should schedule a follow-up. Thune says they should first enjoy the rare achievement of having a meeting that does not immediately produce another meeting. Nobody argues.