How to Build a 90-Day Plan With a Small Team

A solo founder's 90-day plan is a private negotiation with yourself. Add two, three, five people, and the same process needs a bit more structure, without losing what made it work in the first place.

The core process does not change

You still re-read the Vivid Vision, pick the slice the quarter is about, and set three to five rocks. What changes is who is in the room for that conversation.

Bring the team into rock-setting

With a small team, everyone can realistically be in the room for setting rocks. Use a simple process: generate ideas, force-rank with votes, size each one for real. See setting quarterly rocks with your team.

This matters more on a small team than a large one. With only a few people, one person quietly not bought in affects a much bigger share of your total capacity.

One rock, one owner, even on a small team

It is tempting on a small team to say everyone owns everything. Resist it. Each rock still needs exactly one name attached, even if two people are actually doing the work. Shared ownership with no single name is how a rock slips through the cracks on a team of any size.

The weekly check-in becomes a real conversation

Solo, your weekly review is a private fifteen minutes. With a team, it becomes a short standing meeting: each rock owner says on track, at risk, or off track, and what they need. Keep it to fifteen minutes total. It is a status check, not a working session.

Still set your own personal rock, out loud

Set a rock for your own life, the same as you would solo, and say it to the team. Home for dinner four nights a week this quarter, or a real week off booked and protected. This does two things: it protects your own life the way the framework intends, and it models to a small team that this kind of rock belongs on the list, which makes it easier for them to set their own.

Watch for the founder doing all the thinking anyway

A common trap on a small team: the founder still privately decides everything and just announces it dressed up as a group process. If your rocks always end up exactly what you would have picked alone, check whether you are actually leaving room for the team's input, or just going through the motions.

Small-team scoreboards stay simple too

With only a few people, resist the urge to build an elaborate tracking system. A shared document with each rock, its owner, and a one-word status updated weekly is enough. A tracking system can get complicated faster than a small team grows, and once it does, the system stops getting used.

Cross-training matters more on a small team

When only a few people hold the company's knowledge, one person's rock slipping because they got sick or pulled away can stall the whole quarter. Where possible, make sure at least one other person has enough context on each rock to keep it moving if the owner is briefly unavailable.

Celebrate finished rocks visibly

On a small team, a finished rock is a bigger portion of the whole quarter's output than it would be on a larger one, and it deserves to be marked as such. A quick, genuine acknowledgment when a rock closes out does more for morale on a small team than almost anything else in the process.

Revisit the process as the team grows

What works for three people will need light adjustments at eight and real changes at twenty. Do not treat the small-team version as permanent. Every few quarters, ask the group directly whether the current process still fits, and be willing to add a bit more structure exactly when the informality starts creating gaps instead of speed.

Hold the vision. Not the circumstances.