> For the complete documentation index, see [llms.txt](https://www.ftcwiki.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.ftcwiki.org/how-to-build-competitive-robots/how-to-compete/strategic-design.md).

# Strategic Design

### Strategic Design

Strategic Design in the most fundamental starting point to building a performing chassis. It can boost any team's performance . Strategic design in summary is the factors that go into what robot your team decides to build, creating a successful build season schedule for getting it done, and executing it well for competitions. It's about priorities and tradeoffs. It's about designing a robot and playing the game within your capabilities. Without a proper strategy and team structure, you cannot succeed.

Once you’ve grasped the fundamentals of [robot architecture](https://www.ftcwiki.org/design-style/), the next step to building a truly competitive FTC robot is refining your design process and engineering workflow. Top-performing teams go beyond basic functionality—they emphasize efficiency, precision, and adaptability from the earliest planning stages.

<figure><img src="/files/alRVvq41I9dap9iWB2xF" alt=""><figcaption><p>FTC 18438 Wolfpack Machina Powerplay game strategy</p></figcaption></figure>

Understanding and outlining your game strategy is key to developing a productive design process. Starting from as simple as a whiteboard and marker, highlighting your goals and organizing what aspects of your robot archetype to focus your efforts on.&#x20;

<figure><img src="/files/g23AjfpaA6fWcGyZ1gRE" alt=""><figcaption><p>Parallel Plate Mecanum example with servo linkage PTO</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.ftcwiki.org/how-to-build-competitive-robots/how-to-compete/strategic-design.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
