
SGN AI Workshop - what the survey told us
Episode 0 of the SGN AI Workshop briefings
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Episode 0 of the SGN AI Workshop briefings
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
What the survey told us This episode covers the results of the pre-event survey Catherine sent to everyone registered for the Ashling workshops. Catherine Tobin runs events for the Solicitors Growth Network, and she's hosting both days. It explains what people said, what that tells you about each room, and what to change before Monday. No names or firms are mentioned. None of that is needed to act on the results. How much weight to give it Thirteen people answered, out of forty-seven registered. Six are coming on Day One only, six on Day Two only, and one is coming to both. So each day has seven answers behind it.
That's enough to show you the shape of each room, and not enough to treat as a full picture. The people who didn't answer may well be the least engaged, which would make both rooms a little more beginner-heavy than the survey suggests. The survey was also shorter than the one you designed. It asked which day people are attending, which case management system their firm uses, which AI tool they use most, what kind of account it is, where they are with the tools, whether they want a free trial of NewCode, a legal AI company whose team is helping on the day, dietary needs, and anything else they'd like considered. It didn't ask about practice areas, whether firm IT blocks these websites, or what work people plan to bring. So you don't know which areas of law are in the room.
Keep your examples general enough to suit any practice. And have the floor team ready for blocked websites in the first ten minutes, because nobody has warned you in advance. Day One: a beginner room, as planned Of the seven Day One answers, four people said they have not really started. One tried a few times and nothing stuck. Two use it weekly for a few things. So the room you designed for is the room you're getting. The more useful finding is about accounts. Four of the seven are on free accounts.
One has a paid personal account, one has a paid firm account, and one isn't sure what kind of account they have. That tells you the first working session of the day, block one, where everyone checks their account settings and turns training off, isn't a formality for this group. For most of them it'll be the first time anyone has explained what happens to what they type in. The person with a paid firm account also said they haven't really started. Their firm has paid for the tool and nobody has shown them what to do with it. That's a common pattern in small firms, and it's the gap your opening talks about.
On tools, three use Claude, two use ChatGPT and two use Microsoft Copilot. Both Copilot users are either on a free account or unsure. That matters because Copilot only gives work-level data protection when you're signed in with your work account. Signed in with a personal account, it behaves like any other free tool. So in block one, show people how to tell which one they're in, alongside the settings screens for the other tools. Day Two: firm accounts, Copilot, and different case management systems
Day Two is also as planned. Three people use AI most days, three use it weekly, and one is building things with it. Six of the seven are on paid firm accounts. That means Tuesday's session with Eileen Ireland, the data protection specialist, can skip the basics and go straight to the harder questions. There are three. Sub-processors, which are the other companies a provider passes your data to. Subject access requests, where a client asks for a copy of everything the firm holds on them. And data protection impact assessments, the risk review a firm does before using a new tool with personal data. The most common tool on Day Two is Microsoft Copilot, with three people.
Two use Claude, one uses ChatGPT and one uses NewCode. So before Tuesday, check that the context-file and prompt exercises in blocks one and two can be done in Copilot, not only in Claude. VizLegal, a legal tech company helping on the floor that morning, is strongest on Claude, so the Copilot users may need help from you or the NewCode team. The biggest surprise is case management. Case management systems are the software a law firm runs its files in. Your Tuesday session on the case management problem leans on one of them, Keyhouse.
It does that through John's working examples, and through Flor's story about his firm moving systems. John is a solicitor at Flor's firm, and Flor is one of the network's two co-founders. But nobody answering for Day Two uses Keyhouse. Three use Thread, two use LEAP, one uses Evolve, and one has no case management system. The two Keyhouse users are both coming on Monday. So for Tuesday, find out before the day what Thread and LEAP let you export, and whether either has its own AI features.
Then your advice fits the systems actually in the room. Flor's story still works, but tell it as a lesson about any system, not a Keyhouse point. For the pairs exercise, group the Thread users together, the LEAP users together, and put the others in a mixed pair. What people asked for Five people wrote something in the comments box, and three of those wrote "no". The two real comments asked the same thing: how to use AI with the case management system their firm already has. One of those two people is coming on Day One, and Day One doesn't currently cover case management at all.
So give it three to five minutes on Monday, at the end of block two, where you talk about choosing between tools. The short version is that most case management systems don't connect to outside AI yet. For now the practical approach is to take the documents a job needs into a working folder, use the AI there, and file the result back. Tuesday covers it properly. The NewCode trial Nine of the thirteen said yes to the free NewCode trial, and one Day Two attendee already pays for NewCode. So many people will arrive with a NewCode account open, and NewCode's talk after Eileen will land with a room that's already interested. That's another reason to open block one with the common ground about client data, rather than anything that sounds like disagreement.
It also means some Day One people will be doing the settings exercise inside NewCode. Ask Rory and Emma, the NewCode team, to help with block one, not only blocks three and four in the afternoon. What to change before Monday Here is the list in one place. On Monday, in block one, add the Copilot work-account check next to the other settings screens, and ask Rory and Emma to help people using NewCode. In block two, give case management three to five minutes and point people to Tuesday.
On Tuesday, rebuild the case management example around Thread and LEAP, and check what each allows before the day. Make sure the morning exercises work in Copilot. Ask Eileen the Copilot question on Tuesday as well as Monday, because that's where most of the Copilot users are. And there's one person on a free account coming on both days. They'll get the account session on Monday, but have a word with them on Tuesday morning before the context-file exercise. Treat all of this as a strong hint rather than a certainty.
Thirteen answers is a small sample. When you see each room on the morning, trust the room.
Nobody is credited on this episode yet.
Episode 1 of 9 in the set "Solace Worldbuilding"
Episode 2 of 9 in the set "Solace Worldbuilding"
Episode 3 of 9 in the set "Solace Worldbuilding"
Episode 4 of 9 in the set "Solace Worldbuilding"
Episode 5 of 9 in the set "Solace Worldbuilding"