163: Resolving Disagreement and Friction with Event Storming

Writing as the new currency and reducing friction with Event Storming

Thank you for reading Snippets of Text. Snippets from media about tech, programming, parenting, and more. This is a preview of a post available exclusively to paying subscribers. You can get unlimited access to all articles by purchasing a subscription.

Off Topic: Currency in a Knowledge-Driven Economy

Everything is already out there. Art is the re-arranging of the known. Take the time to understand it. It also suggests that information exists in nature; hence, we remix what we learn. The Knowledge-driven economy we live in right now drives the need for the production and sharing of ideas. The new currency will be based on information. Either technical or abstract. Content creation provides a way to exchange knowledge instead of time. There’s no need to sell knowledge per hour. Ideas are the most valuable currency in a knowledge-driven economy; share them. When you create content, people can access your knowledge without wasting time. As an investment account allows your money to grow day and night without your involvement, content does the same with your ideas. 

[^]: Building a Second Brain

Current Work: Resolving Disagreement and Friction with Event Storming

During an Event-Storming session, it is common for disagreements to arise, which can state areas of friction. This friction can often be caused by ambiguity in naming conventions or conflicting concepts. Recognizing that team members may have different ideas and perceptions of the same problem is essential. Two key terms must be understood to understand event storming: a domain event and a domain expert. Yet, domain events represent facts about the domain, which only change when the underlying business changes.

Thank you so much for looking at the free preview of Snippets of Text! Please consider subscribing to the paid version if you find what I'm doing helpful. That way, I'll have more time to develop and share new ideas. Thanks again!