The work

The questions that arrive here tend to arrive in the wrong shape. A technology problem that turns out to be an organisational one. A solution looking for a question the organisation has not finished asking. The name on the brief is rarely the name of the actual problem.

We are living in a time where there are more questions than answers, where the best practices have stopped working, where uncertainty is no longer a phase to manage but a condition to live in. That asks for a different posture, a different mind. Today, most of the time, the question carries AI in it. That is the surface. The deeper thing is older.

What I have learned, working in and around enterprise software and digital products for two decades, is that the most consequential part of any of them is rarely the part you can point at. The interface, the deliverable — these are what gets shown. The thing that decides whether any of it actually works lives elsewhere. In the cadence of a team. In what is left unsaid between two meetings. In the assumptions and structures around a tool that no one wrote down because no one had to. A tool and the organisation around it that do not move together — or that never started — fail in ways everyone could have predicted, and no one did.

This is the terrain Feltsk works in. Not the product alone, not the organisation in the abstract — but the place where neither works on its own. Where the technology and the organisation around it have to be designed as one thing, because they already are one thing, whether anyone is paying attention or not. Some of the slower, structural work I do happens alongside others in a separate collective. Feltsk is where I work when both registers need to be held at once.

This page does not list services. Not because the offer is unclear, but because the work itself happens in the interval — between what a question seems to be and what it actually is, between what an organisation says it needs and what it can hear. Pre-packaging that into modules misses the only place where the work lives. The shape of an engagement only becomes visible once the question itself has been properly seen.

What this looks like, in practice, is quieter than it sounds. It begins with conversations — and not only with the person who brought the question. The people who live with the consequences of a decision tend to understand the problem better than anyone has bothered to ask them. From those conversations comes a written reading of the situation: what is happening here, what surrounds it, what has been true so long that no one names it any more. Putting it on paper is often the moment an organisation first sees itself plainly. That alone changes things.

Then, one or two deliberate moves. Tangible artefacts — sometimes turned toward the organisation, sometimes toward the technology, almost always toward the space between. A map of themes and silences. A written composition of what a system assumes about the people meant to use it. A page that places what is said next to what is done. Things to walk around, point at, push back on. Visual enough to be felt before they are explained.

If something here recognises the shape of a question you are carrying, the invitation is to a slow conversation. Unhurried, open, with no agenda beyond seeing whether the question and the work belong together. Find me on LinkedIn — I am genuinely curious what you are sitting with.