November 2025 Operating Principle of the Month - Surface issues constructively (Transparency)

Surface issues constructively - (a Transparency operating principle).

If you drop by to have a read, please leave a reaction!

During November 2025, the APAC Support Team call will have a section to chat about this operating principle. Feel free to join the conversation here in the issue, or create your own discussion prompts relevant to your group.

Discussion Prompts

1. Awareness: This is an OP that we often see very publicly lived out at GitLab, and by seeing it, we are more confident to embrace it. I think many of us would have found this one a bit confronting in previous roles. How have you seen this one lived out at GitLab, and what positive impact has that had on you, and for our customers?
2. Curiosity: What makes it hardest for you to surface issues constructively? Is it knowing when to escalate, knowing how to frame it, fear of the reaction, or something else? What do you need to change that?
3. Action: The description on this one is quite heavily weighted on surfacing mistakes, but it extends to more than that - in an environment where much of what we do is async, surfacing issues effectively is a necessary skill. How can you most effectively and efficiently communicate an issue? As the recipient of that information, what do you need to be able to act on it rapidly?
4. Closing Thoughts : Anything goes! A final chat to end the conversation, that considers previous weeks' discussions, and any async discussion that occurred here in the issue. Also a good time to suggest an OP for next month if there is one you'd particularly like to see discussed!

This is not APAC exclusive, nor is it Support team exclusive - everyone can contribute! Please leave your thoughts, comments, ponderings here on the issue!

At the end of the month, this issue will be closed and a new Operating Principle of the month discussion issue will be created and linked to the epic.