There's a conversation we have with almost every new client. It usually happens towards the end of the first week, when the system is working but the team hasn't felt it yet.

"We used to do it differently," they say. "I'm not sure about this."

That's normal. What's not normal is not warning them about it.

The J curve

When a team integrates a new system, productivity dips first. Not because the system is bad — but because learning a new way of working takes effort. Always. Even when the new way is objectively better.

We call it the J curve: initial dip, inflection point, sustained improvement. The problem isn't the dip — it's not knowing it's coming.

What changes when someone tells you

If you know the first month is going to be hard, you prepare. You set a reference point. You measure the things that are going well (and there are things going well, from day one) instead of only looking at what doesn't work yet.

Our work, on many projects, starts here: not with the solution, but with preparing the team for what's coming.

It's not an excuse. It's design.

A company that warns you about what might go wrong is a company that knows where it's going. And one that would rather see you reach the inflection point than stay stuck in the dip.

If you want to know what your first month would look like, let's talk.