How warm are your stakeholders about Information Radiators?
From the Easy in theory, difficult in practice Blog
by Kiron Bondale
My musings on project management, project portfolio management and change management.
I'm a firm believer that a pragmatic approach to organizational change that addresses process & technology, but primarily, people will maximize chances for success.
This blog contains articles which I've previously written and published as well as new content.
Recent Posts
Leading Through Crisis Means Leading Through Context
"It's the end. But the moment has been prepared for." - retirement lessons from the Doctor
Just because they are non-critical, doesn't mean they are not risky!
Just because they are non-critical, doesn't mean they are not risky!
How will YOU avoid these AI-related cognitive biases?
Categories
Agile,
Artificial Intelligence,
Career Development,
Change Management,
Communications Management,
Decision Making,
Governance,
Hiring,
Kanban,
Lessons Learned,
Personal Development,
PMO,
Portfolio Management,
Project Management,
Resource Management,
Risk Management,
Risk Management,
Schedule Management,
Scheduling,
Tools
Date
Information radiators can help stakeholders remain informed and can reduce effort spent by a team in handling requests for updates but to reap these benefits we must ensure that the information published meets their needs.
As with any type of communication, if the content published cannot be trusted due to obvious inaccuracies or a lack of currency, stakeholders will cease to consult the radiators and will demand that traditional reporting methods are re-established.
Such defects will also reduce the credibility of the team in the eyes of the stakeholders.
This is one more reason to ensure that if Kanban boards or other work visualization views are made accessible to stakeholders outside a delivery team that team members are diligent in updating them while work is being done rather than after the fact.
If an information radiator generates more questions than it answers, it will become a burden for the delivery team. Not only does this mean that legends, titles, and thresholds are clearly presented, but it also requires that any information which could be misinterpreted should be accompanied with some context so that stakeholders get the correct story.
For example, if a sprint burn down chart is being published daily and by the midpoint of the sprint it appears that very little has been completed, a stakeholder might reasonably assume that the team is going to complete significantly less than what had been agreed to during sprint planning. However, if some context is provided that the team's delivery process includes an independent review by an external inspector who is only available one or two days per sprint, this apparent lack of progress might be perfectly acceptable.
This also means that we should review what is being published to ensure that stakeholders can perceive the forest as well as the trees.
Publishing a sprint burn down chart or Kanban board without providing a team's Definition of Done is only part of the story. Posting a release burn up chart without indicating what is being delivered in the release will not promote shared understanding.
Finally, it's important to educate stakeholders so they can effectively pull information from the information radiators and to set expectations that radiators are to be consulted as the first source for updates.
Poor information radiators are a constant reminder of George Bernard Shaw's caution that "The single biggest problem in communication is the illusion that it has taken place."
Posted on: June 24, 2018 07:00 AM |
Permalink
Comments (13)
Please login or join to subscribe to this item
Drew Craig
Sr. Agile & Product Coach| Vanguard
Philadelphia, Pa, United States
Nice, Kiron. I just went through an exercise with leadership to determine what it was they want to see. We started with our base dashboard and highlighted some key are areas to include. An underlying important factor is ensuring that project data is collected and maintained, then, it is simply a matter of how to present and visualize what is readily available.
Drew Craig
Sr. Agile & Product Coach| Vanguard
Philadelphia, Pa, United States
Oh, and that is a great quote from Mr. Shaw :)
Rami Kaibni
Community Champion
Senior Projects Manager | Field & Marten Associates
New Westminster, British Columbia, Canada
Information radiators are a great first step for stakeholders to get updates. As long as the information displayed is what they want to see, which comes back to what Andrew said. Thanks Kiron.
Thanks Sante - as with everything else in communications, we need to understand the 5W's & H before publishing the content!
Kiron
Anish Abraham
Privacy Program Manager| University of Washington
Auburn, Wa, United States
Good article on information radiators, and thanks for sharing Kiron.
Damian Perera
Monitoring & Evaluation Specialist| Chrysalis
Mellawagedara, Western Province, Sri Lanka
Misinterpretation of information can cause damage beyond imagination. As it is mentioned, that's where we will require few effective techniques to promote shared understanding of what is being done.
Great post Kiron. Where I see challenges with Information Radiators in large organizations is standardization. Presenting the same IRs to all Stakeholders for all projects or initiatives. This approach misses the key point of validating what the current stakeholders need to see by determining the answers to the 5Ws and H
RAJESH K L
Project Manager, PMP| Bharat Electronics, Bengaluru, India
Bengaluru, Karnataka, India
Please Login/Register to leave a comment.
|
"All progress is based upon a universal innate desire on the part of every organism to live beyond its income."
- Samuel Butler
|