October 2015
What makes for a great services team and results? The team members, leadership, resources, tools, the work and culture of the organization are some that come to mind quickly. But there is another element that we sometimes forget, communications.
In all the work we intend and perform we need to have communications among ourselves, up, across and down departments and the organization. So much of what we can do is enabled or hindered with communications in advance, during and after the work is done. This builds well on the ideas of listening and being heard.
Where are areas of your services team where there are gaps in or opportunities for communications to make a difference for your users, your team, your leaders? Are they daily, weekly, periodic or do they relate to communications around people, processes, projects? Try it out and let me know what you learn.
October 2014
I was looking at a software development provider’s scope and proposal. Their first paragraph talked about their brilliance. I'm not out to share my “brilliance".
I am looking to share parts of the reality in our field that I encounter in my work. For example, if we don't listen to and hear each other, we'll talk all day or all year and never resolve the real issues. Listening and hearing are distinct - we don't get to done without both occurring. Being heard is also very satisfying. The clear signal we are just talking is when in the end the true issues aren't addressed. Listening and hearing happens when we act on what people share with us; it's not about debate.
What makes for a great services team and results? The team members, leadership, resources, tools, the work and culture of the organization are some that come to mind quickly. But there is another element that we sometimes forget, communications.
In all the work we intend and perform we need to have communications among ourselves, up, across and down departments and the organization. So much of what we can do is enabled or hindered with communications in advance, during and after the work is done. This builds well on the ideas of listening and being heard.
Where are areas of your services team where there are gaps in or opportunities for communications to make a difference for your users, your team, your leaders? Are they daily, weekly, periodic or do they relate to communications around people, processes, projects? Try it out and let me know what you learn.
October 2014
I was looking at a software development provider’s scope and proposal. Their first paragraph talked about their brilliance. I'm not out to share my “brilliance".
I am looking to share parts of the reality in our field that I encounter in my work. For example, if we don't listen to and hear each other, we'll talk all day or all year and never resolve the real issues. Listening and hearing are distinct - we don't get to done without both occurring. Being heard is also very satisfying. The clear signal we are just talking is when in the end the true issues aren't addressed. Listening and hearing happens when we act on what people share with us; it's not about debate.
RSS Feed