One of the most popular tools I use with my clients for almost any kind of modeling is the Relationship Map. Relationship Maps are effective for many reasons:
- They are interactive
- They are scalable
- They provide a simple, understandable, comprehensive view of an organization on one page
In this post we will describe what they are, how to create one, and why they are so powerful.
Relationship Maps: What They Are
A relationship map is a simple, one-page diagram that shows the major functions of a department, who they interact with, and the nature of these interactions. I like to use a hub and spoke format similar to a mind map.
For example, I have provided a slide from a PowerPoint presentation I am giving at the Enterprise Architecture Conference at the end of March. To see this example, click on the link below:
Download example_relationship_diagram.ppt
In the center is an elipse that contains the name of the organization with a bulleted list of the major functions underneath. This elipse is surrounded by a number of satelite entities that the department interacts with in the course of their day-to-day business activities.
The main elipse is connected to the satelites by lines that depict the nature of the interactions. Using arrowheads one can see if the interaction is one-way, two-way, and which direction the information flows. Text is used on the lines to summarize the nature of the interaction.
How to Create a Relationship Map
To create a relationship map you'll need to get the key players of the organization into a room with a whiteboard. I start by drawing an elipse in the center of the whiteboard and write the name of the organization at the top of the elipse.
I ask the group, "What does this organization do?" I capture the answers on some work space on one side of the board. Within a few minutes you'll have a pretty good list of functions. With a little more effort you can work with the group to boil the big list down to about 3-7 major functions. Find some short names you can use to summarize each of these functions and put them in the elipse under the organization name.
I then ask, "Who do you do these functions with?" I then draw satelite circles around the elipse for each entity identified by the group. I connect each circle to the main elipse with a line.
I finally ask, "What is the nature of these interactions?" I put arrowheads on each connecting line to show the direction of the flow of information. I also provide summary text on each line to capture each interaction.
Within 30 to 60 minutes I have a simple, understandable, but comprehensive overview of the organization.
What Makes Relationship Maps So Powerful
Relationship maps are powerful for a number of reasons:
- They are fast. With the right people in the room you can create one in less than an hour.
- They provide a comprehensive overview on one page.
- The capturing process unites the team. Working together has a unifying effect on the team.
- They save time. The map can be used to provide context to people inside and outside the department without recreating the wheel every time context is needed.
- It provides a good launching point or foundation for more detailed discussions.
In short, relationship maps work! Try it out yourself.
- Have you tried this method?
- What is missing from my suggestions?
Please click on the comment link below to share your thoughts and ideas about relationship maps.
What to learn more?
Come join me at the Enterprise Architecture Conference March 27, 2007 in New Orleans. I am presenting more detail on this topic in my "Rapid Business Modeling: Getting To What Matters" presentation Tuesday afternoon. I'll also be facilitating an interactive session on Thursday entitled, "Giving Good Whiteboard" where I will talk about a lot of the topics we cover in this blog. Come and hear what your colleagues have to say!
If you haven't register yet be sure to use FUSTL77 as a discount code when you register for $200.00 off. I don't get any money for doing this, just passing an opportunity on to my readers. 