DUOLABS
Work

Internal intranet build

We built the intranet that staff at a public institution in the insurance sector use for internal work. In an institution's internal system, if the basic actions of entering, looking up, and switching screens are unsteady, the work built on them stalls too. We implemented the intranet screens and work functions and the entry flows staff follow, and made them behave close to a desktop application inside the web browser.

Launch
2008
Client
A public institution in the insurance sector
Type
Business Systems
01 / 04

An intranet used like a desktop application inside the web browser

The intranet is the system staff use for internal work, and it opens in a web browser. We implemented its screens and work functions so they could be used inside the browser with controls close to a desktop application. Because a browser is all it needs, nothing has to be installed separately at each desk.

An intranet used like a desktop application inside the web browser
02 / 04

Work screens organized so no one gets lost as functions grow

As functions are added one by one, internal work screens make it harder to tell where to do what. We set the screen structure of the intranet staff use for internal work, and organized the screens so the flow stays easy to understand even as the work functions grow complex. The functions growing complex cannot be stopped, but keeping staff from losing the flow is the screen's job.

Work screens organized so no one gets lost as functions grow
03 / 04

An entry flow that lets staff finish the task by following the screen

We set up the entry flow in which staff record their work in the intranet. Screen structure and input order were decided together so staff could handle internal work by following the screen. When the order of the fields drifts from the order in which the work is done, staff end up scrolling up and down hunting for blanks.

An entry flow that lets staff finish the task by following the screen
04 / 04

Behavior that holds steady through entry, lookup, and screen changes

For an institution's internal system, steady entry, lookup, and screen changes matter more than anything. We handled the intranet's basic screen components and user-action processing one by one, with care. The work later became the foundation for building business-system screens for public institutions and companies.

Behavior that holds steady through entry, lookup, and screen changes

Highlights

01

An intranet that works like a desktop application in the web browser

02

Screens and entry flows that stay easy to follow as the work grows complex

03

Steady behavior in entry, lookup, and screen changes

Insights

Read the blog