Most “contentious” design year in a long time?

Technical Technical Discussion
1

Like many teams, after thinking about the possible overall strategies, we start off design by enumerating the possible “robot actions” (eg “intake coral from ground”) and then place them in one of NEED / WANT / NICE-TO-HAVE / NO categories.

We added NO last year for things we wouldn’t pursue at all no matter how easy / cheap they seemed (many teams effectively put trap-score here last year).

This year we added another category, TEST (prototype before deciding), because we just couldn’t come to any consensus on several actions.

Was this other teams’ experience? Or did you get consensus easily?

4 Likes
2

I think that pretty much sums up my team. We had a lot of ideas thrown out and decided to regroup after researching and prototyping to determine what we truly need and want. I think with there being so many different components needed and it being difficult to use the same systems to do it all, it will require a lot of prototyping to design a robot that satisfies everyone. At the end of the day, everyone has their own opinions as to what they want and I think after testing, it should help us see what is feasible and what would require a lot more thinking.

1 Like