131–140 of 258 posts
Interviewing and hiring interaction for seasonal workers. We hire tons and tons of IC's two times per year. We run into bottlenecks due to time on the phone during interviews. If there way a consistent way to screen talent it would save us a ton of time.
* Find a form or template for a document. Sometimes the "template" wasn't really a template but "we worked on a deal that was pretty similar to this one three months ago -- use that". Sometimes the template was "use this form except for this one section you should use from that form".
* Tag form / template as "version 1" in our document management system.
* Fill in all the blanks, remove brackets, etc.
* Tag this as "version 2" in our document management system.
* Create a diff / redline with all my changes.
* Send diff to partner for review.
* Incorporate changes from partner into document.
* Replace (rather than append) "version 2" in our document management system with the new doc.
* Email document to opposing counsel for review.
* If we're sharing docs with opposing counsel via Dropbox, Box, etc., upload there too. But also email them, because they might not remember to check Dropbox.
* Bug opposing counsel every 24-48 hours until they respond with an edited copy of our document.
* Let partners and clients know that you are bugging opposing counsel so they know it's totally not your fault if this deal doesn't get done by Friday.
* Save opposing counsel's edited document as "version 3" in our document management system.
* Create a diff of the document they send and ask partner to review.
* Bug partner every 24 hours until they respond with more changes.
* Save this as "version 4" in our document management system.
* Send this, along with a diff, back to opposing counsel.
* Somewhere in this process we also pass along to our actual client for review.
* Repeat until no one has any more changes. Do this for many more documents that are part of the same deal.
* Send out the first set of documents for signature. Some people don't want to actually review the things they're signing (crazy!), so we create "signature packets" where it's just like four signature pages in a row. Also, everyone has a different set of documents to sign so different people get different sets of pages + documents -- and sometimes we need to make sure that person X doesn't see some document that only person Y can see because secrets.
* Or we use an e-signature service, in which case I spend some time creating little boxes over all the document so the service knows that this is a place where a signature-like image has to go.
* Discover some error in document. Fix. Redo all of my little boxes.
* Respond to people confused about how e-signatures work. Sometimes if there are four documents, the signatory gets four e-mails and then they're confused as to whether they should just sign the last one or all four or whatever (you should sign all four). Also, sometimes people refuse to use e-signatures, so we have to explain to people that because Docusign says the deal is done doesn't mean it's actually done.
* Sometimes this is where we file stuff with the state government.
* Send out a second set of documents of signature. We don't send these out with the first set (even if the same person is signing stuff in both the first and second set) because it's very important that the second set not be signed until after the first set is signed by all the parties (or after we get some sort of confirmation back from the government if there's a filing involved). Sometimes we have very important people that hate being interrupted to sign documents, so we let them sign everything in one go but hold some of those signatures "in escrow" so we can "release the signatures" in the right order.
* Track all of the outstanding signatures and filings via a spreadsheet and try to update this in as "real time" as possible.
* Respond to partner or client asking you about deal status by pointing to spreadsheet.
* Respond to partner or client unable to open spreadsheet for whatever reason by summarizing signature status in text form.
* Bug people periodically until everything is signed.
* If any of the parties to a deal refuses to e-sign stuff, this is where I have to create a "final" signed PDF copy of the documents, wherein I replace blank signature pages in a document with some faxed or scanned signature page.
* If signatures were being held "in escrow", bug the people who are holding the signatures in escrow for confirmation that the signatures are released.
* Sometimes these people need to bug other people for confirmation. These people then ask lots of questions like "has other person X signed yet?". Point to spreadsheet.
* Sometimes money gets wired here. Wait until we confirm the money came in.
* Signatures are released! The money came in! Tell everyone the deal is done!
* Curl into fetal position.
I'd get rid of the manual process of driving to the office every day and replace it with collaboration tools to let people telecommute full time. We actually use such tools, but have a "no remote workers" policy. Occasional work from home is fine, just not full time.
I'm an IT contractor. My last contract was at a defence company, so I understand needing to be on their network and it was only 25 minutes away.
The current one is anything from 70 to 90 minutes each way and they have nothing on site, it's all in the cloud. But they insist we turn up in the office. It's utterly ridiculous. I would happily split the difference on travelling and work an extra hour per day (i'm on a day rate) but both parties lose for no reason at all.
FWIW my day is spent on Slack, Github and their cloud provider. I need to see if Gitlab are hiring for devops / sysadmins as they've got the right idea.
Security. 90 day passwords, with multiple internal sites & servers each needing unique ones? I don't understand why we don't have automated client certificates and auto-generated ssh keys.
The 90 day password thing is pretty universal in my experience, but to be fair NIST has only very recently changed their recommendation on this so you can understand business' reticence to ease off on it. As for the multiple internal sites and servers thing...well, from a security point of view I totally agree with the requirement for separate passwords but it sounds like you're in need of a proper identity managemen…
Even with the new NIST rec, I can't get him to back off on it, so sadly we'll be stuck on that for a while.
Creating Jira accounts and giving them access to the right projects. It's one of my jobs.
Our company pumps out tons of long-document PDFs that are fairly complex in terms of text, charts, tables and whatnot. We then take the docs, excel files, and charts into InDesign to create a nicely designed PDF to upload online. I need to find a way to automate this workflow. Anyone out there experience this in their organization and want to work together on something?
Many bots are admittedly experimental, but individuals are empowered to optimize or unsubscribe from a channel.
I work in pharma, and our biggest bottleneck is drafting and executing service agreements and statements of work with new vendors. A system to facilitate this workflow would be amazing (document templates, a queue for requests with weekly status updates, etc.) Of course there is manual work done by Legal that can't be easily automated, but that is just one component of the bottleneck.