Home / Learn / Insights / Color your Knowledge

Color your Knowledge

A while ago a client asked me to look at some process diagrams which had been created for them by a well-known consultancy.

Improve your process diagrams using color and shape

A while ago a client asked me to look at some process diagrams which had been created for them by a well-known consultancy.

They were recognizably processes: they had a start and an end, some swim-lanes, and some activities. But some of the activities were blue, and some red. A a few were purple.

“What’s the difference between these colored activities” asked my client. “Are they important?”

“I hope not” was my reply.

There was no key to tell the reader what the colors meant. (But that was OK, because the consultants said they would be happy to come back and explain it all – for only USD1500/day.)

And that’s a shame really, because the original authors clearly had a plan in mind when they chose the colors: they were genuinely trying to use those colors to convey information to the reader.

So what do we think about color in models? And for that matter, shapes?

If the purpose of model curation is to convey information, then anything which does that is obviously good. But is more of it better?

In this article, I’ll skip the ‘develop the need’ stage (you know it anyway) and go straight to some suggestions:

Use color – but carefully

  • Pale colors. If I have a criticism of the diagram above, it’s that the colors are a too bright – distracting
  • Make it as easy as possible for your modellers to stay consistent to your color scheme
  • EVERY diagram MUST have a legend. No arguments about this
  • Don’t be afraid to invent your own – so long as you tell everyone WHAT and WHY.

Use shapes as well

A minority of modelling languages have two styles for their shapes. ‘Rectangle’ , and ‘not rectangle’. For example, here is an Archimate 3 diagram:

It’s a fairly dull diagram, but according to Archimates (sic) it’s full of meaning.

But using the ‘alternative’ notation (which one Archimate luminary described to me as ‘childish’) it would look like this:

A fraction more readable.

But add color as well (I know that Archimates use color for showing layers, but that’s only because lots of their diagrams are ‘look at me’ diagrams):

I think this is a good deal more readable.

So that’s it: use color, shape, positioning on the page, songs, modern dance, free chocolate: whatever it takes to get the information across.

And no technique – used thoughtfully – need be ‘childish’.

More Insights

Different documents for Different People

16 November 2018

How to tailor information to each user - making it as easy as possible for everyone to engage with your work, project or deliverables.

Learn More

Document or Model View?

21 May 2018

Use your documents as an alternative to Model Views.

Learn More

Context - Where are we?

20 October 2017

I’m occasionally asked “What’s the most re-usable bit of a model – where should I start?“.

Learn More


12 October 2017

In a recent talk, I asked the audience of about 100 BAs which of them maintained a glossary as part of their work.

Learn More

Hard and Soft

11 October 2017

No, not about Brexit… More about styles of Business Analyst.

Learn More

Printing connectors

18 October 2016

Creating documents that start with the connections between the things in your model

Learn More

Model curation techniques for EA

6 September 2016

How cleaning, navigating and validating your EA model makes sharing and collaborating much more effective.

Learn More

Branch/Merge with EA13

11 August 2016

One of the most common requests we see from new EA users is: "Why can’t I do branch/merge with EA?

Learn More

7 Steps to Agile Documents

8 September 2015

Or “How documents can HELP your project, not stop it"

Learn More

Compare pricing and features

Choose the eaDocX edition that’s right for you and your team

Compare Pricing

Download a free trial

Take a free, no obligation, 30-day trial of eaDocX. Discover for yourself why it’s the world’s best-selling Enterprise Architect extension.