BUILDDigital Products, Platforms & Apps
Build the product around the job it has to do.
The right first version is not the one with the longest feature list. It is the one that performs the core job well enough to learn from real use.
Where this usually starts
An idea is ready to stop being a slide.
Something built quickly, or a spreadsheet the business now runs on, carries real users and real fragility.
The next version is wanted. Nobody agrees what it must prove.
The product needs to be owned, not treated as a black box.
What we take on
Nordleid defines, builds and modernises digital products, whether something customers or partners use or an internal system that has to carry real work. The scope follows the job, not the list of what could be built.
- We establish what the product or system has to do, who depends on it, and what the first version has to prove.
- We define the edges of the version: what is in, what waits, and what would make it essential.
- We build it in a form the business can run, test and continue, whether it is a new product or one part of an existing one.
What changes
The next version exists to prove something. What follows can be decided from use, not from a longer list.
What needs to be known before the next version.
01What this version proves
The claim that has to become true in real hands.
02Who it is for
The users whose work the product has to carry, whether customers, partners or the people running the business internally.
03Edges and leave-outs
What is deliberately not in this version, written where it can be seen.
04Release conditions
What must be true before real use, including store and platform requirements and applicable compliance constraints.
05How it will be owned
Who carries the system after launch, what that responsibility includes, and how it transfers if the business takes it over.
How the work continues
Nothing after this version is assumed. How people use this one, and what they work around, becomes the brief for the next.
Across Nordic markets
If the product has to work in more than one Nordic market
Product configuration, language, regulation and operating conditions can change what the next version has to prove.
- Product configuration
- Language
- Regulation
- Operating conditions
Relevant work
Before the work begins
Do we need a full specification before starting?
No. Nordleid starts from the current product, the idea, or both. What this version must prove is established before production. A complete specification of everything that could be built is not required.
- Business & Product Direction
when what to build is still the open question
How Nordleid approaches this
Start with what the product has to prove.
A feature list records what a product could do. It cannot say which of those things the product has to do well for anyone to rely on it, or what this version must achieve before the next one is worth building. Those answers set the scope, and they make the edges of the version, and what is deliberately left out, decisions rather than omissions.
That version can be small: one product area, one feature that has to work properly, or one part of an existing product that needs modernising. Small does not mean provisional.
If the next version is wanted but nobody agrees what it must prove, show us where you are.