Oracle, via POAP Studio · 2025–2026

FY26 Readiness

A badge collection experience designed inside Oracle’s own platform and design system.

Enterprise
Design system
Embedded

The FY26 Readiness page inside Oracle’s internal hub: Your Path to FY26 Readiness, five core steps, and the I’m Ready for FY26 milestone badge

Role: UX/UI Designer
Timeline: 2025–2026
Status: Embedded in Oracle’s internal platform
Scope: Information architecture · Reusable badge component · State model · Edge-case handling

Context

Designing inside a product I did not own

Oracle did not use Passport. POAP Studio designed a badge-collection experience directly inside Oracle’s internal platform, using Oracle’s own design system: a bespoke embedded enterprise experience, not a white-label implementation.

That constraint is the whole interest of the case. Every decision had to survive an existing component library, an existing page template, an existing navigation, and a host team with their own priorities.

Information architecture

Core Stepsfive, sequential
Extra Challengesoptional, bonus
Rewardsunlocked by steps
Final badgeI’m Ready for FY26

One reusable badge-listing component renders all three tabs. Each step states how many rewards it helps unlock, so the dependency is visible from the list, not only from the reward.

The decision

Where the component sits changes what it means

Decision

Place the milestone above the steps, not below them

The tension

The gamified block had to be inserted into a page that already had an owner, a hero and a purpose. Put it at the bottom and it reads as an appendix nobody scrolls to. Put it at the top and it competes with the host page’s own message.

What I chose

I prototyped both placements at full page scale rather than arguing about them, and put the milestone card directly under the section navigation: high enough to be seen on load, low enough that it never fights the host hero. The core-step cards then flow underneath in their natural reading order.

Three page variants with the gamified component placed at the bottom of the page — The same page, both ways, at full scale. The only way to have this conversation with a host product team.

Three page variants with the gamified component placed at the top of the page — The same page, both ways, at full scale. The only way to have this conversation with a host product team.

States

The unglamorous half of enterprise UX

Most of this project was edge cases.

A badge system inside a corporate platform spends most of its life in states nobody demos: a step completed but not yet verified, a modal dismissed mid-flow, a CTA that is disabled for a reason the user cannot see, a milestone that must not fire its celebration twice.

The FY26 Readiness page with its five core steps — Each step states how many rewards it helps unlock, so the dependency is visible from the list itself and not only from the reward at the end.

The FY26 badge in its unlocked state — Each step states how many rewards it helps unlock, so the dependency is visible from the list itself and not only from the reward at the end.

Documented edge cases: what happens if the user clicks outside a modal while completing a step, and tooltips on disabled call-to-action buttons — Two of the documented edge cases: dismissing a modal mid-step, and explaining why a disabled CTA is disabled instead of leaving it inert.

The complete flow map: core step completion, step detail pages, extra challenges, their detail pages, and rewards — The full documentation board: core steps, step detail pages, extra challenges and rewards, with the modal and tooltip cases threaded through. Scroll sideways.

End of case

If your product has more rules than screens, we should talk.

flor.cdp@gmail.com Read about Florencia

Next case · 06 · Independent side projectBadger TownExplore the city, solve clues, collect wearables, and change the character you own.