One of the challenges I see regularly is inertia following domain discovery workshops. Techniques like big picture event storming are great for mapping out the business and visualising problems and opportunities, but that’s where progress can easily get stuck. How do you go from event storm to product and organizational improvements?

I recommend mapping out your domains on a core domain chart, exploring how you could evolve each domain, and creating a scorecard to decide which you should invest in.

Often, companies want to combine improvements to their products with improvements to their operating model and ways of working. In…


There’s an aspect of Domain-Driven Design that rarely gets talked about. I think it’s the most important aspect of DDD, yet if you search online for “Domain-Driven Design”, you won’t find it.

This treasure has been hiding in plain sight all along. It’s the Share Pie story in chapter 8 of Eric Evans’ DDD book.

To me, this story is what DDD is really about: developing the design mindset of a modeller to drive product innovation and enable continuous delivery of value, involving frequent collaboration with domain experts.

It’s also just a great story which I never get bored of…


If you would like to learn or practice how to break up a large business into domains and use them as the foundation for your software architecture and team organization, I have created a strategic domain-driven design kata that you may find useful. It’s based on the industry of online takeaway ordering and delivery using a fictitious business called Delivericious.

You can find the Miro board here: https://miro.com/app/board/o9J_l45tkpU=/

The instructions are quite simple: open the Miro board using the link above and copy and paste all of the content into a Miro board of your own. …


There is a long list of things I love about visual discovery and modelling techniques like Event Storming and Example Mapping. But there is one benefit of visual techniques which I find so valuable and yet doesn’t get the recognition it deserves: pattern reading.

What I mean by pattern reading is looking at the visual artefacts and making inferences about what the layout may be telling us. In every workshop, I always ask everyone “Imagine there is no text here. What is this arrangement of colours and shapes telling you?”.

I’ve invented the term pattern reading but I’m happy to…


In business, technology and general, the word “domain” appears frequently and with many different meanings in various contexts. This gets tricky at times when collaborating with different companies or communities that use different definitions.

The problem in general is that when we use generic and fuzzy words like domain we make assumptions that put the emphasis on the listener to correctly determine the context and choose the right meaning.

Because domain is such a common word in our world, I think there are a couple of reasons why it’s highly beneficial to have a deeper understanding of the word and…


Modernizing an architecture usually take years. Even a decade or more is nothing out of the ordinary for large organizations who have accumulated legacy and heritage systems over long periods of time.

This presents technology leaders with one of the most difficult modernization challenges: where to start and in which order to modernize?

There are usually a number of factors which greatly complicate the situation. The need to keep delivering product enhancements and new innovations while modernization is in process is one big factor, and dependencies between modernization work items is another.

Often there is a tension. Starting with a…


Mapping out your business’s domain landscape has many benefits: knowledge sharing, generating product ideas, providing the foundation for software architecture, aligning on requirements, but a common challenge is… “where do we start?”

There’s a pretty endless list of techniques to choose from and an unlimited combination of ways in which they can be applied. Discovery feels more of an art than a science. However, I find myself gravitating towards an outside-in approach most of the time.

An outside-in approach starts with the business model, the user needs, and step-by-step zooms into the inner-workings of domains. I like this approach because…


The microservices era has been good for software architecture. I remember when the idea of multiple databases was punishable by death. But, the over-focus on micro has detracted from the true benefits of microservices which are about improving the quality and speed of development.

Over the past couple of years, I’ve seen organizations referring to microservices as Domain Services. I’ve seen such benefits from this small reframing that I now recommend not using the word microservice and using Domain Service instead.

There have been many criticisms of microservices and many horror stories. But I don’t wish to bad-mouth microservices in…


There are a few qualities that differentiate average from high performing software engineering organisations. I believe that attitude towards the design of code and architecture is one of them.

In my experience, the culture is better and the results are better in orgs where engineers and architects obsess over the design of code and architecture. In orgs where it’s all about delivering tickets as quickly as possible or obsessing over technology, the culture and results are poorer.

There’s huge variety between those two extremes, and there’s also a point where too much focus on design and not enough on delivery…


In February 2012 I began working for a new company. On my first day, I deployed to production. I was lost for words. It felt like magic. Every day was the same: pick the highest priority item, implement it, and then deploy to production immediately. After 6 months, I was still pinching myself.

The experience for me as a developer, the Developer Experience (DX), was energising and motivating. Instead of fighting against processes to get my job done and get my code into production, I felt like the red carpet was being rolled out for me.

As a result of…

Nick Tune

Technical Leader | Socio-Technical Architect | Continuous Delivery

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store