There was an interesting podcast episode I listened to a few weeks ago about how puppetry and writing share a lot of ideas and how some concepts of ideas of puppetry can used in writing. The core idea was that a puppet on stage has a really limited range of motions it can do (no facial expressions, rough body language, etc) and that one has to waste no space and give a lot of meaning to every thing that happens while not moving without meaning.
Writing the stuff like a scientist report would bore a lot of readers who aren't into that. Even just listing every single step can be way too much for a reader, because at some point they stop to care. Most people read webnovels to get entertained and not to read a detailed scientific report (real or fictional). So I would recommend to use concepts from both writing battle scenes (set the scene, then focus on the shifts in action) and the ideas mentioned above to describe it.
In short:
- The description of bouncing particles are only fun for a handful of times no matter the speech you use. There aren't that many different descriptions and it even gets silly if you repeat yourself with grander and grander words each time.
- So instead, don't waste those few times on unnecessary steps but on the "cool" ones. Start describing the particles on their own. For that, use interesting comparisons (a lot of fiction uses either bubbles in liquid or (moving) stars in space). One wonderful example (although reversed) is still this:
- After the status quo is established, concentrate on the times something changes. The first time particles group together. Afterwards, skip "and more came". "And a different type of particles came". "And then XY". Most readers don't care what cool real or fictional elements you can list. Even if they read through it, it'll become "meaningless motion" that
- When you concentrate on the important steps don't describe them on their own, but give those small movements a deeper meaning. "This is the first step on a long journey.", "This is the blueprint for a somatic cell.", "This is the first brain cell. It'll multiply and multiply until the being can think.", "This cell already contracting on its own. It'll later form a complex that pumps the blood through the body.", ...
For that two more examples from media:
Look at the background of the big bang theory and how they only pick some (not even all) of the most known events to display human history in 30 seconds:
Or a bit more scientific the way from egg cell to foetus:
https://blog.pregistry.com/wp-content/uploads/2019/02/AdobeStock_52637629.jpg
- On that note, make sure to use moments that are already understood by readers or those you can describe through easy comparisons. Don't explain your world's rules of gravity and evolution if not needed. Explain the most important steps with the least amount of needed extra information.
- Don't repeat the "same step but a little bit different". Nobody cares. Great fight scenes in writing aren't "And he swang his sword. Again. And Again. And a swing from the left. And a swing from the right. And a swing from the top. And another swing. And there was another swing." It's "their exchange continued for 3 minutes without anyone getting ahead, until finally [status quo] changes". And the status quo change isn't "he took a step to the left" but something that shifts the scene and matters. Detailed but endless fight scenes are often skipped by readers because "nothing important happens". (It's really obvious when something important happens in the middle of a fight (new character appears) and three chapters later everyone goes "Wait? Who is that person?")
So the way I would go:
Concentrate on the important moments, make it really visual ("and epic") for readers who don't like science, cut out all unneeded explanation (except you write for a core audience of hard sci-fi and the like), cut out scientific infodumps, and give every step a meaning that shows the reader that the tension builds and builds (particle -> ... --> cell --> cool cell --> mini living thing --> bigger living thing --> end).
