The most underrated requirement in software is still this: does it work where people actually use it?
It sounds banal. But that is often where digital products fall apart. Not in the demo. Not in the boardroom. Not when you are sitting with fibre, two screens and coffee.
But on Bornholm, between two tents, with 8 percent battery, bad signal and three people who have all found an event they want to attend.
That is why we built folkemoedet-app.dk.
Not because the world needed another app. Because Folkemødet is a fairly precise test of whether you understand the user’s reality. The programme is large. This year, the app contains 1,783 events. That is not an information problem. It is a coordination problem.
A programme is not a plan
The official programme tells you what is happening. That is necessary. But it is not the same as helping a team decide what they should actually attend.
If three colleagues go to Folkemødet together, the problem appears quickly. Who goes where? Which events overlap? Where are the notes from the conversation we had after the panel? What was the talk we bookmarked yesterday evening?
These are small questions. But small questions become expensive when they repeat all day.
So the app is not about making the programme more impressive. It is about making it more useful. Shared bookmarks. Personal notes. Offline access. A way to keep an overview without rebuilding the plan five times a day.
It is almost embarrassingly practical. That is exactly the point.
Offline is not a technical feature
You can describe offline access as a technical feature. It is one. But for the user it means something else.
It means the product does not give up on you when the context gets difficult.
That kind of requirement often disappears when software is designed from the organization’s perspective. You start with data, integration diagrams and platform choices. All of that matters. But the user starts somewhere else: I am standing here, I need to move on, and I need this to work now.
That difference is larger than it sounds.
Many companies talk about digitalization as if the task is to make existing information available on a screen. Availability is only the first layer. The next layer is action: can the user make a better decision, faster, in the situation they are actually in?
That is also why we work with AI agents and data integration the way we do. Not as technology for technology’s sake. As a way to remove friction between information and action.
The small product reveals the larger truth
The Folkemødet app is a small product. It is not a platform strategy. It is not a transformation. It is a concrete solution to a concrete friction.
But small products are good at revealing something larger: whether you start with the technology or with the situation.
If you start with the technology, the question becomes: what can we build?
If you start with the situation, the question becomes: what needs to become less annoying for people to do what they are already trying to do?
The second question is almost always better.
That is true at Folkemødet. It is true in customer service. It is true in case handling. It is true in internal processes where employees spend far too much time searching, copying, coordinating and waiting.
The problem is rarely a lack of software. It is a lack of software that respects the situation.
Use it if you are going to Folkemødet
The app is here: folkemoedet-app.dk.
It is built for planning, shared bookmarks, notes and offline access to the programme.
If you are going to Folkemødet with colleagues, it should make the day a little less chaotic.
The most valuable software is not always the most ambitious. Sometimes it is the thing that just works exactly where everything else starts getting annoying.
