Build for the organization you're becoming, not the one you are today.
One of the most common startup operations mistakes is building systems that fit the organization's current size perfectly — and that fall apart the moment it grows. A spreadsheet that works beautifully for a two-person team becomes a liability at ten. A board governance model designed for a founding board may not serve a mature institution.
The right question when standing up operational infrastructure isn't "what do we need right now?" It's "what will we need in three years, and how do we build toward that from the start?"
That doesn't mean over-engineering everything. It means making deliberate choices about where to invest in infrastructure early, because retrofitting systems onto a growing organization is far more expensive and disruptive than building them right the first time.
The handoff is a deliverable, not an afterthought.
In startup operations work, there's always a moment when permanent staff arrive and take over, or when the organization matures past the founding stage. That transition is one of the highest-leverage moments in the life of a new organization. Done well, it accelerates everything. Done poorly, it creates months of confusion, rework, and lost momentum.
I've learned to treat the handoff as a deliverable from the very beginning. What does the incoming team need to hit the ground running? What documentation, what context, what decisions have already been made and why? The goal isn't to hand someone a set of files. It's to hand them a functioning organization with enough institutional memory baked in that they can lead from day one, not spend months catching up.
Hold the mission tightly when everything else is uncertain.
Startup environments are disorienting by nature. Priorities shift. Timelines compress. Decisions get made with incomplete information. There will be moments — often many of them — when the path forward is genuinely unclear.
In those moments, the mission is the navigation system. When I didn't know what the right operational decision was, I asked: what does this organization exist to do, and what does that require of us right now? That question doesn't answer everything. But it answers enough.
Five organizations. Five different versions of the same essential challenge: how do you take something that exists only as an idea — sometimes only as a funding commitment and a mandate — and turn it into a place where people can do meaningful work together?
There's no single answer. But there is a consistent truth underneath all of them.
That's the whole job.