Slow Cycles, Fast Feedback: Learning as a 2x Founder

A few years ago while at Alohome, I shipped a feature on a Tuesday. By Thursday, I already knew if it worked. Conversion was up, or it wasn't. Users loved it, or they churned. I could look at a dashboard, feel the immediate consequence of a decision, and correct course before the week was over. That's the rhythm most tech founders live in: build, ship, measure, adjust, repeat — sometimes several times a week.

Then there's the other side of my work, in real estate development. I've signed a piece of land knowing that the market's verdict on that decision — whether it was the right site, the right product, the right timing — might not arrive for three, five, sometimes seven years. By the time you find out you were wrong, the mistake is already poured in concrete, literally.

Living inside both worlds at once has taught me something I don't think I would have learned from tech alone: resilience isn't just about surviving hard moments. It's about learning to make high-quality decisions when the feedback you need to correct them doesn't come for years. And that skill, once you build it, changes how you operate everywhere — including in the businesses that move fast, and even in how you build the team around you.

The Anatomy of a Cycle That Doesn't Forgive You Quickly

Real estate development doesn't run on sprints. It runs on a chain of dependent, sequential stages, each one with its own timeline, its own risk, and almost none of them reversible without real cost.

You sign the land — often the single highest-leverage decision in the entire project, made with the least amount of real market information you'll ever have. Then you enter permitting, which can take months or years and is subject to municipal timelines, political cycles, and regulatory changes you don't control. Then comes bank credit approval, where your assumptions about costs, absorption, and pricing get stress-tested by an institution with its own risk appetite and its own timeline, often disconnected from the market's. Then construction itself, exposed to material costs, labor availability, and weather. Then the legal formation of the condominium regime. Only after all of that do you finally sell and deliver, and find out — years after the first decision — whether your original read of the market was right.

Every one of those stages can independently delay the project by months. Stack them, and a development that looked reasonable at signing can deliver into a completely different market than the one you underwrote. Interest rates move. Demand shifts. A competitor opens two blocks away. And you can't A/B test any of it. You get one shot, informed by a snapshot of the market that may no longer exist by the time you're done building.

This is the part people outside the industry underestimate: it's not that real estate is slow because the people in it are slow. It's that the structure of the business makes fast correction almost physically impossible.

Tech's Illusion of Control

Compare that to tech, where the feedback loop can be days, sometimes hours. You test a pricing change, you know by the weekend. You launch a feature, the data tells you within a sprint if it's working. This speed is a real competitive advantage — it lets you learn faster than almost any other kind of business.

But it also creates something I'd call an illusion of control. When you're used to correcting course every week, you start to believe that most business problems are correctable in weeks. You develop instincts built for a world where mistakes are cheap and fast to fix. And if you're not careful, you carry that instinct into decisions where it simply doesn't apply.

The clearest place I've seen this play out isn't strategy or product — it's people. Hiring and culture live inside the same company as your fast-moving product, but they cook at a completely different pace. You can tell within a sprint if a feature is working. You cannot tell within a sprint if a hire was right, or if a cultural norm you set six months ago actually took root. A bad hire can look fine for months — even perform well in the short term — before the real cost shows up later, in how they treat the team, in who they push out, in decisions made under pressure that never make it into a dashboard. Culture is even slower: the values you say you have and the values you actually reinforce through daily decisions take a year or more to fully separate from each other, and by the time the gap is obvious, it's already shaped how dozens of people behave.

I've made the mistake of hiring at tech speed — trusting quick signals, moving fast because the market rewarded speed everywhere else in the business — and then being surprised, a year later, when the slow-cooking consequences of that decision finally arrived. The feedback loop on people is closer to real estate's than it is to a product's, and treating it like the latter is one of the more expensive illusions a founder can carry.

Type A and Type B Decisions

Once I recognized that not everything in my business moves at the same speed, I needed a way to decide where my attention actually belonged. The framework that's helped me most is separating decisions into two types.

Type A decisions are reversible. If you get them wrong, you can adjust — quickly, and usually without lasting damage. A pricing experiment, a marketing message, a feature flag, even most hires below a certain level of seniority. These decisions benefit from speed. The cost of moving fast and being wrong is low, because you'll know soon and you can correct.

Type B decisions are effectively irreversible, or reversible only at enormous cost. The land you sign. The core product bet you build a company around. A senior hire who will shape the culture underneath them. The partner you tie your company's future to. These decisions don't forgive you the way Type A decisions do. Get one wrong, and you may not find out for years — and by then, the cost of reversing it can be larger than the original decision itself.

The mistake I kept making, before I named this distinction, was applying the same decision-making speed to both categories. I wanted to be fast everywhere, because fast had worked so well in the parts of the business built for it. But being fast on a Type B decision doesn't make you agile — it makes you exposed, for years, to a mistake you didn't give yourself enough time to catch.

So I've tried to build a discipline around it: fire yourself from the Type A decisions. Delegate them, set a fast default, and trust the feedback loop to correct anything that goes wrong. Your attention is a scarce resource, and Type A decisions don't need much of it — they're self-correcting by design. Then take everything that time frees up and put it toward the Type B decisions: the land, the senior hire, the cultural precedent you're setting, the partnership you're entering. Slow down deliberately where the business won't slow down for you. Build scenarios instead of single forecasts. Look for whatever early, imperfect proxy signals exist — presale interest, reference checks that go three calls deep instead of one, how a candidate behaves under real pressure rather than in an interview — because you won't get the real answer for a long time, and imperfect information beats none.

This is, I think, the real discipline behind resilience: not treating every decision as equally correctable, and having the humility to know which ones you're allowed to move fast on, and which ones deserve the kind of patience that real estate has forced on me.

Carrying Both Clocks at Once

The real shift, for me, hasn't been getting better at real estate or better at tech in isolation. It's been learning to move between two clocks without losing myself in either one — and applying that same split-speed thinking to the parts of any business, tech or real estate, that quietly run on the slow clock even when everything around them feels fast.

From real estate, I've brought back patience and rigor to my Type B decisions everywhere, even inside a fast-moving company — a willingness to sit with a senior hire, a core bet, or a cultural precedent a little longer, and ask "what happens if I'm wrong about this for a year, not a week." From tech, I've brought back an obsession with finding feedback loops wherever they exist, even in businesses built to deny them to you — including in how I evaluate people and culture, where I now look harder for the early signals instead of waiting for the slow, expensive ones to arrive on their own.

Reinventing yourself as an entrepreneur, at least for me, hasn't been about picking one identity — the fast-moving tech founder or the patient long-cycle developer — and mastering it. It's been about holding both clocks at once, and knowing, decision by decision, which one is actually running.

A Message to Fellow Entrepreneurs

If you've only ever built in fast-feedback environments, look closely at the parts of your business that don't actually move at that speed — your senior hires, your culture, your biggest irreversible bets — and give them the patience they need, even if everything else around them is moving fast. And if you're already living inside a long, unforgiving cycle, don't mistake patience for passivity. Fire yourself from the decisions that will correct themselves. Spend everything you have on the ones that won't.

Resilience isn't built in the businesses that correct you quickly. It's built in learning which decisions deserve your speed, and which ones deserve your patience — and having the discipline to never confuse the two.