October 2025 - Operating Principle of the Month - Embracing iteration (Iteration)
Embracing iteration - (an Iteration operating principle).
If you drop by to have a read, please leave an
During October 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
- Awareness: Try reading this as if you've never read it before (I know, tough ask!). What does it mean to you? Does this sound like the way you currently embrace iteration? Maybe this is an opportunity to take a fresh look at how you do that. Share your thoughts.
- Observation: How have you seen other people embrace iteration? What does that look like? And in contrast, what do you notice when people (maybe yourself?) don't embrace iteration?
- Action: I had a chat with Claude about this OP, particularly around the penultimate assertion to "Focus on sharing context at the end of the first iteration rather than a hypothetical future state that requires multiple iterations". In context of all the Iteration OPs, the result of that conversation was an interpretation of that statement to mean: "Don't over-plan future iterations - plan enough to ship the next iteration, then share what you learned." What do you think? And how do you do that? Or how could you do that if you're not already?
- 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!
There are discussion prompts here in the issue for async conversation. This is not APAC exclusive, nor is it Support team exclusive - everyone can contribute!
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.