Behind that first request, there’s a lot to read between the lines: a company that’s growing and needs to explain itself better. A team that needs a clearer tool. A funding round that’s starting to appear on the horizon. A C-level team that needs to validate a decision. A business that can’t afford to stop while changing its technology stack. A brand that no longer represents the real size of the organization behind it.
And that’s where the project truly begins. When we understand what that project needs to move.
Of course we care that a brand is well built. That a website loads properly. That an interaction creates enough intrigue for someone to keep exploring. That the visual system is solid. That the content is well told. That the development is well executed. That the craft is there, even in those details that maybe no one will point out, but that make everything work better.
The quality of all that is part of what we do. Something like an internal standard. A way of respecting our work and the people who trust us.
This also connects with something we’ve been talking about quite a bit at /nk: how we use, and how we don’t use, AI. Technology can accelerate many parts of the process: exploring, organizing, producing, optimizing. But there’s something that remains deeply human: understanding the real problem, reading the context, building trust, and deciding what kind of impact makes sense to pursue.
Because going faster is great. But only if we know where we’re going.
And we also understand that quality, on its own, is not enough.
That’s why the key is to become obsessed with understanding impact. And when we talk about impact, we’re not only talking about flashy results, isolated metrics, or awards. We’re talking about something much deeper: understanding what that organization needs to achieve, at that specific moment, for that specific audience.
Sometimes impact is sales.
Sometimes it’s clarity.
Sometimes it’s business.
Sometimes it’s performance.
Sometimes it’s speed.
Sometimes it’s order.
Sometimes it’s someone understanding in a few minutes what used to take half an hour to explain.
And many times, not to say almost always, it’s a much more complex mix of all of that together, plus a few other things.
In the vast majority of our projects, we start with a discovery program, designed precisely to surface data, information, and conversations that would otherwise be very difficult to access.
It also helps bring together all the teams involved, who may rarely sit down to think together outside of their daily tasks.
It’s a series of dynamics and exercises designed specifically for each challenge. Not because the brief doesn’t matter, but because there are things that are very hard to fully formulate at the beginning.
And there’s never a time when, by the end, someone doesn’t say something along the lines of: “wow, it’s been so long since I actually stopped to think about these things.”
You have to talk. Listen. Understand the context, the moment, the tensions, the voices, the visible objectives, and also everything that starts to appear between the lines as trust is being built.