Skip to content
UX

Service design from blueprint to code

We map how customers, employees and systems work together, draw the service as a service blueprint and build it ourselves, so the insight isn’t lost in a handover.

  • The people who draw it build it
  • Prototypes tested before coding
  • Everyone on the team has 10+ years’ experience

We build and run systems for

  • GlobalConnect
  • Sykehusinnkjøp
  • Home_Net
  • Telia

What a service design project covers

We look at the whole service, from what the customer meets to the processes and systems that deliver it, and build what needs building.

  • Research and mapping

    Interviews, observation and a review of routines and systems show where the service gets stuck.

  • Service blueprint

    A map of the whole service, from the customer’s actions to the processes and systems behind them.

  • From blueprint to architecture

    The phases and events in the service become domains, API contracts and events in the code.

  • Prototypes and testing

    Clickable prototypes are tested with real users and employees before we write a line of code.

  • Employee experience

    Better internal systems, admin panels and dashboards give employees time for customers instead of duplicate work.

  • Building and measuring

    The same people build the service and measure the effect against the targets set at the start.

When does service design pay off?

Service design does the most good when the problem sits between departments, processes and systems rather than in a single screen.

  1. Customers fall between departmentsSales, support and logistics each see their own part of the case.

  2. Staff move data by handSystems that don’t talk to each other cause duplicate work and errors.

  3. A new system is about to be builtThe mapping shows how the work is really done and becomes the basis for requirements and architecture.

  4. Connected public servicesServices built around life events that cut across several agencies and sets of rules.

From what customers type to what they mean

Good services start with what users are trying to get done. In this case study we build search that understands the intent behind the words.

In depth

Service design in practice

We map how your customers, employees and IT systems work together, and we remove the bottlenecks. Many people think design is about how an app looks. Service design is about how the whole service works: what the customer does, what your staff do, and which systems have to talk to each other for it all to run smoothly.

What sets us apart from most firms offering service design is that we also build what we draw. The same senior developers who sit in the workshops write the code afterwards. That's why a service blueprint from us turns into the data model, the APIs and the screens your customers use.

What is service design?

Service design looks at the whole service at once, from the user's first search to the last system involved. It starts from what users need, but pays just as much attention to the processes and people who deliver the service. In Norwegian the discipline is called tjenestedesign.

In practice, we first find out how the service works today through interviews, observation and a review of routines and systems. Then we draw the service as it should work, usually as a service blueprint. Finally, we test the new ideas with real users and employees before you spend money building them.

What customers see, and what happens behind the scenes

A common mistake in digital projects is spending most of the budget on the tip of the iceberg, the part the user sees on screen. Most of the value, and most of the failures, sit below the waterline. They're in internal processes, outdated line-of-business systems, regulations and culture.

A good-looking app is worth little if customer service can't see the same data as the customer, or if the logistics system in the back office falls over when demand peaks. A new interface rarely fixes a problem that really lives in a manual routine or in a system that doesn't share its data. Service design gets us below the surface, so time and money go where the problem actually is.

Connecting departments into one service

In both the private and public sectors, departments working in isolation are the most common reason a good user experience falls apart. Customers don't care that sales and logistics use separate databases. They care that the goods arrive.

When we map a service, we often find gaps between departments where the customer falls through. It might be an enquiry nobody picks up, a confirmation sent by hand, or an answer that depends on who happens to be at work. Each department does its job, but nobody is responsible for what happens between them. We close those gaps by designing processes and integrations that cut across the org chart, and by making it clear who's responsible at each step.

When is service design the right choice?

Service design pays off most when the problem sits between departments, processes and systems. Typical signs are that:

  • customers ask the same question several times, or have to give the same information in two places,
  • employees move data between systems by hand,
  • nobody has an overview of the whole service from start to finish,
  • you're about to build a new system and want to be sure it supports the work as it's actually done.

The last point may be the most important. Requirements based on how work is really done are far safer than requirements based on how someone thinks it's done.

Service design isn't always the right fit, though. If the problem is a single screen or one flow in an app, UX design is often enough. If you already know what to build and the problem is that it's taking too long, you probably need development more than mapping. We'll tell you if that's the case.

Service blueprint: a map of the whole service

The service blueprint is our most important tool for connecting the business side with IT. It shows the service step by step from left to right, and in layers from top to bottom:

  • Customer actions: what the customer does, such as sending an application or booking an appointment.
  • Frontstage: what the customer sees and deals with, such as a website, a receipt, a text message or a person at reception.
  • Backstage: what happens behind the scenes, such as case handling, warehouse picking or approval.
  • Support processes: the systems, APIs and databases that make it possible, such as CRM, ERP and payments.

Lines run between the layers. The most important is the line of visibility, which separates what the customer sees from what they don't. Many of the problems we find sit right there: the customer is waiting for something that happens behind the line, and nobody on the other side knows they're waiting.

Picture a garage where customers book a service online. The form works fine, but the confirmation goes out as a manual email once someone has checked capacity. In the blueprint, that email stands out as an obvious red spot. The fix is usually to connect the booking system to the workshop schedule, so the confirmation goes out automatically.

With every layer on one sheet, managers, specialists and developers can all see where the service holds together and where it doesn't. The map gives everyone a shared language, and the discussion stays on concrete steps.

Customer journey map or service blueprint?

Many people confuse service design with customer journey maps. A journey map shows what the customer experiences and feels along the way. A service blueprint shows what the organisation has to do to deliver that experience.

Both have their place, and we often start with the journey map. It's a good way to understand needs and find the points where customers get unsure or give up. The blueprint builds on it and shows who does what and which systems are involved at each step. That's what you need to actually change the service.

From blueprint to Domain-Driven Design

We connect service design directly to the technical architecture. For us, the service blueprint is the groundwork for Domain-Driven Design (DDD):

  • Bounded contexts: the phases of the service show where the logical boundaries in the software belong. Where does sales end and the warehouse begin? That also decides the boundaries between services in the system.
  • API contracts: the interactions between the blueprint's layers show exactly what data the frontend and backend need to exchange. That becomes the API specification.
  • Domain events: events in the service, such as a customer paying, become events in an event-driven architecture and keep the systems loosely coupled.

Systems that mirror how the business really works carry less technical debt and are easier to change when the business changes.

Employee experience

Many companies leave their staff to move data by hand between systems that don't talk to each other. It's tiring and causes errors, and customers won't get a good experience while employees work in tools that get in their way. That's why employee experience (EX) is a fixed part of our service design work, and employees take part in interviews and tests just as customers do.

Better internal systems, admin panels and dashboards give employees more time for customers and lead to fewer errors. Much of the manual work can also be automated once we can see where it happens.

Service design in the public sector

For public bodies, service design is often about delivering joined-up services. When someone has a child, loses their job or starts a business, several government agencies are involved.

In public administration the benefits are measured in trust, legal certainty and equal treatment as well as money saved. With methods such as gigamapping, we get an overview of the dependencies between legislation, IT systems and the agency's public mission. That lets you deal with them early instead of being surprised halfway through the project. Everything we build follows WCAG 2.2 AA, so it meets the requirements for accessibility.

The same people design and build

A common pattern is that one supplier maps the service and writes a report, and another is hired to build it. Much of the insight is lost in the handover, and the developers are left guessing what was meant.

With us, the same people map, design and build. Everyone has more than ten years of experience, and you won't get juniors on the project. The developers take part in the workshops, so they know why each step in the service looks the way it does. They can also speak up early when an idea will be expensive or hard to build. The blueprint drives the data model and the API design directly, so what gets drawn on the wall is what ends up in the code.

If you want to build it yourselves or with another supplier, you still get the blueprint, the prototypes and the technical specifications, and you own everything we make.

How we work

A service design project with us goes through four phases:

  1. Research and mapping: stakeholder interviews, user observation and a review of the processes and systems you have today. This is where we find the pain points and the opportunities.
  2. Blueprint and architecture: service blueprints made in workshops with you, tied to the technical architecture and DDD, with API contracts and data flows.
  3. Prototypes and testing: clickable prototypes that test the flow with real users and employees before we write any code, adjusted based on their feedback.
  4. Building and measuring the benefits: we build the system in short iterations, help with training and getting your staff on board, and measure the effect.

We set targets early, such as customer satisfaction, processing time or the number of enquiries to customer service. That lets us measure before and after and show what the change actually achieved.

What does service design cost?

Our hourly rate starts at NOK 1,500, and work with a clear scope gets a fixed price. The price depends mostly on three things: how large the service is, how many departments and systems are involved, and whether we go on from mapping to prototypes and development.

Many clients start by mapping a single service. You then get a service blueprint and a prioritised list of what should change, with a rough estimate of what each item will cost to build. You can use the list whoever does the work next, and after the mapping you get an estimate for the next step before we start.

Wondering where your service gets stuck? Book a chat and we’ll look at it together.

How we work

Book a call
  1. interviews and observation

    Research and mapping

    We interview stakeholders, observe users and map the processes and systems you have today.

  2. service blueprint

    Blueprint and architecture

    In workshops with you we create service blueprints and tie them to the data model, API contracts and data flow.

  3. clickable prototype

    Prototypes and testing

    We test the flow with clickable prototypes with real users and employees before we write code.

  4. measured against targets

    Building and measuring results

    We build the service in short iterations, help with training and measure the effect against the targets.

Frequently asked questions

What is service design?

Service design looks at the whole service at once: what the customer does, what employees do and which systems are involved. The goal is a service that feels joined-up to the customer and is efficient for the business to deliver.

What is the difference between service design and UX design?

UX design usually deals with a single digital interface. Service design looks at the whole customer experience across every touchpoint, digital and physical, including the processes behind it, the employees’ working day and the parts of the organisation that affect how the service is delivered.

What is a service blueprint?

A service blueprint is a map of the whole service. It shows what the user does, what the user sees, what happens behind the scenes and which systems, APIs and databases make it possible. It shows everyone in the organisation how the parts connect, and where an improvement has the greatest effect.

What is the difference between a journey map and a service blueprint?

A journey map shows what the customer experiences and feels along the way. A service blueprint builds on it and shows what the organisation and its systems must do to deliver that experience. We often make both.

How do you connect service design to technical architecture?

We use the service blueprint as groundwork for Domain-Driven Design. The phases of the service become bounded contexts, the interactions between the layers become API contracts, and the events in the service become domain events in the code. That way the systems mirror how the business works, which makes them easier to change.

Can you build the service as well?

Yes, that’s exactly what we do. The same senior developers who take part in the mapping build the service afterwards. If you’d rather build it yourselves or with another supplier, you get the blueprint, the prototypes and the specifications, and you own everything we make.

Does service design suit the public sector?

Yes. Service design helps public bodies deliver connected services across agencies. There, the benefit is measured in trust, legal certainty and equal treatment as well as money saved.

What does service design cost?

Our hourly rate starts at NOK 1,500. Mapping and other work with a clear scope get a fixed price, and you get an estimate before we start. Many clients begin by mapping a single service.

More specialist areas

Want to see how the whole service works?

Tell us what you’re working on: mapping an existing service, getting departments to work better together or designing a new service from scratch.