I touched upon this in an earlier post. But I thought it was worth repeating from a team perspective.
If you’re on my team a very quick outline of some sort of expectations management statement could read:
I expect you to speak up when something is wrong.
I expect you to speak up whenever you spot a problem.
I expect you to speak up when something doesn’t make sense to you.
I expect you to tell me when I’m wrong.
I expect you to bring your skill and passion to the table.
And what can you expect from me?
I will listen to you.
I will gather as much input as possible and facilitate a process that leads us forward.
I will kill all nonsense coming your way.
I will get out of your way and let you work your magic.
I will trust and support you.
Basically, we are all problem solvers. If the circumstances surrounding our project, or the very essence of our project deliverables, are completely free of obstacles, or in no need of solutions, I would venture a guess and say that the project in itself is probably rather meaningless, or rather: of little value. In a sense, value is created when difficulties are overcome. For this very reason, hiding problems out of sight out of mind, means compromising the whole process of delivering value.
If you are on my team, you are allowed to fail, if you just made an honest effort and hope to learn something from mistakes made. But the one thing you cannot do. The one thing that will earn you a shit storm of hellish wrath, is this line of thinking:
“It’s crap, a road to ruin, but that’s what the customer wants so hey, by any means – let’s go build it, see if I care!”
Think like that? Time to quit.