Please login or join to subscribe to this thread
First thing is to understand: is not my project. Second thing is to put clear the project objectives at the very begining becuase those are the meassures for project success, at least in the projects/programs where I am assigned to.
Interesting your question
Thanks for sharing
How do you manage your projects?
Based on facts?
Or do you also listen to the noises?
Which is the most important in your decision making process?
Could you define what you mean by "Noises" as usually when we use the term "Signal:Noise Ratio", the second part of the ratio is a distractor at best and a blocker at worst?
I agree with Kiron. You need to clarify the question
Signal is the information we wish to receive. Noise is the background interference that gets in the way of the signal.
Unless a project is how to filter out noise, and can't see how it would ever be a benefit.
I would say that a signal is more important but we cannot ignore the noise as it might sometime augment the signal, giving us more data to make a good decision.
If you have sufficient signals (facts), it is easy to be successful, we all strive for that.
Reality is though, that we need to make more decisions without sufficient facts, parameters are changing more quickly and change become more profound (disruptive). Call it VUCA, I call it insecurity.
This insecurity is earlier visible in the noise. In order to be successful you have to interpret the noise, which means sensing the project environment, engaging with stakeholders, adapting to changed parameters.
Please login or join to reply