Una Marie S. Goksøyr · Data, quality and systems · Norway

I build the systems behind decisions people can trust.

Most organisations have the data. What they lack is a system around it: clear ownership, checks that catch errors early, and answers shaped for the people who need them. That is the work I want to do more of.

See a working example How I work
Work20 years, from the workshop floor to quality management, in maritime, construction and public sector
Study10 years: engineering, safety, society, maths, programming and systems engineering
NowQA and data analytics, connecting systems that were never designed to talk to each other
ToolsMicrosoft Fabric, PySpark, SQL, Power BI, Next.js, Supabase
Why this site

More ideas than outlets

Twenty years of work and ten years of study add up to more ideas than any one job has room for. This is where I build them, test them and share them. Building is how I think, and I want to meet more people who care about the same problems.

The companies here are fictional and the data is generated. The ideas and the work are mine.

Approach

Start with the problem, not the tool

A systems engineering way of working, scaled to the size of the problem.

  1. 1

    Understand the problem and the users

    Who makes the decision, how often, and what goes wrong today? A seller needs a call list, an auditor needs evidence, a manager needs a trend.

  2. 2

    Design the system

    Map the data flow, agree on definitions, decide who owns each part, and place the controls where errors start.

  3. 3

    Build what fits

    A report, a daily list, an alert or a small app. Best practice, but only as much as the problem needs.

  4. 4

    Verify and improve

    Quality gates before data is written, tests before release, and feedback from the people who use it.

Projects

Selected work

Portfolio project · Microsoft Fabric

Solvi: from rooftop to kilowatt-hour

In progress

Solvi is a fictional Nordic solar and battery installer. All data is generated.

One data system for a company where sales, installation, service and quality all depend on the same facts, but each needs a different answer. Installations, production, weather, compliance records, proposals and contracts are joined once, checked once, and then delivered in the form each group can act on.

WhoQuestionWhat they get
Service teamIs it broken, or just cloudy?Installations below what their own weather allowed
Quality and complianceAre we audit-ready?Missing paperwork, open deviations, worst first
Project planningWhat changes after the customer signs?Components dropped or downsized after the site survey
SellersWho is waiting to hear from us?A short list of open proposals nobody has followed up
Customer serviceWhat has this customer bought, ever?One search across the old and the new ERP

Try the working example. Five views, one per user group, built on the same checked data.

Open demo
System choices
  • One definition per number, shared by every view
  • Quality gate: nothing is written if a check fails
  • Weather and snow in the model, so faults are not confused with cloudy weeks
  • Compliance stored as data: requirement, due date, evidence, deviation
  • Old ERP history kept in a frozen, searchable archive, mapped to new numbers
  • Everything in Git, with separate test and production
Ontology, a first sketch 
Site         experiences Weather
Installation produces    Energy
Installation needs       ServiceVisit
Installation requires    Document
Customer     signs       Contract
Contract     delivers    Installation
Microsoft FabricPySparkSQLPower BIGitOntology
Client project · Web app

Freya Hundepensjonat: booking and daily operations

Live

A booking and operations system for a dog boarding kennel in Hareid. A hectic workplace with people and their pets needed a website and an app, with a separate interface for each group that uses it. The goal was fewer interruptions on the phone and more time for the dogs.

WhoWhat they needWhat they get
Dog ownersBook without callingRegister their dog, upload vaccination records, book stays and send messages
The ownerControl without chasingReview and approve bookings, see at a glance what is waiting
StaffKnow the day, hands fullA simple view of who arrives, who goes home and what each dog needs
Details that mattered
  • Customers always see what the next step is
  • The owner sees at a glance what is waiting for approval
  • Regular daycare customers can book a day in a few clicks
  • Planning considers each dog's needs and who gets along
Built with
Next.jsVercelSupabaseResendGitHubAutomated tests

freyahundepensjonat.no

Take a break

Quality Gate

A small game in the spirit of the 90s games I grew up with. Catch the good records, let the nulls, duplicates and old boots sink. Every bad record costs trust.

Play Quality Gate
Principles

Best practice, sized to the problem

The right-sized answer

Not every problem needs a platform. Sometimes a checklist or one well-placed alert does more than a dashboard.

Controls where errors start

Checking at the source is cheaper than explaining a wrong number later. Validation runs before data is stored.

Clear ownership and definitions

Every number has one definition and an owner. That is what lets people trust it, and what makes data ready for AI.

Built with the people who use it

Test early with real users. The small details, like always knowing the next step, decide whether a system is used.