Since EventStorming is language and technology agnostic, we cannot model things like classes, fields, methods or functions. Instead, we need to use more universal concepts. We already discussed such thoughts in the CQRS section, and there we have seen that we can express the behavior in our domain model not just as a list of methods, but as the execution of commands. Commands express the user’s intent. Domain model then gets its state transitioned, and new events are produced, recording the purpose and state transition. Queries represent what users want to see on their screens to take decisions and execute other commands. So, this brings us some sweet elements for the design session, which are not related to any specific programming language or technology.