We were scoping a feature for the next release cycle, and I had visibility into a supplier constraint only three people on the org knew about. I made the call to descope it unilaterally, gave the team a vague technical rationale, and we shipped on time.
Treats unilateral opacity as neutral; no reflection on what that costs the team.
We were scoping a hardware feature and I had supplier constraints I couldn't share with the broader team of twelve engineers. I made the call based on what I knew, framed the tradeoffs around performance and timeline, and the feature shipped on schedule.
Executed cleanly but shows no awareness of the trust cost of withholding information.
We were scoping a feature cut two weeks before launch, and I couldn't tell the broader team why certain things were dropping. I hated that. I gave vague prioritisation reasons to 14 engineers, and some of them figured out something bigger was happening anyway.
Acknowledges the discomfort, notices team saw through it — shows judgment about judgment itself.