Workflow Revolution

Right.

Before we start—

does anybody actually know

what this meeting is about?

No?

Excellent.

Senior man on the calendar,

ninety minutes blocked.

No description in the invite,

but apparently this matters a lot.

We assemble with our notebooks,

professional and keen.

Someone must possess the context.

Nobody on the team.

Then he arrives completely calm,

like ambiguity's his trade:

"I've used all these tools."

And suddenly

we're saved.

Confluence?

Fine.

Three-six-five?

Fine. Jira? Fine. Whatever you've got—

"Tell me how I'll work within your system." Show me where the

documents go.

Draw me every box and connection,

teach me everything you don't know.

We came here without an agenda,

now the arrows are starting to flow.

If nobody understands the meeting— schematise it

and nobody will know.

"I'm just learning."

Good.

"I don't have anything concrete

to share today."

Even better.

First:

brainstorm.

Second:

scope.

Third:

decompose the Jira ticket

into a statement of work.

Four commits.

Review points.

Different feature,

same device.

And somewhere in this process

we administer

the sniff test.

Does it pass the sniff test?

...It smells enterprise.

Now we're talking healthcare,

where consistency goes to die.

Ask two trusts the same question,

get seventeen replies.

One starts in emergency,

one starts somewhere else,

one spreadsheet says pneumonia,

another

contradicts itself. "They can't homogenise anything in healthcare."

That's not a lyric.

That's just what he said.

Tell me how I'll work within your system,

show me where the information goes.

Every trust provides a different answer,

so naturally— we need more flows.

Boxes into boxes into boxes,

arrows multiplying on the screen.

We still don't quite know why we're here,

but Christ, the diagram looks clean.

"I'm a visual guy."

Fair enough.

"I like flowcharts."

We can do flowcharts.

"It's much faster to change some text

on a workflow than it is to rewrite a class."

... Unfortunately,

that's actually quite sensible.

Business-case engine, get the structure right.

Prompt for every section,

context tight. Crack this one,

then tender to tender.

Build the backlog, remember,

remember— "Once we

enable this, we get to work on this next cool thing."

TELL ME HOW I'LL WORK WITHIN YOUR SYSTEM,

I HAVE USED YOUR SOFTWARE BEFORE.

We walked in not knowing why we'd gathered,

now there's a roadmap on the wall.

Confluence! Jira!

Three-six-five!

Every arrow makes the strategy

alive.

So. Any other thoughts?

... Cool.

I've got another meeting