Okay, jokes apart. I think you want to delete the data from a table which is already locked as some other query is doing some modification in that table.
If that is the case, you will not be able to delete the data from the table untill the first transaction is not complete. This is required to ensure data consistency & integrity as per the ACID property.
If you are facing excessive locking then you need to look for the queries that are involved in locking & optimize them.
Note: NOLOCK can't be used with DML operations such as INSERT, UPDATE & DELETE. Apart from that it should be avoided in SELECT statements too, as it actully enables dirty reads (you can read the data which is not-commited & even can be rolled back later by the transaction.)