Flagholm
Gift note stays off until someone names the number that would turn it on. We are not adding a flag so a meeting can invent that. Receipt copy is the one that is out: half of orders, tickets flat. Delivery window came back off. Late orders rose.
This is how Flagholm is used. Not a catalog of features. A change either has a number, or it does not go on.
Someone wanted a flag so the gift note could be tried. There is still no number that would say the note is safe to turn on. A meeting can want the flag and plan to pick the number later. We do not add it. The note stays on the old path until a person will say, before the switch moves, what they are watching.
The new wording on the receipt is the change. It is on for half of orders, not for everyone. The number was support tickets. Tickets stayed flat, so the change stays out. Half is not a compromise and it is not a brand campaign. It is wide enough to see the number, and still small enough to take back the same day.
A new window for when the order would arrive went out. Late orders rose. The owner turned the flag off. Customers are on the old window again. The new code is still deployed, and it is not what people get. That is the switch working. A rollout you can take back is not a failed release. It is the reason the flag was there.
Same rule on each of them. Name the change. Name the number first. Put it on for a few people, or a slice you can still reverse. If the number stays quiet, it can go to everyone. If it moves the wrong way, it comes off. When a change is in for good, delete the flag.
If the change you have looks like the gift note, do not write to ask us for a flag. Name the number. If it looks like the receipt or the window, write and say which.