New builds
We agree what someone should be able to do from start to finish in the first release. That gives us a way to decide which screens, records and connections to build first.
01 / About Hygge
Software in everyday use
We start by looking at what people need to do. That might mean finding information on a website, handing a job over to another team or recording work on a device with a poor connection.
We also look at what happens after release. We think through who will update content, how a team will spot a failed transfer between systems and what a future change might need to account for.
In the journal, we share the reasoning behind those decisions, what we found while testing and what we learnt once the work was in use.
02 / Development practice
How we work
A first release and a change to an established system call for different decisions. We look at what needs to work from day one and what people already rely on.
Existing systems
We review the code, the information it holds and how people use it today. Before release, we test changes against the records and workflows people need to keep using.
Our own products
We use our own projects to explore problems we want to solve. We build enough to try an idea in practice, then use what we learn to decide what to develop next.
Development tools
We choose tools around what the project needs and how it will be maintained.
03 / Further reading
Explore by topic
Our guides explain how we approach web, software and application development, with related entries from the journal.