Grouped by the problem each one is for.
Test whether a plan holds up, size a team when the forecast will be off, and check whether a change moved the number.
Planning, revenue and execution, one problem each from my own work, with what I got wrong.
Case studyPlanning and resource allocationUnit cost used to show up from finance late in the year, when the only lever left was headcount. I turned it into a number three teams agreed on and saw every month.
54% → 100% of initiatives with quantified impact, in two weeks
What I got wrong: I built the complete version first and the one-page version second. It should have been the other way around.
Read the case study →Sellers already had the list. They couldn't tell a publisher what it was worth, so they kept losing to pitches that came with a number.
8 figures of incremental revenue, and a peak of 256% pipeline velocity
What I got wrong: I scoped the queries to my own region, so I couldn't validate the results in the two regions that adopted it.
Read the case study →Several hundred people kept building through months of regulatory hold, on a deal that might not have made it through review.
74% → 95% on-time deployments, in under three months
What I got wrong: I didn't standardize intake before a dozen vendor teams each built their own tracker.
Read the case study →Operating questions that usually get decided on gut feel.
ArticleOperating model designA support function can stay central or split into dedicated pods. A shared person would have to be 73% slower on every request before pods come out cheaper, which is much further than most people guess. The break-even also shifts with client size.
Read it →Paste the number you watch, click when you changed something, read one sentence. How the tool decides, the false-alarm rate it was held to, twelve pastes shaped like real exports, and the slope fix I tried that made things worse.
Read it →I designed an intake form around what I needed and didn't think about what anyone would fill in. Then I blamed stakeholders when nobody used it. Forty-two fields, three of them ever read, at a company whose CRM already had most of the answers.
Read it →Free tools for Google Sheets.
Add-onGoogle SheetsWrites every comment in a spreadsheet to a sortable tab: sheet, cell, author, date, resolved status and replies.
Read about it →Pulls every comment thread out of a Google Sheet, with its tab, its cell and its replies. Runs in your browser. Nothing is uploaded.
Try it →A job pipeline I run every morning, an experiment in tracing what an event changed, and a journaling app on Google Play.
ToolJob searchA job pipeline that reads twelve thousand postings a morning, checks its rules against 886 hand-labeled emails, and fixes a year of stored records when a rule turns out to be wrong.
Read about it →Drop in an event everyone remembers and watch what it changed, in the order it happened, with how sure it is of every link.
Try it →A small AI journaling app.
See it on Google Play →
