> For the complete documentation index, see [llms.txt](https://guide.mlh.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.mlh.com/hardware-hackathon-guide/pitfalls.md).

# Pitfalls

Hardware projects require precision under a tight time constraint. To help participants make optimal use of their limited time, communicate these common pitfalls and corresponding mitigation strategies.

### Technical friction

* Give hackers components vetted to work together as a system with minimal configuration

### Scope creep and time management

* Develop a thorough design plan early on, identifying the core components needed for a Minimum Viable Product (MVP) to get started quickly.

Here's an example breakdown of how hackers might spend their time at a hackathon:

* 10% Product Ideation (4.8 hours in a 24-hr hackathon)
* 35% Product Development (8.4 hours in a 24-hr hackathon)
* 30% Product Packaging (7.2 hours in a 24-hr hackathon)
* 25% Product Documentation (6.0 hours in a 24-hr hackathon)

### Component shortages

* Bring Your Own Electronics/Hardware (BYOE/H): Bringing personal components reduces the likelihood of reliance on the main lab inventory.

> Organizer Note: Source additional parts or reserve ahead of time to minimize event shortages.

### Soldering

* Pre-solder headers on microcontrollers before the event if possible
* Use hot glue for quick and durable prototyping

### Hard to move projects

* Build for portability and presentation:
* Build the project on a movable surface (e.g., a tray or small cart).
* Keep the project size manageable.
* Design the project to be easy to disassemble and reassemble.
* Take plenty of photos and videos showing the project working, especially for fragile or large assemblies, as backup for judging.

### Long reset time

* Document the process: Take frequent photos and videos showing the project working
* Create a simple reset checklist for bringing the project back online after power loss, movement, or demo completion

### Fabrication delays

* Prototype early: The sooner your idea is finalized, the sooner the design can be measured, finalized, and sent to a 3D printer or fabricated (e.g., using laser cutters)
* Around 30% of a team’s project time is recommended for physical packaging. That includes printing, fitting, etc.

### Robot pathing

* Multiple paths: If your challenge(s) use a test floor on site (such as for robot pathing challenges), set up multiple test zones so that many teams can test during the event at once