This week's five pieces kept finding the same thing in different rooms: a summary number that was accurate as far as it went, and something underneath it that nobody reported. An adoption dashboard, a season of one-reason exclusion notices, a flattening chart, a hiring vendor's pooled selection rates and a board's voting record all look fine from a distance.
On September 16, the planning software company Board released a survey of 300 CFOs, CIOs and COOs at enterprises with at least $100 million in annual revenue. Eighty-three percent said their board has made a strategic decision based on a forecast they already knew was outdated, and 40 percent reported significant business consequences from that decision. Three-quarters said roughly half or more of their planning decisions rely on data more than 30 days old.
Board sells planning software, and its own explanation is the one its product answers. Its CFO, Gordon Pothier, puts the cause down to data that moves faster than the planning cycle. The full report sits behind a sign-up form, and the release names no research firm, fieldwork dates or question wording, so these figures deserve the caution any vendor survey does.
Read the 83 percent sentence slowly, though. In the release's wording, the people who knew the forecast was stale were the executives answering the survey. A faster data pipeline shortens the lag between the forecast and the business, and it has no answer for an executive who already had the newer picture. Whether these executives said so before their boards decided, the release does not say, and the report that might is behind the form.
This week's pieces kept returning to that spot, from a hiring vendor's pooled selection rates to the boardroom voting records in Friday's piece: a summary that was accurate when it was made, carried into a room by people who knew more than it said.

If you have not heard Episode 6 of High Road Conversations, Tom Judkins is worth your time. When a handful of his videos first took off, he says, none of it had been planned, so he went back, studied the ones that worked, picked apart what he had done and built a template he could repeat on purpose. In his words, it went from a “miracle thing to a strategy, and a business concept.”
Listen →
I don't just talk about Agile and leadership, I put it into practice in my Skool, building and shipping real products with Claude every Thursday at 12:30pm EST.
Join us →There is a story in the Becoming REAL chapter of Agile Sucks! (When You Do It Wrong) that fits this week. A product manager, summoned to one of his CEO's surprise grillings the morning after a serious problem flared up, planned to walk through the sales history and roadmap and leave the crisis out. My co-author James Wright took over the meeting, rolled a whiteboard to the front and told the executives, “You came for a status report, but we had an emergency last night.” The team got a solution, and there were no more grillings.
Get the book →A short read every Saturday morning. No spam, unsubscribe anytime.
Subscribe