Back to Blog

Business Analysts: Don’t Miss the Immense Power of Color Coding

LN Mishra

 

Color coding has been used by humanity for ages. The most famous one is possibly the traffic light indicators used across the globe to assist motorists and people. Unfortunately, most Business Analysts don’t use the power of color-coding. Here is our attempt to showcase a few use cases where color-coding can be immensely valuable to business analysts.

Scope Modeling

We all requirements analysts have been taught that models always convey more with less text. Models also improve requirements clarity. We all know how to model processes, activities, entities, and states. However, when the time comes to model scope, we all develop cold feet.

Most guide books say, try use-case diagram or functional decomposition. We can use these 2 techniques for in-scope items. What about out of scope or items whose status is undecided? decided?

Why not use the RAG indicators which almost everyone in the business can easily understand? Green (G) for in scope, Amber (A) for yet to be decided and Red (R) for what is out of scope. Here is one worked out example.

Suxeed Scope Model

Use Case Diagrams

For a long time, we, requirements engineers and business analysts have been using use case diagrams. Use case diagrams are pretty useful to indicate system features, actors, scope, and reusable functionalities. However, they all have been colorless - all black and white.

Let’s color the use cases to make them more intuitive. The color scheme proposed is as below:

Use Case Diagrams For a long time, we, requirements engineers and business analysts have been using use case diagrams. Use case diagrams are pretty useful to indicate system features, actors, scope, and reusable functionalities. However, they all have been colorless - all black and white. Let’s color the use cases to make them more intuitive. The color scheme proposed is as below:

Legends:

  1. In-scope: Green
  2. Out of scope: Red
  3. Doubtful: Yellow
  4. Misuse: Black
  5. Include: Blue
  6. Extend: Maroon

Process modeling

RAG color scheme can also be quite effective in process models. Here in this high-level process model, we understand 2 processes are performing well, Identify Prospects and Support Prospects, one process is performing not so great, Convert prospects and one process is under-performing, Nurture prospects.

 

Prospecting Process

Business model canvas

We also can use color-coding to indicate aspects of the business model canvas where the organization is performing satisfactorily, areas where it needs improvement and areas where it is performing poorly.

Business Model canvas

In this blog, we have attempted to demonstrate the utility of the color-coding technique. We are absolutely sure there will be many more techniques where color-coding can be very helpful.

Do share your inputs on where else color-coding can be effectively used by business analysts.

No link IIBA Prep Webinar CTA

Suggested Reading-

Requirements Life Cycle Management: Tools and Techniques

Fundamental Tools and Techniques Every BA Should Know

Prototyping: Discover User Expectations Before Implementation

 


Related Posts

Who should the Business Analysts report to

LN Mishra

Who should the Business Analysts report to?

Read more

Should business analysts learn data analytics

Ann

How much technical skills is right for a Business Analyst?

Read more