I’ve been closely involved in many digital projects over the years. Different industries. Different budgets. Different ambitions.
Still, I often see the same pattern.
When projects become difficult, the explanation is usually technology, estimates or capacity. The technology was wrong. The budget was too low. The timeline was too optimistic.
Sometimes that is true. But often, the root cause lies somewhere else: in lack of clarity.
Lack of clarity about what is actually going to be delivered. Lack of clarity about who makes decisions. Lack of clarity about what matters most when time, budget and ambition need to be prioritized against each other. And lack of clarity about what should actually be different when the project is finished.
Projects rarely go off track in a single day
Most projects that run into trouble do so gradually.
It often starts with small misunderstandings. Everyone thinks they agree on what should be built, but the customer, designer, developer and project manager may all have slightly different pictures in their heads.
Then come the decisions that take too long. An unresolved priority, missing copy, or an integration no one fully owns can slow down the entire project.
Another classic problem is that no one clearly owns the whole. Design moves in one direction, development in another, content in a third. Everyone is working. Everyone is doing their best. But the tracks do not meet well enough.
It is rarely lack of effort that makes digital projects difficult. It is lack of shared direction.
Clarity is a project activity
At Frontkom, we spend time early in projects creating shared understanding.
We need to understand what the customer is actually trying to achieve, not just what is written in the brief. We need to know who can make decisions, which goals matter most, what risks we already see, and how we should prioritize when something changes.
That is why we establish clear roles and responsibilities, fixed meeting points, and a shared rhythm for reporting, prioritization, and adjustment. We clarify how changes will be handled, and make sure the steering group is used for decisions — not just status updates.
It may feel like a lot of structure in the beginning.
But good structure is not bureaucracy. Good structure is what allows the team to work faster, safer and with fewer surprises.
Good projects require shared ownership
A digital project cannot succeed on the supplier side alone.
The customer often holds the key to the most important clarifications: goals, priorities, content, domain knowledge, user insight and internal decisions. That is why we need active product owners, available decision-makers and clear points of contact.
This does not mean the customer should micromanage the team. It means the customer needs to be close enough to provide direction, prioritize, and clarify when the project needs it.
The best projects I have seen have had one thing in common: both parties owned the result together.
We don’t only measure whether something was delivered
A digital solution is not successful simply because it was launched.
It has to work for the users. It has to support the organization’s goals. It has to be possible to operate, improve, and develop further. And it has to create value after the project has ended.
Of course, time, budget and quality matter. Projects need to be managed. The financials need to be under control. Expectations need to be aligned.
But we should not confuse the project delivery with the effect of the project.
What we are really trying to deliver is not just functionality. It is better work processes, better user experiences, and better conditions for future development.
The right pace starts with the right direction
Many people want to start building as quickly as possible. I understand that. Building is concrete, visible, and creates momentum.
But the earlier we clarify goals, responsibilities, priorities and risks, the better the project becomes.
Not because the plan will never change. Digital projects almost always change along the way. But when the direction is clear, it becomes much easier to handle those changes well.
At Frontkom, we believe good digital projects are about more than building the right solution. They are about creating enough shared understanding for the right decisions to be made along the way.
That is how we deliver projects that actually work in practice.
Do you have an upcoming project where you want a partner who asks the important questions before you start building? I’d be happy to talk.