6 ideas
Meetings begin with 20-30 minutes of silent reading of a six-page narrative memo before any discussion. Writing prose forces logical rigor that bullet points hide, and silent reading ensures everyone engages with the full argument rather than reacting to a presenter's delivery.
Before building a product, write the press release and FAQ as if it has already launched, describing the customer benefit in plain language. If you cannot write a compelling press release, the product isn't worth building — the document becomes the test of whether the idea matters to customers.
Every important initiative gets one leader whose sole job is that initiative, with no competing priorities dividing their attention. Dependencies and divided ownership are the primary cause of slow execution, so isolating accountability to one undistracted person accelerates progress.
Teams should manage controllable input metrics — like selection, price, and in-stock rate — rather than fixating on output metrics like revenue or stock price that they cannot directly move. Improving the right inputs reliably produces the desired outputs over time, so attention belongs upstream.
Teams should be small enough to be fed by two pizzas, because communication overhead grows non-linearly as teams enlarge. Small autonomous teams that own their entire stack move faster than large teams burdened by internal coordination and cross-dependencies.
Good intentions don't work; only mechanisms do — a complete process with tools, adoption, inspection, and reinforcement that survives turnover and forgetting. When something repeatedly fails, the answer is to build a self-correcting system rather than to ask people to try harder.