OJK — Public Website Redesign.

A self-initiated concept. This redesign is not affiliated with, commissioned by, or endorsed by Otoritas Jasa Keuangan. It is an independent design exercise exploring public-sector UX, using only publicly available information.

01 — Context

OJK is the body most Indonesians turn to when something goes wrong with money — a fraudulent investment, an illegal lending app, a bank dispute. But for a site that carries that weight, the public-facing experience asks a lot of the visitor: dense navigation, PDF-first content, and a homepage built around the institution rather than the person reading it.

This concept asks a narrow question: if someone arrives scared, confused, or in a hurry, can the site help them in under a minute?

“A regulator’s website is read at the worst moment of someone’s financial life. It should behave like it knows that.”

02 — Approach

We framed the audit around three real intents, each one a person rather than a page:

• “Is this investment legal?” — someone about to send money.
• “I think I’ve been scammed.” — someone who already has.
• “Is this lending app allowed to do that?” — someone mid-dispute.

Each intent should have one obvious, fast path from the homepage. In the current site, all three are buried two to four clicks deep, often ending in a PDF.

03 — Execution

The redesign keeps the institutional weight — this is still a regulator, not a startup — but reorganizes the surface around tasks.

The homepage leads with a single “Check & Report” module: a search field that answers the legality question directly, and a clearly separate, calmer path for reporting. Content that used to live in PDFs becomes plain HTML pages that load fast on a mid-range Android phone over 4G, which is how most of the audience actually arrives.

Typography does quiet work here. A clear, high-contrast type scale and generous spacing make dense regulatory language feel approachable without dumbing it down.

04 — Results

The deliverable is a clickable prototype covering the three priority flows plus a homepage, and a short IA document proposing how the deeper content tree could be reorganized.

Measured against the one-minute test, each of the three intents resolves in two clicks or fewer in the prototype — down from the current three-to-five.

As a concept, the goal isn’t to claim it’s the right answer. It’s to show what a task-first, anxiety-aware public site could feel like — and to use that as a way of thinking about every public-sector project Roha might take on.