[tossandthrow]

"it's your call" does not mean there are no requirements.

On my team it is always people's own call, but they also need to be critical thinkers and call for the right thing.

If a manager, denotationally, can call out that there is something missing, then it was not implemented right.

[enraged_camel]

“It’s your call” specifically means all the decisions on the table are valid and fit the requirements and the employee is being granted permission to make a judgment call. Questioning that judgment call afterwards is shitty and leads to an erosion of trust because the employee will thereon second guess themselves and also try to avoid making any decisions (because they expect them to be overridden).

[jsiepkes]

> and fit the requirements

And that is where the friction is. A lot of these requirements are implicit.

For example; If an application is built around Protobuf / gRPC and you suddenly start doing JSON / REST you are going to need a really, really good reason for that. Since you are introducing a new technology, with all it's glory and all it's horror. So your judgment is going to be questioned on that and most likely the reaction will be; We are not going to do that.