Operations use cases at Loom

Hi, I'm Ashley I'm illegal. And here are a few ways on how I like to use loom in legal. The first is to provide context for a question.

So I'm often asking people for it information In order to provide legal guidance, or I might need to run something by someone.

And it Needs a way for me to do that is to record a loom, Give them the quick one minute background on what it is and why I'm asking and ask my question.

That way. An example of that is if I am Reviewing a contract and there is a provision that I need to run by someone, or see if we can accept the risk on a red line, I can just pull up the contract, show them the language, provide any context and ask them that question.

The second way I like to use loom is show not tell. So this comes up a lot with our product, the team, when they are rolling out a new feature or making a change in the product, and they have a legal question or an issue that they want to get my take on, they can just record a loom and show me what it is they're doing.

So for example, if they had a question on our export insights feature, they could just pull it up and show me what it is they want to change.

I also then can reply with the loan and then explain what the legal risk is. Show them the different options, because it's often not a yes or no answer, and I can give them some legal guardrails that might help them reduce risk in their product decisions and product design.

The last way I like to use Lim is not unique to legal, but we have a legal Wiki that has a bunch of them process dogs or guidance or checklists on it for people to come and use.

If they're looking for resources on legal issues or legal guidance. And so I find it really helpful to record a loom and have it be linked to the doc.

And it's basically like a TLDR of what the dock is, how you can use it and maybe explains any high level or no, he wants to concepts that just don't come Through in a doc.

So that's it. But that helps.