Librem 5 shipping schedule update

The problem with that logic is it prevents flexibility.

Let’s say to appease you they make the batch sizes:

A 25
B 50
C 100
D 100
E the rest

Yay now you know the batch you’re in and they can almost certainly meet their expectations.

But what if during the deployment they find things are going well and they can ramp up to:

A 25
B 100
C 1000
D 2000
E the rest

Well now you have a few thousand people you are putting in earlier batches that weren’t expecting it and may have changed their minds from when they responded with their preference so there’s a whole bunch of extra communication required which then results in what actually goes out being

A 25
B 75
C 500
D 750
E the rest

Now there’s a bunch of unused hardware and they haven’t met the revised expectations so now you’re unhappy again.

In the name of openness if everyone had been given a sequential order number then they could publish the current shipping order number and that might be a middle ground and you could know how far away from your order number they are and roughly how many are shipping per day. Even with this I don’t think committing to specific batch sizes does anything other than impose arbitrary hard limits that greatly reduces flexibility.

2 Likes