This sunset will make us rich

Pawel Halicki

Artwork for the Business Sci-Fi story "This sunset will make us rich"

Four humanoid robots are working beside the aircraft, two at each baggage belt. They feed suitcases to the handlers inside the holds. A tug operator brings the next cart. Behind the marked trial boundary, the engineer checks the live trial recording. Her business partner is watching the sun emerge beneath the clouds.

— This sunset will make us rich.

— Don’t say that on the recording.

Her partner checks her headset.

— Was I live?

Their client chuckles.

— Every word.

The sunlight is stretching across the wet tarmac. Beside the forward conveyor, a robot supports a bulging suitcase underneath rather than lifting it by its handle. Their client continues.

— Those always worry me. Not the stitching, but people who think a handle means you can pull anything by it.

The robot settles the case onto the belt. Its metallic colleague places another one behind it, leaving room between them. The engineer confirms.

— Still inside the loading requirement.

— And now you’ve got your weather.

— Yup. The last one on the list: delayed loading, low sun, wet surfaces. We hadn’t tested all three together.

— If tonight goes well, that’s your field-test checklist complete. Procurement is already talking about six more airports.

Her partner smiles at her. The engineer keeps watching the robots. A silver case reaches the front of the cart. Water beads along its ribs. The nearest robot lowers its wrist camera, pauses, then changes the angle. On the tablet, the case’s photograph appears beside its reconstructed shape. The handle is clear in the photograph. In the reconstruction, the space beneath it breaks into scattered points.

— It can see the handle.

— But it can’t measure the space behind it well enough to trust the grip.

— Glare?

— Yeah. The reflections change between camera angles. We can clean up the images, but we can’t recover what the cameras never captured.

The robot tries a lower position.

— Will it call someone?

— If it can’t find a suitable approach.

The robot’s request passes to its partner. The second robot finishes placing a suitcase, then steps between the silver case and the sun. Its shadow crosses the handle. The scattered points fill in. The first robot checks the gap and lifts. The second returns to loading. The client smiles.

— You taught them to stand in each other’s light.

— We’ve given them ways to improve each other’s measurements.

— That sounded less expensive before you explained it.

— Wait until you see the invoice.

At the rear hold, the other two robots continue loading without pausing.

— Why aren’t those doing it?

— Different angle. They don’t need to.

— Same software?

— Yes.

A dark, glossy suitcase follows the silver case. The robot requests another shadow. This time, its robotic colleague is approaching the belt with a heavy suitcase. The request waits.

— Why doesn’t it help?

— Watch the conveyor.

The handler inside briefly stops the belt to rearrange the luggage, then starts it again. The second robot places its suitcase on the belt and moves over to provide shade. The first robot lifts its bag and places it on the belt. Before the second one can return to the cart, another request comes in. It turns back. Inside the hold, the baggage handler watches the belt run empty.

— Can you keep them coming?

On her tablet, both robots show green. Below them, the loading rate drops.

— Both robots are doing what they’re supposed to. So why are we falling behind?

— Because helping one another takes time away from loading.

Another shadow request appears. This time, the first robot changes its grip while the second keeps loading.

— And if they both need help?

— They try another grip or ask for help. If loading starts falling behind, they hand the difficult bags to your crew sooner. The closer we get to departure, the less time they spend trying.

Some passengers boarding the plane start taking pictures of the robots handling their luggage. The client studies the display.

— What happens if we only use the software they came with?

— They load the bags, try different grips and call for help when they’re stuck.

— So why do we need yours?

— Because a robot passing every test doesn’t mean the whole operation works at a crowded airport.

The engineer brings up the loading figures.

— The robots already know how to handle luggage. Our software helps them work together, with your people and equipment. Then we test what the whole operation can actually deliver.

The baggage handler’s voice comes through her headset.

[Forward belt. Handles towards me on the next two.]

The request appears on her tablet. Both robots turn their cases before placing them on the belt. The handler pulls the first towards him.

— Very impressive robots. But we’re still loading bags. What would you improve next?

The engineer brings up two sets of results.

— We’ve tested two configurations. This one prioritises speed. That one gives the robots more time to find a safe grip. Fewer retries, but slower loading.

— Could either miss the departure target?

— Neither has so far.

— We already load on time. Airlines don’t need another minute from us. They need fewer damaged bags. That’s where I want us to stand out.

— Then that’s the configuration I’d put into the longer trial.

The client watches a robot tuck a loose strap underneath a suitcase before lifting it.

— So tonight’s a pass?

— For this condition. The longer trial will tell us whether it holds up.

The client folds his arms.

— Send me the report tomorrow. I’ll support the longer trial. Procurement can wait for the results before rolling this out.

Her partner glances at the tablet.

— So, the other airports are using the same robots?

— Mostly. We use a different supplier at some airports.

— Then we’ll need to test those separately. The same software doesn’t mean the same results.

— Of course.

A robot moves into the sunlight. Its metallic colleague’s shadow falls across a wet handle. The client watches the case rise.

— If this works, I can choose the next fleet based on the operation I want to run. Not just which robots give the best demonstration.

The engineer glances at the setting sun.

— Now you can say it.

Her partner looks at the recording indicator.

— Nah. Let’s finish first.

Artwork for the Business Sci-Fi story "This sunset will make us rich"
Why build memories from a future that hasn’t happened?

Narrative Microdosing is how you practise futures thinking and build your ability to navigate uncertainty. Instead of predicting whether this future will happen, you temporarily imagine that it already has.

Start with something familiar, then use the prompts to explore what this future could mean for you, the people around you, and the organisation or community you know. That turns an abstract future into specific possibilities, tensions, questions and language grounded in real life and work.

Repeat with more stories to build more futures you’ve already thought through, and more reference points for navigating change.

Three prompts. About 10 minutes. No right answers.

A page from the Practical Futures white paper, with brain scans of remembering the past and imagining the future

Memories to build from this future:

Think about the last time your phone updated itself overnight. In the morning, the screen looked a little different, and your thumb went to where a button used to be. The update promised to make it faster and smarter. It still couldn’t do the one thing you wanted.

‍

Now, stay with what you wished it had got better at:

01

Go back to a regular day when a service you used could reorganise how its people and machines worked together to deliver the result you cared about most.

What did you ask for that the service couldn’t have delivered before?

How did your everyday life change once the service adapted to what mattered to you?

Which trade-off were you willing to accept to get the result you wanted?

02

Try to recall a regular month when your team could rewrite the rules for how people and AI worked together, and the work rearranged itself to match.

Which result mattered enough for your team to change how the work was done?

What became possible for the people relying on your team once you changed how everyone worked together?

How did your team respond when the new arrangement improved one result but made something else harder?

03

Think back to a regular quarter when your organisation could rewrite how its people and machines worked together, test different versions, and put one into practice.

Which outcome became possible that your old way of operating couldn’t deliver?

What did your organisation discover it wanted to be best at after seeing different versions of itself handle the same week?

What did the tests leave unanswered when it was time to choose which version to use?

To round this one off.

‍

If the thing everyone around you keeps trying to speed up were already fast enough, what would you want it to be good at next? What small test would you be curious to run first?

‍

And does anything from this one keep showing up across other sessions?

Key Takeaway

The better our systems get, the easier it is to mistake improvement for progress. The same systems that perfect yesterday’s priorities can free us to pursue something better tomorrow.

Emerging Signals

Evidence this future may be closer than you think

Futures Thesaurus

Words from this future to play with

One future down. Plenty more to explore.

New science-fiction stories, emerging signals and essays exploring how life and work could change. Fresh perspectives and questions worth thinking about, delivered to your inbox.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Unsubscribe any time. Privacy Policy