FULL ARTICLES
How do you build a technical community that is competitive, attractive and profitable at the same time?
ReadClose
Three observations from four years building a consultancy from zero to Microsoft Partner of the Year in Norway.
I now work as an advisor in the public sector, after many years in the private sector. It's a contrast that forces some reflection, particularly on how technical communities that actually deliver over time are built, and how easily they erode.
The strongest technical communities I've worked with all share one thing: they're built on choices that look wrong if you measure them against the quarterly result, but that do three things at once, they make you competitive in the market, attractive to the best talent, and profitable over time. These aren't three separate goals. It's one system.
In 2019 I left an exciting role at Microsoft to build a consultancy from the ground up. The challenge I saw wasn't primarily a business opportunity, it was a competence gap. Norwegian enterprise customers needed to transform old, complex IT systems so they could run in automated cloud environments. That requires a specific kind of competence: deep understanding of legacy architecture combined with modern automation, security and governance in the cloud.
That competence couldn't be studied for. There was no programme at NTNU or anywhere else that produced ready-made people in this area. It had to be built, in practice, by solving real problems on real systems.
What I wanted to build therefore didn't exist in Norway: a technical community deep enough in Azure transformation that complex enterprise customers could trust us with their core systems. Not a consultancy shop selling hours. A competence community that actually produced the competence the market lacked.
Four years later we were named Microsoft Partner of the Year in Norway.
What I've thought about most since then isn't the award. It's what actually got us there, and why the distance in time and context makes it clearer now than it was then.
Three choices proved decisive.
One, the best should be guiding stars, not superstars
We invested heavily in recruiting the best experts we could find. But what we gave them to do was something different from what they were used to.
In most consultancies, seniors are measured on their own billing. That creates a logic where the most skilled are reserved for the customers who pay the most, while juniors learn by observing and experimenting on less critical assignments. The best become superstars, irreplaceable individuals the organisation is vulnerably dependent on.
We did the opposite. The best were meant to be guiding stars. Not irreplaceable individuals, but people who lifted everyone around them. Their job wasn't just to deliver, but to ensure that two or three others could deliver the same thing within six months. We paired juniors with seniors on real projects, set aside time for internal knowledge sharing, and measured whether the competence was actually spreading.
It wasn't just about winning customers. It was just as much about winning talent.
When the competence didn't exist in the education system, we had to build it ourselves. And the sharpest minds evaluating us as an employer weren't looking for the highest salary or the most exciting client names. They were looking for a place where they could become good, where the best had time to train them, where they got to play on a team with people who lifted them, and where development wasn't a bonus after billable hours, but part of the job.
That's a competitive advantage that's hard to copy. You can match salary quickly. You cannot match a learning environment quickly, it has to be built over years.
This is, incidentally, the same dynamic that makes it hard for the public sector to attract the hungriest technology talent. It isn't primarily salary that's the problem. It's that hungry talent goes where it gets to become the best. If a technical community signals that you're allowed to become sharp on advanced technology there, alongside people who already are, that community wins the fight for talent, almost regardless of sector.
It looked like inefficiency in the short term. We "wasted" senior hours on training that could have been billable. That was exactly what made us deliverable in the long term, because when a large enterprise customer needed ten skilled Azure architects at once, we had them. Competitors with the same headcount, but without the same learning mechanism, had two seniors and eight people still learning on the job.
That's an entirely different delivery capacity. And it doesn't come from luck.
Two, we productised consulting delivery, and spent the profit on development
We productised fixed-price delivery. In practice, Infrastructure as Code based standardised services for cloud migration and governance.
Infrastructure as Code means that the entire setup of an IT infrastructure, servers, networks, security, rules, is described in code rather than configured manually. That means the same environment can be reproduced, tested and changed with the same precision as software. It's the difference between building a house from scratch every time, and building from a blueprint that guarantees the same result every time.
In concrete terms, instead of selling "we'll send five consultants for six months", we sold "we'll deliver a production-ready Azure landing zone that meets these requirements, at this price, by this date".
That's not trivial to pull off. It requires knowing exactly what you're delivering, how long it takes, and what risks sit in each engagement. It requires knowledge that would otherwise live in the heads of individual consultants to be coded into reusable modules and processes.
This achieved two things.
First, it shifted the conversation with the customer. From "how many hours do we need" to "what outcome should we achieve". That's a fundamentally different buying process. It attracts a different kind of customer, one more interested in outcomes than in resource management. And it changes the pricing mechanism: as we got better and faster, we kept the margin instead of billing fewer hours.
Second, and this is the mechanism few people talk about, it gave the most skilled consultants demanding, interesting development work internally. Building and evolving these standardised services was intellectually demanding work. It required depth in Azure, in automation, in security, in how large organisations actually function. Those working on it had their billing targets reduced while they built the services.
What we were effectively doing was converting billable hours into an investment in the company's capability. The margin from fixed-price delivery financed the building of the next generation of fixed-price delivery. And at the same time, the sharpest minds had a reason to stay, because building is more interesting than delivering the same thing over and over.
This is where the three dimensions meet. Learning financed by the business model, not treated as a cost sitting beside it. That's what made us a learning organisation, not as a slogan on a wall, but as operational reality.
Three, we learned to say no, but only after saying yes too often
We learned to be honest about what we were actually good at. But that didn't happen from day one.
The first couple of years we became overconfident. We had growth, we had momentum, we had a team that delivered. That's a dangerous combination, because it makes you believe you can deliver in areas where you don't actually have depth. We took on engagements outside our core, because the customer asked, because it felt unwise to say no to revenue, because we thought the learning curve was manageable.
It cost time, money and frustration. We didn't deliver at the same level we did in our core. The consultants felt outside their natural territory. Customers noticed the difference, even when they couldn't always put words to it.
But it was precisely that cost that forced us back to what we were genuinely good at. We learned that winning an engagement outside your core is one of the most expensive ways to grow. And we learned that the focus that lets a technical community become genuinely deep at something comes from having said no enough times that the organisation knows what it shouldn't be.
Over time we dared to say no, even when it hurt the quarterly result. That's a completely different discipline from saying no from the start, because you've felt the cost of saying yes. It stuck as learning, not as principle.
Three dimensions, one system
What I've taken away is an observation that these three things are connected.
The competitiveness came from being able to deliver what others couldn't, because we had enough depth across the whole organisation, not just in a few people. The talent magnetism came from the best wanting to go where they get better, and we had built an environment that actually did that for them. The profitability came from a business model that financed its own development, instead of pitting learning and earnings against each other.
None of the dimensions could stand alone. Competitiveness without talent erodes. Talent without profitability doesn't finance itself. Profitability without competence building becomes short-term optimisation that eventually eats what it lives on.
For leaders in the middle of building something: the question isn't whether you have skilled people. It's whether the system around them rewards what actually creates depth over time. If the quarterly result is the only genuinely consistent measure, the organisation, regardless of the rhetoric, will optimise toward it.
For boards considering where the company should be in three years: ask what leadership is actually measuring, not what they say they prioritise. That's often the only genuinely revealing information.
For founders building something new: the most decisive choices you make in the first year are about what you build in as mechanisms, not what you write in the culture document. Mechanisms survive leadership changes. Slogans don't.
This isn't a question of culture in the soft sense. It's a question of what you actually measure, and what you're willing to sacrifice in the short term to build something that delivers over time.
The hardest part of leadership is rarely knowing what's right. It's holding onto it when the quarterly result pushes in the opposite direction.
Norway isn't losing on conditions. We're losing on execution.
ReadClose
Norway says it wants to build new industry on green power. Yet many of the largest technology investments go to our neighbouring countries.
It's not because Norway lacks the right conditions.
We have clean power, a cool climate and stable regulatory frameworks. On paper, this is one of Europe's most attractive locations for digital infrastructure.
Yet investors choose differently.
Through work on data centre development and larger technology projects, I see a clear pattern: it isn't primarily about the price of power. It's about the ability to execute.
Three issues keep recurring:
Access to power is too unpredictable. The challenge isn't energy itself, but grid connection, queues and timelines. When this can't be clarified early in a decision process, the investment moves elsewhere.
Timelines run too long. Capital seeks projects that can be realised within the investment horizon. When clarifications take years, Norway falls out, not because we're unattractive, but because other countries are faster.
The value creation is underestimated. Data centres aren't static buildings. With a 3 to 4 year lifecycle on ICT infrastructure, these are continuous investment platforms with ongoing local activity. I know a specific data centre of around 30 MW, with plans to triple capacity, that already generates over 200 local jobs once subcontractors and project activity are included. At the same time, it has customers who want to establish there but can't get access to enough power.
That's an execution problem. Not a resource problem.
Three measures would have an immediate effect:
Binding deadlines in the grid connection process, with mechanisms to release reserved capacity that goes unused.
Industry-ready power: pre-defined areas with power and regulation already cleared, so investors can move straight to a decision.
A distinction between types of data centres, prioritising projects that deliver local value creation and strategic control, rather than treating all projects the same.
Norway has a real competitive advantage. But in today's market, the winners aren't those with the best conditions. They're the ones who make it simple to invest and fast to execute.
That's where the competition is decided.
SELECTED POSTS
Well-functioning organisations rarely ask for help
ReadClose
Well-functioning organisations rarely ask for help. So when someone brings in an interim leader or CEO, you know something has stalled. The only question is what.
And here lies the first trap: what the organisation asks you to fix is rarely the real problem. It's a symptom of something more fundamental that has broken down.
Sales are falling. People are leaving. Growth has stalled. Margins are disappearing.
Having gone into several organisations as an interim leader and CEO, from SaaS start-ups and consultancies to the public sector, I've learned that this is almost always the surface. Not the core.
Treat the symptom alone and you can create a short-lived improvement. But the problem comes back, often in a new form, often shortly after you've walked out the door.
So the most important task early on isn't to act fast. It's to make an honest diagnosis. And that is far harder than it sounds.
First, the information reaching you is often distorted. Leadership tends to tell a story where the causes lie outside their control. Sometimes that's true. Often it's only part of the truth.
Further down the organisation there's usually a more honest reality, but it won't surface until you've built trust. The most honest picture usually comes from those who have been there the longest. They share it when they believe you'll use the insight to solve something, not to assign blame.
The second challenge is even harder. Even once the core problem is identified, the organisation has to be willing to acknowledge it. This is where most turnarounds succeed or fail.
It has changed my view of what interim leadership is really about. The goal isn't for me alone to understand what's wrong. The goal is for the organisation itself to dare to see it, and own it.
Because an interim leader moves on. If the recognition leaves with me, I haven't solved the problem. I've only kept the organisation afloat for a while.
Success in these roles is therefore a fairly paradoxical thing: making yourself redundant.
The most important knowledge in a change process is something no consultant can bring with them
ReadClose
The most important knowledge in a change process is something no consultant can bring with them.
The decisive insight usually already sits inside the organisation. The people inside it understand the technology, the business, and the history that shaped today's situation. They know which decisions led to where things stand, where the dependencies lie, and where the real challenges actually are.
At the same time, outside experts have often seen similar problems before. They know the methods, the pitfalls, and the opportunities new technology can create.
The best change processes I've been part of are therefore not about outsiders replacing insiders, but about combining internal knowledge with external experience. That's where the real value is created.
Even so, two concerns tend to surface when consultants come in, and they're rarely written into any mandate.
The first is the fear of being judged without the full picture being understood. The people inside know the weaknesses of the current solution better than anyone. The concern is being judged by someone who doesn't understand why those choices were made.
The second is the fear of being left holding the consequences. Consultants come and go. The people inside have to live with the solutions for years after the project ends.
Both concerns are rational. They are not resistance to change. They are experience.
This is also where many change projects are decided. The consultant who arrives with the answer before understanding the problem confirms both fears at once. People rarely share their biggest challenges with someone who seems focused on assigning blame. They share them with people who genuinely try to understand.
The consultant who succeeds uses their expertise differently. They act as mentor, sparring partner and catalyst, building on the competence that already exists.
Because lasting value isn't created when the outsider takes over. It's created when the outsider makes the people inside capable of seeing and delivering the opportunities themselves.
It's the same paradox that applies to an interim leader. The best external resource is often the one who makes themselves redundant.
If you're bringing in outside help for a change that matters, there's one question worth asking: are you looking for someone to fix the problem, or someone who makes the organisation capable of fixing it itself?
I build teams and processes that deliver, not just plan
ReadClose
I build teams and processes that deliver, not just plan.
I am now concluding my engagement with Cyberforsvaret (the Norwegian Cyber Defence Force) and look forward to new leadership assignments, either as a permanent leader in an organisation that needs a step change, or as an advisor or consultant on defined engagements.
Throughout my career I've built and developed high-competence organisations, led the restructuring of companies that weren't performing well enough, and driven complex, global sales processes at the intersection of technology and business. I add the most value as a leader who structures teams and drives processes toward decisions and delivery, not as a pure subject-matter expert producing analysis without momentum. As a technology leader I don't write the code myself, but I have a solid understanding of the technology behind it, and I believe in decisions grounded in fact, not opinion.
Is your organisation looking for a leader for a permanent position, or do you have a defined engagement where you need someone who gets things done? Feel free to reach out, or share this with someone you think might be interested.