I start from your problem, not my methodology. From there, I bring experience, best practices and work alongside you and your team until they fit your world and your reality.
I bring an honest, neutral read on where things actually stand, and how clearly that's understood by the people around you. I do the hands-on work of making the change itself happen, once a direction is set, in the room and on a steady weekly rhythm. I prepare it. You lead it. And I build the trust between people that turns a disconnected group into one team.
A neutral perspective from someone with no stake in your organization's politics or its blind spots. I talk to you and a handful of the people who actually have to change how they work, to clarify how well they understand what the end state actually looks like, why it matters, and whether the initiative has a real way to show its progress. A diagnostic conversation, a readiness review, a report you can act on immediately, before committing to anything bigger.
AI adoption that hasn't changed how the team works, an org structure the company has outgrown, technical debt eating the roadmap, a leadership bench that needs rebuilding, a new way of working that hasn't stuck, the label doesn't matter. None of these are done until they change how people actually work, day to day. What matters is whether people end up with a direction they understand, real buy-in from the ones who have to live it, and progress that doesn't stall out three months in. That's the work I do: the workshops, the interviews, the reporting, the weekly rhythm. I prepare it. You lead it.
A strong team forms when people know what each other is actually good at, and trust they can lean on it. I bring together people who start out siloed, different functions, different sites, different backgrounds, into a team that actually pulls together. Workshops, offsites, and kickoffs, run from the outside, built to get there.
A workshop, an assessment, a round of interviews, a straight conversation with your leadership team. Scheduled, delivered in a day or a few days, no ongoing commitment on either side. This is usually where things start: a diagnosis, an adapted practice, a report you can act on immediately.
Weeks or months, scoped to one objective: a reorganization, an AI adoption program, a shift in how your teams work together. You and I agree at the outset on the end state, the point where your organization can carry it forward on its own. When you're there, I step out.
A standing number of days each week, committed to you and your organization for as long as it's useful. Support builds on what came before instead of resetting with every new engagement, covering whatever's live right now: this month's fire, next month's initiative, whatever needs an outside, execution-focused hand.
Support counts tickets deflected. Sales counts hours saved. Engineering counts adoption. Every pilot is a green light, and none of it adds up to one answer.
You keep funding pilots you can't rank against each other, until someone asks for the total impact and all you have is five unrelated green lights.
Pick one shared way to measure impact across pilots, so "winning" means the same thing everywhere.
Start here →
The org chart was the easy 20%. The why, the messaging, and the feedback loops, the part that actually turns it into reality, still isn't built.
The chart goes out, everyone nods in the town hall, and six months later people are quietly back to working the old way.
Get the why pressure-tested from outside, then the rollout and measurement plan built around it.
Start here →
Three different roadmaps, three different definitions of done, three different stories about what went wrong. Product, design, and engineering are supposed to act as one team.
Every release stays slower than it should, and you're still the one who ends up refereeing whether it was product, design, or engineering that dropped the ball.
Get an outside read on exactly where the handoff breaks between product, design, and engineering, then one shared way of working built around it.
Start here →
"I start from your problem, not the playbook."
A 50-person product organization stuck in classic feature-team silos, roadmap slipping, ownership unclear. Redesigned the team topology into empowered product squads, built the "Empowered Team" blueprint the organization used to onboard every squad after, and left behind a shared leadership vocabulary still in daily use long after the program officially ended.
Multi-site, Copenhagen and Sofia. Four simultaneous organizational changes running in parallel without the department losing delivery momentum or trust in the process.
Prosci® ADKAR Certified Change Practitioner.
Facilitation from 6–12 people up to 150; stage presentations to 200–750.
MSc in software engineering plus 15 years across engineering, product, and design.
No pitch, no deck. If any of this sounds like your situation, let's talk about what you're actually dealing with.
A 15-minute call to see if this is the right fit. No agenda, no slide deck.
Request a call →Prefer to write? Send a direct message and René will reply within one business day.
Send a message →A 50-minute call to dig into your situation properly and walk through the different ways I could help.
Book now →Based in Copenhagen. Working with leaders across Denmark.
razmuzzen@renerasmussen.dk
René Rasmussen has spent fifteen years directing Product, Design, and Engineering organizations. Most recently a 75-person, multi-site team at Milestone Systems, running four change efforts at once. He's been on both sides of the table: the leader designing the change, and the person it landed on.
He's a certified Prosci® ADKAR change practitioner, and holds an MSc in software engineering. Which is why he's as credible in front of engineers as he is in the boardroom.
Based in Copenhagen. Works with leaders across Denmark.