founders-guide-10x

Step 5: Remember the castle. When the metrics look bad, when the resistance feels personal, zoom out to the stone walls. The castle isn't a reward; it's a reminder that the game was rigged from the start. The 10x ask isn't about productivity; it's about extracting surplus from people who can't afford to say no. The castle is where you'll wait out the quarter, sipping something single-origin, while the 'low performers' are cycled through. And when you announce the next 'efficiency initiative,' you'll do it from the battlements, because distance lends authority to absurdity.

So that's the guide. It's not a parody, because parodies require exaggeration. This is just a description, filed under 'executive leadership.' The real lesson isn't for the founders; it's for everyone else. When you hear '10x productivity,' translate it as 'we want more from you for less.' When you hear 'unlock potential,' hear 'we've locked the pay.' And when you see a castle, ask who built it and who's still hauling stones. The metric that matters isn't output per hour; it's who owns the hour. The rest is just architecture.

Postscript: Count the hours, not the heads. The 10x framing always comes with a dashboard. Revenue per employee, story points per sprint, lines of code per day. The numbers look neutral, like they fell out of a calculator. But someone chose the denominator. Someone decided that the metric is output per hour, not ownership per hour. That choice is the whole game.

Consider the 'unlimited PTO' startup. Unlimited time off sounds like freedom until you realize it means no accrued vacation liability on the books and no obligation to approve any of it. The effective metric is 'how little time off can we make people feel entitled to?' Or the open-office redesign: 'collision density' goes up, noise goes up, but the founder's corner office stays enclosed, because the castle needs a view. The metrics are applied to the people who don't get to choose the metrics.

So when you're told to '10x your impact,' the first question isn't 'how?' It's 'who defines impact?' If the answer is the person in the castle, you already know the impact won't be on your calendar. The only metric that has ever mattered is the one you can't see on the dashboard: who owns the hours of the people doing the work. Everything else is just architecture with a pivot table.