deadlock after performing Execute SQL task

As part of my DSTX package I have an 'Execute SQL task' which performs an UPDATE statement to a table in a table in our vendors application. Before the update statement there is a line as follows:

WAITFOR DELAY '00:01:00';

My question is would the WAITFOR DELAY be better off in it's own 'Execute SQL task' rather than being in the same code as the update statement? I ask this because we seem to have started to get the occasional deadlock occuring with another update process which runs within the vendors application.