Job Maps

Example Job map: Building Site Manager
A Job Map is a diagram, created by you, that shows the interconnections between your job and the people who have an expectation of you in your job. It can be a very helpful tool for understanding and clarifying your role and priorities at work and as a tool for problem solving. It is especially helpful when used as a tool to aid recruitment, or to assist someone starting a new job.
A good job map can be used to:
 
  • Give a clear indication of key responsibilities.
  • Make it clear to others exactly what it is that you do.
  • Identify and tackle problem areas.
  • Help produce a job description and be useful when setting objectives.

When you combine your own map with the job maps of other people in your teams you may also be able to:
  • Identify common problems.
  • Highlight areas where efforts are duplicated or confused.
  • Spot important new areas of work or gaps in existing responsibilities.

 

Sharing your Job Map

Sharing the information in your job map is an important step in improving the understanding of how the various jobs in your team all rely on each other. Sharing your job map with your line manager allows both of you to focus on your world and is a great way to help analyse where problems occur and where challenges can arise. Which of the various groups do you find the most difficult to deal with? What is the problem? What could be changed to make it better? If you can start to answer these questions then you can really start to make progress towards improving performance.

When other people share their job map with you, think about what their job must be like. How can you help them to resolve their issues and challenges? How can they help you with yours? Can you develop a plan together?
 
Sharing Job Maps

Going the extra mile


Sharing your job plan with your line manager or colleague will be helpful in talking about and tackling problem areas, but if you are still faced with a problem  - what can you do?

One really powerful approach is to arrange to meet with someone from your problem group and talk through your job map with them. Try to talk about the area where the problems arise and try to see the problem from their side. Focus on the issue and not personalities. Working with them in a collaborative way may help you both to get to the crux of the issue and lead to the best solution.

Using Job Maps to understand others


If it is not possible to talk the situation through with the problem group, then all is not lost. Take a few moments to draw a job map for your problem group. Which are the groups that they have to deal with? Where might their problems be? Could it be that the problem you experience is actually created by something that someone else expects of them? Looking at the problem from this perspective may enable you to see the other side of the problem. This can be a good place to look for solutions.

 

Combining Job Maps


If all members of a team can share their job maps then you can get a very clear view of the full scope of responsibilities across the team. Spotlighting the problem areas will also give team leaders a really good view of where their staff face their major challenges. If we can look at this data from a higher level then gaps or duplications of effort can also be spotted and common problem areas can be reviewed and targeted from a strategic perspective.

 

Using your Job Map to define your job description


A job map can be a great skeleton for a job description. By working through a completed job map and placing an allocation of time against each expectation, then you can begin to draw up a job description that can be helpful both as part of the recruitment and appraisal processes.
 
 


Comments

Post a Comment

Popular posts from this blog

Off and running...

Image
My Dad gave me a calendar yesterday. It was one of those desktop ones on which every date there is a new ‘thought for the day’. I’m not really sure of the theme, Dad had used a few days of it himself so the cover was long gone. In general I suppose the quotes, most which are attributed to 'great thinkers' throughout history,would be considered as ‘life tips’. Not my dear old Dad's cup of tea at all, hence the handover. He knows me well. It's off to a good start. The entry for the 12 th April reads: “ We never do anything well until we cease to think about the manner of doing it ” and is attributed to William Hazlitt. I googled Hazlitt to assess his credentials for such a statement. A contemporary of Wordsworth and Coleridge, Hazlitt was a philosopher, journalist and essayist in early 19 th century Britain. According to The Hazlitt Society he became the first major drama critic in English, the first major art critic, and one of the most gifted literary and...
Read more

Business Continuity as a form of OD

Image
Is Business Continuity a form of OD? It's a bit early in the week to wire up  "The Cogitator" and consider the world of OD through my own particular lens, but as I am delivering a Business Continuity decision making exercise this week I wanted to stop for a moment to consider the connection between Business Continuity and Organisational development. Does BC = OD? Simulations provide a key opportunity for learning and offer an opportunity to analyse decision making in a safe environment and are an excellent tapestry for personal development, yet few relatively few organisations choose to run decision making exercises for this purpose. In the field of L&D overall simulations tend to be niche areas, and not always regarded as the first option. I find this rather thought provoking, especially when the role of simulations is so well established in some other areas of organisations. Take for instance the field of Business Continuity. Business Continui...
Read more

Critical Incident Timeline. Are you prepared?

Image
Understanding how a critical incident develops can help us to know what to expect when an incident happens for real. So far this year there have already been a number of high profile critical incidents affecting organisations. Most recently the escalation of the Algerian hostage crisis has been a major news story. Last week, the first ever helicopter crash in London sparked a critical incident that, whilst more local in impact, was headline news and impacted organisations caught up in the maelstrom of unfolding events.   Studying how the news unfolded in this stand alone tragic accident can help us to assess the realism of the timelines in our own continuity exercises and critical incident simulations. In this blog post I present a timeline for the helicopter incident and briefly discuss critical incidents from an organisational impact perspective. Building the timeline What I have done below is to build a timeline of the helicopter crash incident, as best as I have been ...
Read more