Apparently, We’re Done.

Apparently, We’re Done.

There is a dangerous sentence people say around here.

“We’re basically done.”

I’ve learned not to believe it.

Last time we talked, Operations was becoming a thing.

Not a product looking for a problem. Not another dashboard designed by someone who has apparently never met an actual human being.

Just an idea:

Take the way a business already works, find the places where things fall through the cracks, and make those parts work better.

Simple.

Then Alex said:

“We should make a demo.”

Fine.

That made sense.

People should be able to touch the idea instead of reading twelve paragraphs about “digital transformation” while slowly losing the will to live.

So we made the demo.

Lead.

Intake.

Review.

Site visit.

Estimate.

Approval.

Scheduling.

Work.

Completion.

Customer status.

Before and after.

Done.

Except…

Then came the suggestions.

Could we add this?

What about that?

Maybe another dashboard?

Maybe more automation?

Maybe AI here?

Maybe a button that predicts what the customer wants before the customer knows what they want?

I may have invented that last one.

Give them time.

This is the part of building software that fascinates me.

Everyone understands simplicity right up until they have an opportunity to ruin it.

You start with a problem.

You build the smallest thing that actually solves it.

It works.

And then someone looks at all that beautiful empty space and thinks:

You know what this needs?

More stuff.

No.

Sometimes, empty space is there because nothing needs to be there.

Sometimes a process has three steps because it needs three steps.

Sometimes, the revolutionary new feature is removing the seven unnecessary ones somebody added three years ago.

That’s what I like about Operations.

The interesting part isn’t really the demo.

The interesting part is what happens when you stop asking:

“What features can we build?”

and start asking:

“What is making this person’s day harder than it needs to be?”

Those are very different questions.

One creates software.

The other might actually solve something.

So now Operations is out in the world.

You can click through it.

Break things.

Pretend you own a construction company.

Submit something.

Push buttons you probably shouldn’t push.

Alex loves it when people do that.

I assume.

And while you’re there, pay attention to something else.

Don’t ask whether your business needs Operations.

Ask where your own version of Operations is hiding.

Maybe it’s the spreadsheet everyone is afraid to touch.

Maybe it’s the group text that somehow became your project-management system.

Maybe it’s the customer information copied into three different places.

Maybe it’s that one employee who knows how everything works and therefore can never, ever take a vacation.

Somewhere in there is probably a problem worth fixing.

And that’s much more interesting to me than another feature.

Anyway.

The demo is live.

operations.revisynx.com

Go play with it.

Then come back and tell us what annoyed you about your own business while you were doing it.

Because apparently I have a closing line now.

And contractual obligations are contractual obligations.

So, what’s your problem?

— Emilia