I have touched on this before. The revisit is because one it is hitting me personally (stakeholders I feel your angst) and two it just hits home for what I think is the core problem in a lot of change initiatives- Assumptions.
There are so many things in life that to understand, follow through with or participate in require shared understanding. With the need for speed in shared understanding comes assumptions. If we start “from the same spot” we can move forward faster. If you already know something at a certain level I can then teach you the next step. The person or entity represented by that person that delivers must gauge the assumptive area. Two problems with that- One you must be aware of the fact that you have to gauge and two you must be good at it. Watch a good change practitioner and you will see expert in action in this area. I would venture to say it is THE core competency (I say competency because it usually requires a mix of specific skills) of a change management consultant.
So I will use CSS as my example.
I will not even try to explain this. Search “web design, float, relative, absolute” or “box model CSS” or “normal document flow” if you want to play with this example yourself. Normal Document Flow (in caps because it is apparently something really important and lets use NDF and make it something official) is our assumption. It has a lot to do with where something is supposed to be, things taking the place of that thing when you tell it to be somewhere else and people (and browsers) constantly changing the display parameters with their individual preference, software and hardware. Read that last sentence again. ‘Sound like a generic sentence for most business change?
If I am on the receiving end of this, the user, your NDF means absolutely nothing to me- by definition or importance.
If you have asked me to create this and I have always been quick with a pencil and napkin (or design software in this specific case) then not only is it hard to understand your NDF it seems a ridiculously slow way to get things done.
If the “you” person has helped in the design of this CSS thing- for many good reasons like SEO, cleaner code and that compatibility thing mentioned above- NDF is pretty important. It is the basis for a lot of the reasons the web is used. You get that.
Let’s say you are the leader in this grand NDF initiative, multiple year because it is complicated. If you do not clear the assumptions about flow (linear) and use (tactical) and creation (spatial and visual) George Washington, Lincoln and yes, many Wilson bills are going to change hands needlessly (for you, maybe not them- depending on who you chose as your consultants). You must be aware, or made aware, from the beginning ,that this assumption will be important. You must find a quiet place alone or with others to figure out how to gauge and then address knowledge, perspective and interest to learn (which then translates into participate and engage).
Here is an interesting tie to our analogy- When a demo online or a training video shows examples of “ways to position things” for CSS and somehow avoids the use of NDF as a term or assumption I get close to getting it. For the CSS person it has been “dumbed down”. For me it is using my languaging and learning style. Constantly refer to NDF and where something “would normally be” and you lose me. Another post right in this paragraph about how you move forward after you tackle the assumptions…
