We also underestimated how fragile specialist knowledge can be. Some of the most critical systems depended on a small number of individuals with highly specialised skills, particularly in hardware development and manufacturing. When those contributors moved on, continuity suffered. In hindsight, redundancy, documentation, and knowledge transfer should have been treated as essential from the outset.
There were, however, areas where the work gained traction. Education and outreach proved resilient. Through partnerships and grants, we delivered workshops that introduced students to orbits, rocketry, and spacecraft design using accessible tools. On the technical side, while the cubesat did not progress beyond development, there were meaningful milestones. Alongside early discussions with launch providers and hardware manufacturers, completing a preliminary design review with a former NASA engineer marked an important learning moment.
Another key lesson was the cost of not building in public. We felt pressure for everything to be finished and polished before sharing progress, and without short-term feedback or visible wins, momentum suffered. If we were starting again today, we would stay smaller for longer, prioritise clarity over scale, keep the satellite firmly at the centre, and invest earlier in leadership, mentorship, and resilience.