I think you’re spot on, Jed. Your last sentence really captures what it’s all about. Well said.

This idea of cultural acceptance of even asking the question is too common. I agree in the importance of asking and setting the precedent of accountability, laying the groundwork for a team to really jump to action is aligning around the common goal. Why are we here at all (“Needs” as mentioned), is this the right team, do we all know what we intend to accomplish together? Ideally this is previously managed, but all too often takes a backseat to us protecting our “(dys)functional” areas. Are you a part of this project/product/process dev. team – or – are you a part of a “sourcing/operations/engineering/etc. team that happens to also be responsible for project deliverables. Create a team, align to the goal, people will be quick to be the who, what, when, where – in my experience.

No worries about being slow, my friend. I appreciate your insight whenever it comes. I’ve also been in the situation you describe where I haven’t felt like it was appropriate for me to ask the question. I’ve found that once the idea of asking questions similar to this “catches on” and becomes more common, it’s easier to speak up. Has that been your experience?

Thanks, Steve. Simple concept but hard to apply consistently. I agree with you about empowering individuals through this question. Great point.

Totally agree, Liz. I appreciate your input. I’m working on a follow post that will get into why I tend to not ask the question myself. I’m guilty of letting discussions end and being a part of the “silent acceptance” you mentioned. Room for improvement!

Thanks for the post Greg.

Thanks, Jenny. You are an expert at getting things done already. If you get even better, watch out!