Block 9: Planning for a Quarter

You want the matrix first.

The prioritized use-case matrix. The 90-day roadmap. The stakeholder alignment doc that says who owns what and when. Then — only then — will anyone be allowed to touch anything.

Jen said it clean on July 20th: "I'd like to have a clearer, more organized approach into kind of what we're doing first and then how we're doing it." (Client call 7/20)

(Brad note: the names in here — Jen, Daphne, Ben, Erica — are real clients on real calls. If you want in the same room, apply at buildwithoptimus.com.)

And I get it. That's how MBAs think. That's how good operators of the old world thought. The old world rewarded rigor-first because building was expensive and mistakes cost real money and time.

That world is over.

I said this to one of my clients on July 13th, and it's the sentence I want you to sit with:

"We need to get away from the idea of, oh, we need to plan for a quarter, and it's going to take 90 days or 180 days to get to this goal. That kind of [thinking]'s going to kill you." (Client call 7/13)

Kill you. Not "slow you down." Kill you.

Because the leaner team on the other side of the country isn't running quarterly planning cycles. They're running a series of same-day tests. And every day you spend organizing before executing is another day they collect data you don't have.

Here's the frame that replaced planning for me. I said it to him on July 6th:

"The ability to have an idea and go to market the same day is nuts, and that will give you a ridiculous advantage." (Client call 7/6)

Same day. Not same sprint. Same day.

And a specific challenge from the same call — this is the drill I use to shake clients out of the matrix trap: "Can I have an idea at 9:00 a.m. and be testing it by noon, even as a novice?" (Client call 7/6)

That's the benchmark now. Nine to noon. If your ideas take longer than that to reach reality, you have an organizational problem, not a strategy problem.

On the "organize first, execute later" instinct — I told him on July 27th: "The organization and classification by humans probably slows it down more than speeds it up at this point... Just dump a bunch of data, tell it what you're looking for, refine it." (Client call 7/27)

The agent does the sort. You give it the raw material and the criteria. That used to take a team a week. Now it takes an afternoon.

And when the agent tells you the project will take eight weeks? I'll leave you with the same reaction I had on the July 13 call:

"I love how it says eight to 12 weeks. It's often usually that factor of seven. But really that's like one to two weeks." (Client call 7/13)

Divide every estimate by seven. Then start the work.

This week

Skip the planning meeting.

Take tomorrow morning's best idea. At 9 a.m., open the terminal. By noon, you're testing it.

Dump the data. Tell the agent what you want. Refine what comes back. Ship the version that works. Kill the version that doesn't.

That IS the plan. Not preparation for the plan — the plan itself.

"Let me just show you versus telling you." (Client call 7/20) That's the operating principle.

Show, don't tell. Every single week.