Michael Knudson —
practitioner, engineer.

The moment I knew Norrœna needed to exist was the one when I realized I was the only person in the building who knew how the work was actually done — and I was the one who had to teach it to everyone coming in next. The retiring institutional memory had walked out the door. Three other HR people had walked out behind her. The processes survived in spreadsheets and folders and one person's recollection of where things lived. I was now that person. And the work was not going to wait.

I came into HR through an unusual door. I have a Ph.D., which gave me years of training in reading carefully, writing clearly, and trusting structured thought over impulse. I trained as a full-stack software developer because I had been watching the same problem repeat itself everywhere I worked: HR teams were being asked to do increasingly technical work with tools that were not built for them, by vendors who had never sat in their chair. I earned a PHR certification once I was operating in the field, because the field rewards rigor and rigor is the part of the work I most enjoy. Now I'm pursuing formal credentials in data science and AI/ML engineering — because so much of HR's modern second life lives in data nobody quite trusts, and modeling that data well is becoming as important to the practice as understanding the policies behind it.

I serve as the sole HR specialist for a third-party administrator with roughly 350 employees, fully remote, distributed across more than thirty states. I stepped into the role from a predecessor who had been with the company twenty-seven years and was retiring. She had built the processes over time — most of which lived in her head, with shortcuts on a desktop and files in folders whose origin she could no longer trace. Practices that had served the company well in the pen-and-paper era had been transferred into the digital one without being rethought, severely underutilizing the tools the company actually paid for. Within months of her departure, the recruiting specialist and the SVP of HR both left as well. I was now the institutional memory I had so recently been trying to absorb — and I had to learn the work, do the work, and teach the work to the people coming in to help, all at once.

What surrounded that situation was the typical sprawl of mid-sized HR operations carried into the cloud era without architecture. Reports the HRIS couldn't natively produce had to be handcrafted from multiple sources — the cleaning, calculating, and formatting consuming hours more than the reports themselves were worth. Tracking lived in spreadsheets scattered across folders and drives, hoped not to be lost or corrupted or saved in the wrong location. There was little transparency between departments and stakeholders about the processes that moved their people — a black-box feeling for employees, a rework problem for everyone else. FMLA cases drifted because the employee, the manager, and HR were never quite looking at the same picture. Decisions made one year had to be re-litigated the next because nothing about them had been documented for the next person to find. Information arrived in different shapes from different people; requests dispersed unevenly; rework compounded as new context surfaced. The work that needed to happen was happening — but the system around it was holding the work back, not supporting it.

I wanted a central hub of knowledge. A source of truth that everyone in the company could utilize and be empowered by — the employee asking about their leave, the manager planning coverage, HR doing the work the institution had hired them to do. The tools to build that hub existed. They had simply never been assembled in the shape the work actually needed. So I assembled them.

§ IWhy I built Bifröst.

I built Bifröst — the platform that now sits at the center of Norrœna's practice — because I needed it. Not as a side project, not as a startup idea, but as a working solution to a working problem. The off-the-shelf tools available to a company at our scale solved roughly seventy percent of the work. The remaining thirty percent — the report nobody could pull, the integration that should have existed but didn't, the tracking that needed to be uniform across departments, the audit trail that needed to be defensible — was the gap I sat in every day. I built into it.

What I had that most engineers don't was the lived experience of being the person at the bottom of the bottleneck. I didn't have to interpret a requirements document. I was the requirement. Every design decision in Bifröst came out of a question I had asked myself, in the middle of a busy week, while the work waited.

That intersection is what Norrœna sells. Not the platform — although the platform is what makes the economics work. Not the credentials — although the credentials are what make the work defensible. What we sell is the judgment of an HR practitioner with the hands of an engineer. The judgment to know what to automate, what to leave human, and what to refuse on principle. The hands to build the thing the judgment recommends.

§ IIWhy Norrœna.

The name comes from the Old Norse term for the language of the North — the tongue that connected far-flung settlements that otherwise had no common ground. It was the bridge across distance, the medium of trade and law and counsel. I chose it because that bridging function is exactly what the firm does: between HR and engineering, between compliance and automation, between the people who do the work and the systems that should be helping them.

Bifröst — the rainbow bridge in the same mythology — is the platform. Mímir — the wise counselor whose well held the world's knowledge — is the assistant. Draupnir — Odin's ring, the artifact that dripped eight identical rings every ninth night — is the modular tier: each engagement forged once, designed so the next one comes faster. Rún is the quiet word, the whispered counsel, the audit. The names are not decoration. They are a promise that the firm thinks carefully about every piece of what it builds and what it calls things.

§ IIIHow I work.

Three working principles shape every Norrœna engagement, and they're worth stating plainly so you know what to expect:

I sell outcomes, not hours. If a build that should take three weeks of an unprepared developer's time takes me three days because the platform is reusable, the price is the same. You're not paying for the clock. You're paying for the solved problem. Hourly billing punishes speed; outcome pricing rewards it. The arithmetic works in your favor either way.

Every fixed-fee deliverable has written acceptance criteria. I learned the hard way — both as an HR practitioner watching scope creep destroy projects, and as an engineer watching the same thing happen — that "we'll figure it out as we go" is the most expensive sentence in any engagement. Every deliverable I sell has explicit done-conditions, written down before work begins. This protects both of us.

Compliance review is part of delivery, not an afterthought. Any work that touches multi-state employment law is reviewed against current rules before handoff. I will not give legal advice — that's what your attorney is for — but I will not ship a system that I haven't checked against the rules I know it has to live inside.

§ IVWhat I'm building toward.

Norrœna is, today, a solo practice. That's a deliberate choice, not a phase. The economics of a solo expertise-driven firm — with a proprietary platform that makes delivery fast — beat the economics of a growing agency for a long time, and they beat them more cleanly the more compounding the platform produces. Each engagement makes the next faster to deliver. That's operating leverage achieved without headcount, and it's the core reason I can compete profitably against venture-funded HR software vendors without trying to beat them at their own game.

Over time, the practice will grow — but slowly, by referral, on terms that protect the quality. Contractors for overflow before employees for capacity. Recurring revenue covering payroll through a slow quarter before any hire becomes defensible. The pace is set by the work, not by an ambition to scale.

What I'm building toward is a small, high-trust practice that small and mid-sized organizations turn to when their processes have outgrown manual workflows but do not justify enterprise platforms or a full engineering bench. A bridge between where they are and where they need to be. That's the whole idea. The name is the brief.