One of the quickest ways to design a bad Morocco itinerary is to look only at distances.

The map says a route is possible.

Technically, it is.

That is not the same as saying it is a good idea.

I learned this more clearly once tourism put me on Moroccan roads regularly.

A distance is a number.

A road has a rhythm.

Those are different things.

Two hundred kilometres can mean very different days

Morocco changes quickly.

You can be on a fast road, a mountain road, a narrow road through villages or a long open stretch where the kilometres are easy but the day is still tiring.

Weather changes things.

Traffic changes things.

Stopping changes things.

And stopping is part of the point.

If somebody travels all the way across Morocco but experiences the country mainly through the window because the itinerary is trying to defeat mathematics, I do not consider that efficient travel.

It is just fast.

There is a difference.

The road is not empty space between attractions

This became one of the ideas behind how I think about Arhhal.

A lot of itineraries are written as a sequence of destinations.

Marrakech.

Dades.

Merzouga.

Fes.

The road appears as an arrow.

But the arrow may contain most of the day.

If you treat that time as transport that simply needs to be completed, you have missed a large part of travelling through Morocco.

Landscape changes.

Architecture changes.

Weather changes.

The food changes.

The way people speak changes.

Even the light changes considerably across some routes.

The road is not an inconvenience separating the “real” experiences.

It is one of them.

More stops do not automatically make a better road day

The question should not be how many things we can physically fit between departure and arrival.

It should be whether each stop improves the day enough to justify taking time away from something else.

That sounds obvious.

Tour itineraries regularly ignore it.

Travellers experience time, not kilometres

If I tell somebody a drive is 300 kilometres, that does not tell them how the day will feel.

If I explain that it is a long road day with mountain sections, several worthwhile stops and a late arrival, now they can actually judge it.

This matters particularly with private travel because one of the advantages of a private journey is having the ability to change the rhythm.

Families with children may need a different day.

Older travellers may want fewer stops and more comfortable timing.

Some people love road days.

Some people absolutely do not.

A good itinerary should know the difference before it congratulates itself for including more Morocco.

Google Maps is useful. It is not a tour operator.

I use maps all the time.

Obviously.

But software answers a different question.

It can estimate how to get from A to B.

It does not know whether the person in the passenger seat has already spent six hours in a vehicle yesterday.

It does not know whether another two-hour detour is worth it for this particular trip.

It does not know whether somebody cares about the place you are adding.

That requires judgment.

Technology improves planning enormously, but I do not want to outsource the decision itself to a route calculation.

The road teaches you to respect trade-offs

That may be the biggest lesson.

Every itinerary is a set of trade-offs.

More places means less time in each place.

More stopping means later arrival.

A relaxed morning changes the afternoon.

Adding somewhere means taking time from somewhere else, even when the itinerary designer pretends otherwise.

Once you spend enough time actually travelling those roads, these trade-offs become difficult to ignore.

I think that is a good thing.

The aim should not be to prove how much Morocco you can fit into a week.

The aim is to make the week worth travelling.