Earthly Lunar
Project

Earthly Lunar

Making engineering health visible — for everyone who needs to see it.


Enterprise SaaS | Developer Tools | Web Application | Dual-Audience Design

 Enterprise

Scale

2

Distinct User Audiences

Solo

Product Designer

Earthly Lunar · Earthly.dev · RedCrackle's Client

The Brief

Earthly Lunar is an engineering guardrails platform — it turns engineering standards, compliance requirements, and process documentation into automated, deterministic enforcement across every repository in an organization.

The challenge

The platform serves two fundamentally different audiences — engineering leaders who need high-level visibility across hundreds of services, and developers who need granular, actionable feedback on their specific work. Designing one interface that serves both without overwhelming either was the core problem.

The Product

At its core, Earthly Lunar gives large engineering organizations answers to questions that are otherwise impossible to answer at scale:


  • Which of our 247 services are healthy right now?
  • Which domains need attention?
  • Is this PR compliant with our engineering standards?
  • Who owns this component?


The dashboard surfaces all of this in real time — tracking adherence scores, domain health, active initiatives, and service-level compliance across an entire organization's engineering infrastructure.

Dual-Audience Design

The most important design decision in this project was recognizing that the same data means completely different things to different people.

Manager

Engineering Leaders

They need the 30,000-foot view — overall adherence scores, domain health trends, initiative progress, and risk signals across the entire organization. They're making strategic decisions. They need clarity, not detail.

Developer

Developers

They need the ground-level view — specific feedback on their PRs, guardrail violations in their repositories, and actionable next steps. They're making tactical decisions. They need precision, not breadth.

I designed the dashboard to serve both — a high-level organization overview that leaders can scan in seconds, and drill-down views that give developers exactly the detail they need without the noise.

Key Design Decisions

01 — Authentication — every error state covered

Login, registration, forgot password, reset password — every flow has empty states, error states, and success states. The auth experience is the first thing every user sees. Getting it right matters.

authentication

02 — Adherence scores as the primary language

Rather than showing raw data, the dashboard translates complex engineering compliance into a single percentage score per domain and per initiative. Leaders can immediately see where attention is needed without needing to understand the underlying data.

adherence scores

03 — Domain Health at a glance

The domain health table uses a traffic light system — green, yellow, red — with 30-day trend indicators. A leader can scan 12 domains in under 10 seconds and immediately know which ones need their attention.

domain health

04 — Drill-down without getting lost

Every high-level view links to a detailed view. Every detailed view has clear navigation back. The information architecture ensures that users — whether leaders or developers — always know where they are and how to get back.

drill-down-view

Outcome

A dual-audience enterprise dashboard that makes engineering health visible — from the organization level down to the individual service. Designed to serve engineering leaders making strategic decisions and developers making tactical ones, in the same product.

demo-image

Contact Me

Let's build something worth using.

I'm currently open to full-time Product Designer roles and select freelance projects.


If you have something interesting, let's talk.