AI Vocabulary

Workflow or conversation: which one holds a matter?

A conversation handles one request at a time, in the order you put them. A workflow executes a sequence of steps defined in advance, always in the same order, with the same controls. The first adapts to anything and retains nothing; the second adapts to nothing and guarantees repetition.

What each does well

The conversation excels at the unforeseen. You ask a question nobody anticipated, you get an answer, you follow it up. No workflow could cover the range of questions a lawyer asks in a day.

The workflow excels at repetition. A contract review, a compliance check, a consistency control: tasks where you want exactly the same thing every time, in the same order, without quality depending on the mood of whoever framed the request.

What each does badly

The conversation guarantees nothing. Two people asking the same question in two different ways get two different results, and neither will know which asked better. On work that binds, that variability is a problem.

The workflow does not leave its path. Faced with a situation its designer had not anticipated, it applies the prescribed steps anyway, producing a result that is coherent and beside the point.

One defect of workflows deserves naming because it is rarely discussed: they age without warning. The steps were written at a given moment, for a given practice and a given state of the law; two years later they still execute perfectly, on rules nobody has revisited.

Why the question is wrongly framed

Because the two are often presented as competing philosophies, when they answer needs that do not overlap. An organisation with only conversations could standardise nothing; one with only workflows could handle only what it had anticipated.

The real question is one of level. On an isolated task, the conversation is enough. On a matter that runs for months, neither suffices alone: what has to be held is neither a sequence of steps nor a sequence of exchanges, but what the matter established between the two.

That difference of level explains a common disappointment. An organisation that automates a contract review obtains a real gain and finds, six months later, that nothing has changed on its complex matters: it had addressed the repetitive task, not continuity.

What it does not solve

Neither holds anything of a matter. A conversation ends, a workflow completes, and in both cases what was decided along the way disappears with the execution.

And a well-built workflow remains automation, not judgement. It applies rules someone wrote; when the rule is bad, it applies it perfectly at scale, which is worse than automating nothing.

Why it matters to a lawyer

Because the two words describe very different products and a demonstration almost always shows only one register. A conversational demonstration impresses and says nothing about repeatability; a workflow demonstration reassures and says nothing about what happens outside the anticipated case.

Ask for both, on the same material: what it does with an unexpected question, and what it guarantees on a task repeated 100 times.