Johannesburg
That's the most common brief I get. Things are slow, or breaking, or just costly in ways nobody can pinpoint. I come in, look at what's actually happening, and build a clear picture before anything gets fixed.
I spend time with the people doing the work. I look at the data, the tools, the handoff points, the decisions that get made by one person and should be made by a system. Then I build a picture of where the real friction is, and propose what to fix first.
Sometimes the answer is a new system. Sometimes it's killing three old ones. Sometimes it's just writing down a process that exists in one person's head and training the team on it. I don't show up with a preferred solution.
A clear view of where data, decisions, and work are getting stuck. Specific, not generic.
A plan ordered by what will actually move the needle, not what's technically interesting.
If I build it, your team will know how to run it without me. That's not optional.
Start by describing it. We'll figure out together if it's worth digging into.