Strategy to Mechanism
The mechanism you build matters less than whether it's the right mechanism. A great shooter is worthless if the winning strategy was just pick-and-place. This page covers how to go from a game reveal to a locked robot concept.
1. Break down the game
On kickoff, read the manual and answer these questions before you think about mechanisms at all:
What actions score the most points per cycle?
Tells you where to focus.
Which ranking points require specific capabilities?
Some RPs are non-negotiable for seeding well.
What's scoreable in auto?
Auto points don't compete with teleop time.
What's the endgame worth vs. one more scoring cycle?
Determines whether endgame is essential or a trap.
How many full cycles can you realistically fit in a match?
Forces honest math about what's achievable.
Map out a "perfect match" on paper: how many cycles, what capabilities, how many points. This is your ceiling. You won't hit it, but it tells you what to prioritize.
2. Prioritize
Decide what the robot will do and what it won't do. A robot that does two things well beats one that does four things poorly. You have six weeks.
Cut anything that's low points, complex to build, or inconsistent. If you find yourself saying "but what if we need it for playoffs?" — a mechanism added last-minute without testing is a liability, not an asset.
3. Choose between options (decision matrix)
When there are multiple ways to accomplish the same action, use a decision matrix to choose.
Max scoring height (in.)
4
4
3
Total part count
3
2
3
Estimated weight (lbs)
3
2
3
Cycle time to score (sec)
4
4
2
Number of unique pivot points
2
4
1
Weighted Total
16
16
12
How 4123 does decision matrices:
Score 1–4, not 1–5. A 5-point scale lets people default to "3" because it's the safe middle. A 4-point scale forces you to pick a side.
Use measurable criteria only. If you can't count it, measure it, or test it, it's too vague:
Mechanical complexity
Total part count, number of unique joint types
Speed
Cycle time from pickup to score (seconds)
Reliability
Success rate over 20 prototype trials (%)
Ease of manufacturing
Number of CNC'ed parts required
Weight criteria by what this game rewards. Fast cycling game → cycle time weighted high. Tight weight budget → estimated mass weighted high.
A decision matrix is a tool, not a verdict. If the numbers don't match your gut, talk through why. But don't ignore the numbers just because you like one option more.
4. Research past robots
Don't start from zero. Once you know what the robot needs to do, look at how other teams solved similar problems in past games.
Where to look:
Game libraries: FIRST Archived Game Documentation has manuals, game animations, and field drawings for every FRC game back to 1992. Use this to find past seasons with similar game elements to the current year.
Robot reveals and match footage (YouTube): Search "[year] FRC robot reveal" or "[team number] [year]" to see how top teams played specific games. Watch full playoff matches to see what mechanisms worked under pressure, not just in reveal videos.
Behind the Bumpers (YouTube): Teams walk through their robot design up close. Great for understanding why a team made specific choices.
Chief Delphi build threads: Top teams post detailed build logs. Search for the game year or mechanism type you're researching.
Open Alliance / build blogs: Teams like Spectrum 3847 document their entire season publicly — strategy, prototyping, CAD, fabrication — day by day.
CAD releases: After each season, many teams post full robot CAD on Chief Delphi. You can open these in Onshape and study every detail.
If 15 of the top 20 robots at Worlds used the same basic intake geometry, that's a signal worth paying attention to.
5. Lock the concept
By the end of this phase (a few days to one week after kickoff, max), the team should be able to answer:
A whiteboard sketch is fine. No final CAD yet. The point is that everyone agrees on what the robot does and roughly how. If there's disagreement, resolve it now.
Reference
Last updated
Was this helpful?