Lessons Learned from Our First Mission — What’s Next
By Lijie Zhu
You don’t forget your first satellite. The build nights that turned into early mornings. The failed antenna deployment tests. The unexpected victories — like hearing that first beacon. It’s messy, humbling, and wildly addictive.
At Interstellar Communication Holdings Inc., launching HADES‑ICM wasn’t just a technical milestone. It was a transformation. We moved from theory to orbit, from whiteboards to downlinks, from dreaming to doing. And now, standing on the other side of that mission, we’ve had time to reflect.
There’s this thing in aerospace — a kind of reverence for "lessons learned." These aren’t just bullet points for presentations. They’re the subtle truths that shape your next design, your next team meeting, your next decision to try again.
So, here’s what we learned from our first mission — and where we’re headed next.
1. Simple ≠ Easy
We started with a belief that simplicity would be our strength. Keep the payload lean. Use off-the-shelf components. Minimize points of failure.
And that worked… until it didn’t.
Space has a way of exposing every assumption. A connector rated to survive vacuum might technically be compliant, but if it wasn’t crimped just right? You’ll find out — probably too late. A firmware patch that works flawlessly on the bench might become unusable with real Doppler shift and noise floor interference.
Takeaway: Simplicity is still our design principle — but it now includes margin, redundancy, and a healthy dose of paranoia.
2. The Ground Game Matters More Than You Think
We obsessed over our satellite’s health. But what we didn’t obsess over enough — at least not early — was the ecosystem around it.
Our ground station worked, sure. But we didn’t fully anticipate how many variables would affect data integrity: temperature drift in SDRs, local RF noise, the quirks of third-party decoding software, or misconfigured time stamps.
Then there’s the human side. Volunteers around the world started logging our signals — some with better reception than we had! We scrambled to onboard them, verify their reports, and build tools to streamline it.
Takeaway: You don’t just launch a satellite. You launch a network — and every link matters.
3. People Show Up If You Let Them
One of the most surprising — and moving — parts of the HADES‑ICM mission was the sheer enthusiasm from people we didn’t even know.
A university group in Argentina tracked us daily. A student in Bangladesh wrote code to parse our telemetry. An artist in Norway submitted an FM beacon poem idea — which, in hindsight, we probably should have flown.
What started as an internal project became… something bigger.
Takeaway: Participation isn’t just possible. It’s powerful. The next generation of mission design must invite community from day one.
4. Redundancy Is Not Optional
We cut a few corners. Not recklessly — just budget-wise. And for the most part, our single-string architecture held up.
But we also had a few close calls:
A partial telemetry blackout due to thermal expansion
A low battery cycle we didn’t predict
A weird data glitch that resolved itself (thankfully)
In each case, a bit of redundancy — a second sensor, a watchdog circuit, a fallback mode — would’ve saved us stress.
Takeaway: Redundancy doesn’t have to be bulky. It just has to be thoughtful.
5. Don’t Wait to Celebrate
We were so focused on "making it work" that we sometimes forgot to pause. To say, “Hey, that test passed — let’s enjoy this.” Or, “Our satellite just deployed, and it’s alive.”
That’s easy to skip in startup mode, or when deadlines blur into each other.
But space is hard. Wins matter. And even small ones deserve a moment.
Takeaway: Mission culture is just as important as mission specs. Celebrate your team.
So… What’s Next?
After HADES‑ICM, we’re building toward a more open, scalable platform:
More modular PocketQubes — faster to iterate, easier to adapt
Payloads by invitation — artists, teachers, and tinkerers welcome
A new community dashboard for real-time tracking and experimentation
Open source tools to decode and visualize data with no prior experience
We’re also working on the next icMercury mission, which we hope will reflect everything we learned — and everything we’re still figuring out.
And in November, we’ll be heading to London for the 2025 Go Global Awards, hosted by the International Trade Council. Being nominated is a big deal for us — not because of prestige, but because of what it represents: that our work is part of something bigger. That space innovation is being recognized as a global language — and we’re proud to be fluent in it.
It’s not just a ceremony. It’s a convergence — a gathering of the world’s builders, thinkers, and doers. And we’re grateful to be in the room.
Final Thought
First missions are never perfect. Ours wasn’t. But it was real. And that’s what matters.
Because now we know what works — and what we’d never do again.
That’s how we’ll build what’s next. With humility. With excitement. And with a deeper understanding that space — like innovation — is better when it’s shared.