Sci-Fi Eye: What can engineers learn from writers?

It might seem unlikely, but writers and engineers approach projects in very similar ways, whether it’s building a bridge or writing a novel. Authors spend their time creating strange new worlds, fascinating characters, and uniquely imagined stories. By embracing their creative side, engineers can think ‘outside the box’ to produce ground-breaking and innovative solutions.

Before an author writes a single word, they often sit down and carefully plan their narrative. They need to know that their story will work and not contain inconsistencies or errors that will derail their reader, and so they spend a great deal of time thinking about every possible outcome of each scene. In the same way, an engineer needs to put together a plan that pays attention to all possible contingencies. We all know the apocryphal story of the architect who designed a library but forgot to account for the weight of the books that it would house, with the result that its foundations began to sink into the ground. Embracing the mindset of care that authors take in their work can assist engineers in preventing errors and producing well thought out solutions.

Once the plan has been drawn up, the correct team must be assembled. For an author, that means they must select the best characters to play key roles in the story. Similarly, when putting together a team for a project, engineers must make sure every person is there for a specific function, and is the person best suited to that position. If the author chooses the wrong characters, the story won’t work, and the same applies in engineering. You need the right people in the right place at the right time.

One of an author’s key skills is the ability to convey complicated information clearly and compellingly using only the written word. By learning to communicate more clearly, engineers can articulate technical concepts in a clear and compelling manner, fostering better collaboration, and understanding to ensure their team members, clients, and stakeholders all have the correct information and all understand the status and progress of the project, as well as their roles in it.

Just as authors need empathy and understanding to put themselves in the shoes of their characters and understand what drives them and makes them tick, so engineers can also employ the same techniques to consider the wants and needs of the end-users of their products or systems. By considering the needs, feelings and preferences of their clients and end-users, engineers can be sure they’re designing a solution that is user-friendly and meets expectations.

While writing, authors often face unexpected plot twists, critical feedback from editors, and sometimes the need to work on several projects at once. Engineers also come up against unexpected challenges throughout the development process. Taking a leaf from authors, engineers can learn to be agile, embrace change, and think on their feet, finding creative solutions to unexpected obstacles.

I mentioned editorial feedback there. Once an author has finished their manuscript, they will often show it to a few trusted friends and maybe their agent, who will give them feedback about what does and doesn’t work. Good authors embrace this feedback. It helps them see their story through fresh eyes and make changes that strengthen and improve it before they submit it to a publisher. Collaborative feedback from colleagues can help engineers see their projects more objectively, and spot weak points that might have otherwise gone undetected.

Similarly, once an author delivers their manuscript to a publisher, the in-house editor will read through the manuscript and suggest changes that make the story more readable, of higher quality, and more in tune with their house style and the expectations of their readers. This is the same as when engineers deliver a solution to a client and receive feedback on the quality and useability of their product or service. Taking this feedback on board helps tailor the finished item to its intended users.

 Stephen King says, “If you don't have time to read, you don't have the time (or the tools) to write. Simple as that.” And by that, he means that authors need to be constantly learning and improving their craft, as well as steeping themselves in the literature around them by exploring new genres, styles, and ideas. Engineers can adopt this mindset of continuous learning by keeping abreast of the latest advancements in their field, attending conferences, and seeking novel techniques and approaches that can transform their work.

Gareth L. Powell is an award-winning science fiction author from the UK. His tenth novel, Descendant Machine, is out now from Titan Books.