Stage 4 · Strategy

Stage 4 is what separates teams that make Worlds from teams that don't: a habit of improving how you design, not just what you design. The skills here are strategic — choosing what to build before you build it, then learning from every event so the next season is sharper than the last.

Strategic design as a discipline

Strategic design is the practice of deciding what to build by reading the game, not by gut feel. Identify the highest-value scoring action, count cycles, and design your robot around the bottleneck of that one cycle. Most lost matches are strategic-design losses, not mechanical ones.

Cycle-time analysis

Pick up + traverse + score = a cycle. Time each phase on your prototype. The longest phase is your bottleneck — fix that one before you optimize anything else. Optimizing the wrong phase is the most common waste of a build season.

Reliability and single points of failure

Every belt, chain, connector, and zip-tie is a potential SPOF. Identify the top three on your robot at every event and either eliminate them or build a redundancy. A 90%-reliable robot loses to a 60%-capable, 99%-reliable one — and the math gets worse as the match wears on.

Iteration vs. revision

Iteration is small tweaks to your existing design. Revision is ripping it out and starting over with a different approach. Most teams iterate when they should revise. If three iterations didn't fix the problem, the design is wrong — admit it early, lose a weekend, save a season.

Post-mortem habits

After every event, write down what broke, what surprised you, and what wasted time. Make it a 30-minute team ritual the day after, not a Slack message that gets forgotten. Teams that improve fastest do this religiously; teams that plateau don't.

Time budgeting and scope cuts

Map your build-season hours to your subsystems. If 60% of hours go to the drive base, 60% of competitive capability had better come from the drive base. When the budget doesn't match the priority, fix the budget — usually means cutting scope before you run out of weeks.

Learning from elite teams without copying

Watch elite teams' match videos and CAD reveals. Don't copy the mechanisms; copy the decisions. Why did they pick this archetype? Why did they cut this feature? What did they prototype and throw away? The reasoning transfers across seasons; the geometry doesn't.