A practitioner's work is technical work

A practitioner checking whether a judgment has been appealed does roughly the same six things every time. Find the decision. Confirm it is the current version. Check the date. Look at what cites it. Look at what it cites. Decide whether any of that changes the position. Nobody calls that a procedure, but it is one, and it fails in predictable ways when a step is skipped.

I spend my days on the other side of it. My work is deciding how sources are ingested, what gets structured, what becomes filterable, and how we know when something upstream has changed. For a long time I assumed those were two different kinds of work, mine technical and theirs professional. They are the same kind of work.

Neither of us can rely on a term that has not been defined. A practitioner cannot search for a category the source does not record, and I cannot build a filter for something we did not decide to structure before ingestion. When we take on a new source the question we settle first is not how to store it, it is what somebody will eventually want to filter on. Get that wrong and the data is present but unreachable, which for the person searching is the same as absent.

Both jobs run on verification

The step neither profession can delegate is checking. A solicitor reads a summary and then goes to the original, because the summary is a convenience and the original is the authority. We do the same on a sample before scaling an ingestion, because a pipeline that looks correct across ten documents can be wrong across ten thousand in a way nothing surfaces until somebody relies on it.

That habit matters more than it did three years ago. When the next reader of your work is a model rather than a colleague, nobody downstream stops to ask whether this really makes sense. Whatever you left wrong gets carried forward with confidence. So the checking moves earlier and gets stricter, in both professions, for the same reason.

Why we have never written a user manual

The clearest evidence that I believe any of this is a product decision we took early and have never reversed. Vizlegal has no user manual. We have never written documentation explaining how to use the application.

That is not an omission. Our users know their environment better than we do. A librarian in a large firm understands legal information sources in a way I never will, and a planning consultant knows what matters in an An Bord Pleanála file better than any document I could write about it. Our job is not to explain their work to them. It is to remove the steps between them and the thing they came for.

So the platform is built to be discovered rather than taught. Not simple, because the subject is not simple, but phased. You begin with a search, and some weeks later you are combining filters and tracking cases across courts without anyone having handed you an instruction sheet. It works the way a well designed game teaches its own mechanics, by leading you into complexity a little at a time.

What that looks like in practice

The decision shows up before anyone has run a search. Onboarding is designed from the moment a firm comes in, through configuring the platform, the calendar, and the alerts, and at every step the question we are trying to answer is how to remove a step, not how to explain it better.

The rest is left to be found. When somebody does need telling, one sentence at the point they need it usually does it. They get the moment of, right, that is how it works, and then they do not forget. No manual produces that moment. Being told once when it matters does, and working it out yourself does it better.

Whether the approach holds is not for us to decide. We have support and we have client success, and we spend real time helping teams get more out of the platform. What we barely get is support requests. Almost none arrive, and the few that do are somebody forgetting where something lives, not anybody asking how the thing works. For a platform covering the Superior Courts, tribunals, and planning decisions, used by people who arrived without an instruction sheet, that is the argument.

If your own method already looks like this, finding, verifying, and deciding what changed, the platform tends to feel familiar quickly. You can book a demo today or get in touch at vizlegal.com/contact.