When something new is introduced in an organisation, not everyone appreciates it straight away – especially when it affects the work environment: the light at the desk, the view, and the sense of control over your own place. Sooner or later you'll meet the person who isn't happy with how their particular shade behaves. That is not a failure. It is often the beginning of the fine-tuning that makes the system better.
Not everyone feels confident at the same time
People take to new solutions at different speeds. Some appreciate the automation immediately, many become positive once they see that it works in everyday use, and a smaller group needs more time, clearer explanations, or more control of their own.
That is especially true when technology affects the physical work environment. A shade does not just control energy and glare; it also affects daylight, views, heat, and the sense of self-determination. In traditional sun-control projects we've seen users wedge sticks into the window tracks to stop the shade from coming down. It looks like resistance, but it is often something very human: someone is trying to regain control over their place.
First line: give control back
The most immediate answer is therefore to give the person a simple way to influence the situation. With a keypad or the app, the user can take over their own shade when needed. The automation pauses, the user can solve the situation in the moment, and the system then returns to normal operation on its own.
Just knowing that the automation can be overridden often goes a long way. It makes the system feel less alien and more acceptable: the shade is no longer perceived as something that “decides over the room”, but as something that helps – and can still be told no when the situation calls for it. More on the two levels of control is in How do you get an autonomous system to do what you want?.
When the objection is concrete: adjust that unit
Sometimes a button is not enough. Then the next step is to take the objection seriously and adjust that particular shade. This can be done without changing the rest of the building.
There are two main paths:
- Change the decision model for the unit if that particular place actually needs different behaviour from the rest of the facade or zone.
- Keep the model, but adjust the parameters. If you want to keep the same overall logic – for example for energy follow-up or ESG reporting – but need to change thresholds, wait times, or comfort levels for that specific user.
The point is that the exception can be handled locally. One dissatisfied user does not have to become an argument against the whole system.
CONDUCTOR: see why – and explain
When a shade moves, it is natural to first look for the explanation in the automation: which decision model applies, which sensors are being used, what do the weather data, sun position, or temperature say? But the movement may just as well be caused by something else. Someone may have controlled the shade from their mobile app because it felt right in the moment. A local keypad may have been used. Or an administrator may have created a schedule several weeks ago that is now being executed exactly as planned.
If you have Pendax CONDUCTOR, the answer does not have to be a guess. There you can see what was behind the event: an autonomous decision, a manual command, a schedule, or another control signal. When someone says, “the shade just went down again – why?”, you can look at the event and explain the logic.
Sometimes that is enough. Irritation decreases when behaviour becomes understandable, and if the behaviour really does not suit the place, you also have concrete evidence for adjustment.
The dissatisfied person can be an asset
It is easy to call the person who complains difficult. But it is often more useful to see that person as an early signal. The one who speaks up tells you something about how the work environment is actually experienced – something others may also feel but not put into words.
Handled well, that feedback becomes valuable. You can explain, give control, adjust, and learn where the system needs to become more responsive. Then it often ends with both the individual user and the rest of the building getting a better shade.
To see how decision models and parameters are chosen, start in the configuration tool, or read How does the decision engine work?