Static Document – Dynamic Environment
Once created, iMapMyTeam reports don’t change much. Oh sure, as
the developer we may tweak language a bit to clarify, make minor adjustments
based on client feedback but they remain fairly static because they are written
accurately to what the data means based on our years of experience.
However, I find that from time to time – I get surprised in a
way I don’t want to be surprised.
I’ll be engaged in discussion with a client, they begin to
share an account of something that has happened recently, and I ask “did you
use ___fill in the blank___ iMap
report to help you with that situation?”
Their response goes something like this. “I’ve looked at that
report before”. Or “I’ve worked with John Doe/Sally Doe for 10 years and read
the reports once a while back when we first went on the system.”
Yes the report is similar – the issue is that the person is in a dynamic environment
that is constantly changing.
At any particular time that dynamic environment may or may
not be in sync with that person’s motivational need. It is the same person, but
are they in the same exact environment and situation as when you last looked at
the iMap report?
Chances are slim that they are the same, most everything
everywhere is being shaken up. What was important or relevant in that report 6
months or a year ago is different today.
For the most part, iMapMyTeam reports are informing you what
to do relative to a person’s motivational need. The need is the filter of how
they perceive the world around them. It is the yardstick they use to measure if
they are being supported or not. Needs are not negotiable.
Without the needs being met, the person shifts into their
stress reactive behavior.
Sitting with your direct report or colleague and asking “right
now, which is the most important sentence in this report for you?” is always a
great question. Even if you think you
know, ask it and you will probably be surprised by their answer.



0 comments:
Post a Comment