Operational level agreement: the internal promises an SLA depends on
An OLA is what each internal team owes the one facing the customer. Without it, an SLA is a promise made on behalf of people who never agreed to it.
Employee engagement is a real signal wrapped in a bad habit. The measurement is cheap and useful; the annual survey followed by no visible change is what turns it into a running joke.
Employee engagement is the extent to which people are willing to put discretionary effort into work they could do adequately without it. It is not happiness, and it is not satisfaction — a comfortable team with nothing to do can be perfectly satisfied and entirely disengaged. It correlates with the things a business notices later: turnover, quality, absence, and how quickly problems get reported rather than hidden.
The concept has a bad reputation, and the reason is not the measurement. It is the pattern: a long annual survey, three months of silence, a slide deck of averages, and nothing anyone can point to that changed. Ask a second year and the response rate drops, which is itself the most honest engagement metric you will collect.
Anonymity has to be real or not claimed. A survey that promises anonymity while collecting team, role and tenure in a company of thirty people is identifiable, and everyone answering knows it — which is why those results skew positive. Either aggregate hard enough that individuals genuinely cannot be picked out, or drop the promise and ask openly.
It cannot fix pay that is below market, a manager people are afraid of, or a strategy nobody believes in. Surveys measure symptoms, and running one over a known structural problem is worse than not asking: it demonstrates that leadership would rather collect data than act. If you already know the answer, spend the money on the fix rather than on the measurement.
Ettex Teams holds the team structure the results get segmented by, and the survey itself runs in Ettex Forms — the mechanics of writing questions people will answer are covered in customer feedback surveys, and the performance-review flavour of asking is a separate exercise in 360 degree feedback. Actions coming out of a round belong on a board with owners and dates like any other commitment.
What we do not provide: there is no engagement benchmarking against industry data, no sentiment analysis of free-text answers, no engagement score model, and no guaranteed-anonymous response pipeline beyond how you choose to configure the form. Those are the province of dedicated engagement platforms, and if benchmarking against a peer group is the point of the exercise, buy one.
Satisfaction is how content people are with conditions. Engagement is how much discretionary effort they are willing to give. A satisfied team can be entirely disengaged, which is why the two need separate questions.
Quarterly with a short set of repeated questions works better than annually with a long one. The frequency keeps trends readable and the brevity keeps response rates up.
Only if the anonymity is genuine. Collecting team, role and tenure in a small company makes answers identifiable regardless of what the introduction promises, and people answer accordingly.
The trend matters more than the level. A rate falling round on round is the clearest signal that previous rounds produced no visible change — which is a finding in itself.
An OLA is what each internal team owes the one facing the customer. Without it, an SLA is a promise made on behalf of people who never agreed to it.
IT general controls decide whether you can rely on anything a system tells you. Weak ITGC does not fail on its own — it invalidates the controls above it.
Segregation of duties splits a transaction so that committing fraud or hiding an error requires collusion. Most breaches of it are accidental, and invisible until tested.