SIAP Cover
Go Back

Focus On Your Harvest. We Made Protecting It Easy.

Product Overview

SIAP (Sistem Informasi Asuransi Pertanian) project was a strategic, government-mandated initiative assigned to PT. Asuransi Jasa Indonesia.

The core challenge was to overhaul the legacy system and create a simple, unified digital platform capable of streamlining and simplifying the acquisition and claims processes for a diverse range of subsidized agricultural insurance products.

Role Product Designer
Company PT. Asuransi Jasa Indonesia
Please Note: In accordance with project confidentiality policies, I am not at liberty to share the visual design artifacts for this work.
1

Discover

Output

User Research Findings Heuristic Analysis
2

Define

Output

User Journey Map Problem Statement
3

Develop

Output

App Sketches User Flow
4

Deliver

Output

High-Fidelity UI Design Handoff

Designing Within Real-World Constraints

Why 'making it easy' was actually a very complex challenge.

This revamp process began with a user gathering to dive deep into the existing legacy system. From interviews with 15+ users, my team found three main "headaches".

Adoption Constraint

Our users had varying tech literacy and were used to the legacy system. We had to evolve, not revolutionize, maintaining familiarity for adoption.

Business Constraint

This was a government-mandated project with a complex BRD. Our role was to simplify the user experience without changing non-negotiable business rules.

Process Constraint

An aggressive timeline forced parallel design & development; we delivered just-in-time and iterated rapidly.

Learning What Isn't Working for Our Users

By stepping into their shoes, we get a clearer, more human-centered view.

Interviews and research surfaced three consistent issues that guided our design decisions.

High Cognitive Load

Dense forms caused cognitive overload—users couldn't easily know what to fill or why.

Complex Flow

The flow felt like a maze; users lost context and became anxious about next steps.

Inconsistent Wording

Jargon and inconsistent terms made users hesitate—uniform language was required.

Rice field illustration

Getting to the Root of the Headaches

Turning user headaches and business requirements into a unified goal

The root cause was that the system was built inside-out—forcing internal business logic on users. We synthesized interviews into journey maps and aligned findings with the BRD to pinpoint problems.

Sketching Out a Simpler Path Forward

Collaboration & rapid exploration shaped our low-fi solutions.

We began with low-fidelity flows and sketches to map the "happy path" and validate quickly.

Corn illustration
Tobacco illustration

Low-fi concepts became interactive prototypes, then high-fidelity mockups.

The Final Result is a Design That Just Makes Sense

We translated validated prototypes into a solution that directly solved user headaches.

The proposed high-fidelity design addressed the three main issues we discovered:

A Multi-Step "Wizard"

Break long forms into guided steps to reduce cognitive load.

A Clear Progress Tracker

Always-visible progress so users know where they are.

Consistent Language

Glossary and unified wording across the platform.

We handed off consistent components and clickable prototypes to developers for accurate implementation.

Arrow pointing up