The fastest way to make a future feel artificial is to let everything work perfectly. Doors open exactly when they should. Transit never pauses. Every interface understands the first request. The technology may be impressive, but the world can start to feel like a showroom.

Real life is full of small negotiations with systems that mostly work. A printer needs paper. An elevator is being serviced. An app wants an update at the worst possible moment. Speculative worlds become more convincing when their extraordinary inventions develop equally ordinary irritations.

Start after the miracle

Suppose your city has elevators that can travel sideways between towers. The obvious scene is a visitor staring through the glass as the cabin crosses open air. A resident is more useful if she barely looks up.

At 5:12 p.m., Nemi reaches the lift and finds a yellow strip across the panel: CROSSWIND MODE — LOCAL STOPS ONLY. She sighs, takes the service stairs down two floors, crosses a pedestrian bridge, and complains that the city always schedules filter cleaning on windy days.

Nothing in that moment explains how the elevator works. It shows something better: people have been living with it long enough to have shortcuts, complaints, and expectations.

Make the inconvenience belong to the world

Random malfunction is not enough. If every futuristic device simply breaks when the plot needs trouble, the setting starts to feel manipulated.

Let the annoyance grow from the invention itself. A house that rearranges its rooms might require residents to label the furniture it must never move. Instant translation might handle formal speech beautifully and stumble over family nicknames. A delivery drone network might make groceries effortless but turn every apartment balcony into a noisy landing schedule.

The limitation does not need to become the story's central conflict. Its job is to suggest that somebody designed this technology, somebody maintains it, and millions of people have already adapted their habits around it.

Let characters complain instead of explain

A complaint can carry worldbuilding because it assumes knowledge. “Not another calibration day” tells the reader that calibration exists, that it happens repeatedly, and that people dislike it. You can explain the mechanism later if the mechanism matters.

This also protects dialogue from becoming a disguised encyclopedia. Two residents rarely tell each other facts both already know. They do compare delays, blame bad design, remember how the old version worked, and argue over whether the inconvenience is worth the benefit.

Try it in a draft

Take the most impressive technology in your setting and give it one minor, recurring inconvenience. Then write a short scene in which the character wants something unrelated—a coffee, a quiet commute, five more minutes of sleep—and has to work around it.

Do not explain the invention's history. Show the workaround first. If the reader can infer what kind of world produced that annoyance, the setting has started to feel inhabited rather than displayed.

Part of Beyond the Known, an independent journal by Arin Vale.

Related reading: Build a World Through Breakfast — another way to reveal setting through ordinary life

Read our editorial approach