3. Extracting a “Yes” out of a “No!”

(This is the third part of the series on Getting stuff done. Click here to read from the beginning)

In the previous post, we discussed an example of handling a “No” by finding out a manual workaround where the integration was not critical, at least in the short term. Many times this is not an option, and it is a make-or-break situation where we need a change made to an external system (one which we have no control over) to meet our program objectives. However, that other team is not able /willing to support us. We hit a wall. Now what?

Depending upon the organizational dynamics, escalating up the chain may or may not yield results. (If it did, then that is the obviously easy way out, but many times it leads to those teams further digging in their heels and burning bridges long term- so think twice before escalation, Does your team /executives have the soft power to succeed?)

If not, what do we do now?

Start with the PM or Architect (whoever is the most reasonable /approachable / knowledgable) on that team. Take them out for lunch /drinks and try to build a relationship. Ask them how you can help them to help you. Yes, genuinely ask them how you can help. Remember, your whole program’s success depends on this, and they are overworked as well.  You might be able to get a resource or two or some budget to spare for them. For example, can you give them your developer(s) to do the work required for you under their supervision?  They might say, “sorry, that is a critical piece of code; we don’t want any new developers touching it.” Can you help buy the license for some software/ hardware that eases their work? Or get them something else that motivates them to help you? Is there a win-win route?

Ask if they can use the resource you provide to offload some of their monotonous but simpler work so they can use that bandwidth to help with the critical change required by you. If this also does not work, don’t give up yet. Think hard, there might be a way out.

When there is a will there is a way! You have not failed until you give up!!

Caveats:

Be careful while you loan your developer to the other team. Several complications might arise:

1. Your developer might break something in their system – Ensure their testing is thorough.
2. They might fall in love and poach your developer. Set expectations upfront!

Stay tuned….. Until my next post with another strategy…