I'm preparing for next week's product owner training, I'm thinking more about the lifeguard model of responsibility. I have a similar model for developers, testers, managers.... for most people I think. :)
When someone is drowning, whose job is it to reach out? Should the drowning victim be expected to meet you halfway? That's a crazy thought, isn't it? But when the project is in trouble, how often do we say "That's not my job" or "I'll do this much, but that's their job, not mine!"
At the end of the day, we're all lifeguards. When you see someone drowning, jump in! Imagine a lifeguard sitting on the tower, watching someone thrashing in the water, and saying "That's not my area. I only guard the water up to that fence. You'll need to wait for Joe to come back from his break."
If we want our projects, and our company, to succeed we've got to look around, see what's not working, and go after it. It may be someone else's area, but if it needs doing, then do it. Don't step on
Previous Topic
