Have you ever wondered why it’s so hard to manage people's expectations?
I used to think it was easy - ask x if they can help solve y, clearly communicate the end goal (the required output) and discuss the following:
Who
What
Where
When
How…
Now don’t get me wrong, covering the above is still somewhat useful but let’s unpack how things may still get muddled even when you tick all those boxes. Read the example of Adam below and see if you relate to this…
When Adam first joined his company, he experienced a smooth onboarding process that included clear training and comprehensive discussions about his role's expectations. He felt confident in his responsibilities and understood how his work contributed to the team's success.
However, as the pace of change within the company and all around him accelerated, Adam's role began to evolve rapidly. New projects were introduced, and expectations shifted. Adam found himself navigating these changes without the same level of guidance and feedback he had initially received. In fact, he felt like the goal posts kept changing (that’s because they were).
Adam gradually lost sight of his main responsibilities and how they aligned with the company's evolving goals. The absence of continuous communication left him feeling uncertain, isolated and struggling to keep up with the shifting demands. Eventually, Adam's performance started to suffer and he received feedback that he was prioritising the wrong projects and wasn’t keeping up with current strategies.
Was it Adam’s responsibility to speak up sooner and ask for more clarity? Or was it the leader’s responsibility to better communicate and schedule check-ins? Perhaps the responsibility was on both sides? Or was there more to this story?
Without clear direction Adam had started making assumptions about what to prioritise. We all have preferences and so did Adam. Instead of checking he just started focusing on things he preferred doing to the things that needed to be done. He liked doing things the way they had always been done and to be honest, didn't really want to embrace the change that was unfolding around him. Adam also had a fear of asking for help or direction so he chose not to speak up. To make matters worse he had a limiting belief about his ideas and didn’t think they were that great so chose not to share them. Because he didn’t speak up, the leader assumed that Adam knew what to work on and how to get it done. This is such a common set of compounding factors that we see over and over in companies, especially in ones that are growing exponentially.
I used to think it was easy - ask x if they can help solve y, clearly communicate the end goal (the required output) and discuss the following:
Who
What
Where
When
How…
Now don’t get me wrong, covering the above is still somewhat useful but let’s unpack how things may still get muddled even when you tick all those boxes. Read the example of Adam below and see if you relate to this…
When Adam first joined his company, he experienced a smooth onboarding process that included clear training and comprehensive discussions about his role's expectations. He felt confident in his responsibilities and understood how his work contributed to the team's success.
However, as the pace of change within the company and all around him accelerated, Adam's role began to evolve rapidly. New projects were introduced, and expectations shifted. Adam found himself navigating these changes without the same level of guidance and feedback he had initially received. In fact, he felt like the goal posts kept changing (that’s because they were).
Adam gradually lost sight of his main responsibilities and how they aligned with the company's evolving goals. The absence of continuous communication left him feeling uncertain, isolated and struggling to keep up with the shifting demands. Eventually, Adam's performance started to suffer and he received feedback that he was prioritising the wrong projects and wasn’t keeping up with current strategies.
Was it Adam’s responsibility to speak up sooner and ask for more clarity? Or was it the leader’s responsibility to better communicate and schedule check-ins? Perhaps the responsibility was on both sides? Or was there more to this story?
Without clear direction Adam had started making assumptions about what to prioritise. We all have preferences and so did Adam. Instead of checking he just started focusing on things he preferred doing to the things that needed to be done. He liked doing things the way they had always been done and to be honest, didn't really want to embrace the change that was unfolding around him. Adam also had a fear of asking for help or direction so he chose not to speak up. To make matters worse he had a limiting belief about his ideas and didn’t think they were that great so chose not to share them. Because he didn’t speak up, the leader assumed that Adam knew what to work on and how to get it done. This is such a common set of compounding factors that we see over and over in companies, especially in ones that are growing exponentially.