Apparently office politics is a horrible thing that other people do.
But many of the emerging IT leaders I speak to get told they need to be better at “soft skills” and “influencing at a senior level”. What this often means is get good a politics.
Sadly a lot of office politics seems to involve people playing games to get their own way at the expense of everyone else. This skill can be learned and might seem useful, but it is not what I am going to talk about here. I am going to talk about “how do the good guys get the right outcomes when people have competing interests or needs and some people seem like knob-heads”.
Continue reading “The dark art of office politics for IT leaders (part one – why is it stressful?)”
I am starting a bunch of small projects at the moment and people are rushing to help define the solutions. That is great but I am (as always) nervous that we are providing solutions before we really understand what we want to solve.
I like to define the problem (or vision) and then a rough plan to get there and with this in mind I have already published an article suggesting teams use a project charter and possibly a product statement, but where do these come from?
I usually start right at the beginning, by asking people what they want and then asking what they mean by that – I call that approach a “question compass” because it is useful for finding your direction right at the start of things.
But even with all those links, how do you go from “hi, there my name is James – what would you like today?” through to “Cool, here is an initial project charter – it will allow us to address the enclosed focusing question … that will be $3.2M if you choose to continue, have a nice day”.
Continue reading “Focusing questions and project charters are great, but where do you start?”