There are several techniques available to derive to design your bounded context and domain models. I like to start then with event-storming to focus on the specific part of the system, identify what is happening in your domain. It's usually reflecting a user journey on your water map. From there I apply the tintepologies and specs trying to bring in where are the potential stream of changes that are then reflected by the user needs. And also having the team cognitive load in mind, so components on the further left of water map, they tend to require a high-tech team cognitive load because there's no clear path to action.

Get the Snipd
podcast app

Unlock the knowledge in podcasts with the podcast player of the future.
App store bannerPlay store banner

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode

Save any
moment

Hear something you like? Tap your headphones to save it with AI-generated key takeaways

Share
& Export

Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode