It may not be possible to enforce. My position, some days, tends to lean more towards the DevOps role. Because of past history where often the problems were related to infrastructure issues usually are raised to my team for vetting. It became natural to pass on an issue and wait for team duct tape to take a cursory glance.
My position has made a divide between me and some of the developers because I'm out of the normal management structure. It may be a natural "fear of the unknown," but the ways that I try to counterbalance this:
* Give them interesting or fun problems to solve;
* Debate and challenge their ideas openly;
* Admit that (most of the time) I have absolutely no idea what I am talking about.
I usually end most coffee conversations egging them on and telling them to test their theories. I think by creating a better team environment the fifteen minute rule may organically be followed.
My position has made a divide between me and some of the developers because I'm out of the normal management structure. It may be a natural "fear of the unknown," but the ways that I try to counterbalance this:
* Give them interesting or fun problems to solve;
* Debate and challenge their ideas openly;
* Admit that (most of the time) I have absolutely no idea what I am talking about.
I usually end most coffee conversations egging them on and telling them to test their theories. I think by creating a better team environment the fifteen minute rule may organically be followed.