You don’t need to diagnose

You don’t need to diagnose the problem before bringing it to me.

A client booked 30 minutes with me for something that technically worked, but didn’t feel sustainable.

❌ We didn’t start with templates.

❌ We didn’t start with automations.

❌ We worked backwards from the problem.

What’s actually getting in the way?
What needs structure?
Who needs access to what?
What should stay manual?
What, if anything, is worth automating?

The goal wasn’t to fit as many recommendations as possible into 30 minutes.

It was to make sure we were solving the right problem first.

Her review afterwards mentioned something I particularly appreciated: that I took the time to understand both the business and the broader context before recommending what should happen next.

That’s probably the simplest explanation of how I work.

Sometimes the answer is a better workflow.

Sometimes it’s clearer ownership.

Sometimes it’s automation.

Sometimes the process shouldn’t exist in the first place.

Bring me the problem. We’ll figure out what actually needs to happen next.

Until the next problem, Marilit