Andy Weir's Project Hail Mary: What Fiction Writers Can Steal from a Novel Built on Questions
Spoiler policy: This piece discusses the book's opening structure, its POV mechanics, and a few mid-novel craft choices freely. One significant plot development from roughly the halfway point is mentioned in general terms. If you want to go in completely cold, read the novel first. You won't regret it.
Most craft advice about opening chapters tells you to start with action, or conflict, or a character doing something that reveals who they are. Project Hail Mary does something stranger: it starts with a character who cannot tell you who he is, where he is, or why any of this matters. Ryland Grace wakes up alone on a spacecraft with no memory, two dead crewmates, and the narrative equivalent of a blank page where his identity should be.
The instinct for most writers faced with that setup would be to fill the gap fast. Get the reader oriented. Drop in a flashback. Have Grace find a journal. Andy Weir does the opposite: he makes the gap the engine.
The Question Is the Plot
Weir's core structural bet is that not knowing can drive a story just as hard as knowing. Every chapter in the early section of the novel is organized around a question Grace can answer by the end of it. What are these organisms on the solar collector? What does this instrument reading mean? Why are my legs not working yet?
Notice what this does for pacing. Each chapter has a built-in micro-arc: problem, investigation, partial answer, new question. The reader never finishes a chapter feeling cheated, because something was resolved. But the resolution opens the next door. Weir is essentially running a mystery structure inside a science fiction premise, and he doesn't need a detective or a crime to do it.
If your novel stalls in the middle, look at your chapter architecture. Are your chapters organized around questions the reader can watch the protagonist pursue? Or are they organized around events you need to convey? Those are different shapes, and only one of them keeps people reading at midnight.
Scientific Realism as Voice, Not Texture
Here's the trap writers fall into when they try to write hard science fiction: they treat the science as texture, as atmosphere, as proof they did their research. It sits in the prose like furniture description in a literary novel, present, detailed, inert.
Weir uses science differently. For Grace, working through a physics problem is characterization. The way he thinks about equations, the pleasure he takes in a clean solution, the frustration when the numbers don't cooperate, all of that tells you who this person is without a single line of backstory. The science isn't decoration. It's dialogue between Grace and the universe.
The lesson generalizes beyond hard SF. Whatever your protagonist's expertise is, surgery, carpentry, competitive chess, bread-making, let them think in that domain on the page. Don't just have them perform the skill. Let the reader watch how their mind moves through it. That's where character lives.
Writing for the Reader, Not the Camera
Weir writes for comprehension, not cinematics. His prose doesn't frame shots; it builds mental models.
This is worth sitting with if you've been told to "write visually." Visual prose, done badly, produces a string of camera angles. Weir's prose produces understanding. When Grace is trying to figure out how the Astrophage (the novel's central organism) behaves, Weir walks you through the logic step by step, in Grace's voice, in real time. It's closer to a worked example in a textbook than a film scene, and it's completely gripping, because you're solving the problem alongside the character.
Your novel doesn't need to be science fiction to use this. Any scene where a character reasons through a problem can be written for comprehension rather than image. Let the reader's brain do work. That engagement is its own reward.
The Lone Protagonist Problem
One of the harder craft challenges in Project Hail Mary is one Weir doesn't advertise: a single character, alone, for a significant stretch of the novel. No antagonist to bounce off. No ensemble to carry scenes. Just Grace and the problem.
Weir solves this partly through the amnesia structure (the flashbacks to Earth provide secondary characters and a second timeline), and partly through a mid-novel development that I'll leave vague for spoiler reasons. But there's a third solution that's easy to miss: the ship itself becomes a character. Grace names things. He talks to instruments. He gives the inanimate world a kind of personality through his relationship to it.
If you're writing a confined or isolated story, that's worth stealing. Objects, spaces, and systems can carry relational weight if your protagonist treats them as having personality. It's not magical thinking in the text; it's just how isolated humans actually behave, and it creates something for the reader to watch besides one person thinking.
Amnesia as Architecture, Not Gimmick
Amnesia in fiction has a bad reputation, mostly because writers use it as a mystery box: what happened to this character? The revelation is the point. Weir uses it differently. Grace's amnesia isn't primarily a mystery to solve; it's a delivery mechanism for information the reader needs at exactly the right moment.
The flashbacks arrive when Grace's present-tense investigation has reached a point where knowing his past actually changes how we read what's happening now. The structure is precise. That's the craft move: not amnesia as secret, but amnesia as controlled release. You decide what the reader knows and when. The character's memory loss just gives you a clean mechanical reason to exercise that control.
If you're writing any kind of non-linear structure, ask yourself: is each piece of past information arriving when it will hit hardest, or when it's convenient for you to deliver it? Those are different questions, and the first one is harder.
A Note on Nexa, If You're New Here
Writing Nexus has a built-in story coach called Nexa. She works like a developmental editor embedded in your drafting process: you can bring her your structure questions, your chapter outlines, a scene you're not sure is working, and she'll push back, ask the right questions, and help you think through the decision rather than making it for you. She doesn't write your novel. She helps you figure out what your novel is trying to do and whether your current draft is doing it. If the chapter-architecture question above made you want to audit your own manuscript, that's exactly the kind of conversation Nexa is built for.
What to Take to Your Own Draft
Here are four concrete things Project Hail Mary can teach you, stripped of the spacecraft:
Give each chapter a question it answers. Not a theme. Not a mood. A specific thing the reader didn't know at the start of the chapter that they know by the end.
Let expertise be characterization. Whatever your protagonist knows how to do, let them think in that domain. The texture of expertise is personality.
Write for comprehension, not cinematics. If a scene requires the reader to understand something, walk them through it in the character's voice. Don't just show the result.
Control information release with intention. Whether you're using flashbacks, amnesia, or simple scene sequencing, ask when each piece of past or contextual information will land hardest. Then put it there.
If you want to work through how any of these apply to your specific project, start with your novel's structure at Writing Nexus and bring your questions to Nexa. The architecture decisions are yours. Having a thinking partner for them makes the work faster and sharper.
