What Beverly Boy Learned from Max Arshavsky About Resilience and Learning by Doing
Max Arshavsky is the co-founder and CEO of Zenno Astronautics. His company develops magnetic technologies for space and has operated superconducting technology in orbit. But his Authority Magazine interview was less about the technology itself and more about what it takes to turn a difficult idea into something real.
Arshavsky’s path was not straightforward. He left biomedical engineering after realizing it was not the work he wanted to spend his life doing. He then spent years reading, working, volunteering, and searching for something that felt meaningful before founding Zenno in 2017.
One of the most interesting parts of the interview came when he was asked for five things he wished someone had told him before becoming a founder. He said he did not really wish someone had given him the answers. Some lessons, he explained, only become meaningful after you experience them yourself.
For video teams, five practical lessons still emerge from his story.
Progress Comes From Solving One Problem at a Time
Arshavsky admitted that he once imagined major companies being built around one big breakthrough. The reality was much slower. Zenno moved forward by solving thousands of problems over many years rather than waiting for one defining moment.
Video teams can work the same way.
Not every project needs to reinvent the format. Improve one or two things each time. Tighten the opening. Ask better interview questions. Simplify graphics. Notice where viewers may lose the thread and fix that in the next version.
Consistent improvement usually matters more than chasing one perfect piece.
Big Ideas Need a System Behind Them
Arshavsky learned that having an idea was only the beginning. To turn Zenno’s technology into something real, the company also needed people, facilities, manufacturing, funding, suppliers, and customers.
Creative work needs support systems too.
A company that wants regular customer stories needs a repeatable way to find participants, schedule shoots, collect releases, and handle media management, review edits, and approve final versions.
The creative idea may get the attention, but a good process is what allows the team to keep delivering.
Test Early Instead of Assuming
One of Arshavsky’s early mistakes was deciding to build an orbital simulator himself. He expected exact results because the underlying physics was exact. When the results were not perfect, he had to learn that tools and models have limitations.
The lesson for video teams is simpler than the science behind the story: test important assumptions early.
Read the script out loud before shoot day. Use a technical location scout to check for noise, lighting, access, and other issues before the crew arrives. Record a quick sample of the spokesperson. Try more than one opening before committing the entire edit to it.
A small test can uncover a problem while it is still easy to fix.
Some Lessons Only Make Sense After You Live Them
When Arshavsky was asked what he wished someone had told him earlier, he said that advice alone would not necessarily have helped.
He had already received plenty of advice. The difference was that some things only became real after he made mistakes, faced setbacks, and learned through experience. He even believes some of his early naivety helped him start in the first place.
Video teams can relate to that.
A checklist can prepare you for a difficult shoot, but it cannot teach everything. A confusing interview may show why the pre-interview process needs work. A rough cut may reveal that the original message was too broad. A missed deadline may expose an approval problem.
The important part is to carry the lesson into the next project.
Reduce Stress, Not Just Hours
Arshavsky also offered a useful perspective on burnout. For him, the problem was not simply how many hours he worked. It was the stress and anxiety he attached to the work.
His approach became simple: get up, do your best work, then go to bed.
He also reflected on how founders can become attached to constant highs and lows. Over time, he came to believe that some of that drama disappears when you decide you no longer need it.
Production teams can reduce the same kind of pressure by creating clearer boundaries. Lock scripts before the shoot. Name one final approver. Separate rough-cut feedback from final polish. When a late change affects the schedule, make the tradeoff visible instead of quietly adding more work.
Good planning does not remove every problem. It removes unnecessary ones.
Practical Application for Video Teams
Treat content as an ongoing program rather than a string of unrelated projects. Choose a schedule the team can actually maintain and improve the process after each release.
Build reusable tools around recurring work: interview briefs, shot lists, approval stages, graphics templates, and organized footage libraries.
Test important decisions while they are still cheap to change. Then, after each project, note what slowed the team down and what worked better than expected.
The goal is not to avoid every mistake. It is to avoid making the same mistake twice.
Team Beverly Boy’s Takeaway
What stands out in Arshavsky’s interview is how much distance exists between having a strong idea and making it work consistently.
That applies to video too. Strong creative work depends on more than inspiration. It takes repetition, testing, clear systems, and a willingness to learn when the first plan does not work.
We also like his approach to stress. Teams do better when the process carries some of the pressure instead of relying on people to constantly push harder.
Conclusion
Max Arshavsky’s story is ultimately about learning by doing.
For video teams, the lessons are practical: improve one project at a time, build a repeatable process, test assumptions early, learn from experience, and reduce unnecessary stress around the work.
Big ideas matter. But steady execution is what turns them into something real.
This article is based on an interview originally published by Authority Magazine. Read the full interview here.
