Customer Footprint

Customer Footprint was developed within Oracle Store, a division supporting a broad ecosystem of direct customers, partners, and franchise-based organizations using Oracle products, subscriptions, and cloud services.

These customer relationships were often large, layered, and difficult to understand at a glance. Direct customers needed visibility into the products and services they used internally. Partners often managed Oracle services as part of resale or white-labeled offerings. Franchise-based organizations, including major global brands, depended on Oracle Cloud services and tools to support a consistent ecosystem across their franchise networks.

Despite these differences, all three groups faced a similar problem: their relationship with Oracle was spread across fragmented systems, contracts, subscriptions, renewals, and service touchpoints. Customers could not easily see the full scope of what they had purchased, what they were using, what was approaching renewal, or how individual services related to the broader account relationship.

This created a recurring operational burden. Customer-side account owners often lacked the institutional knowledge needed to manage renewals and subscription decisions confidently, especially when responsibility for the Oracle relationship changed from year to year. Each renewal cycle could become a rediscovery process, requiring repeated clarification, manual research, and back-and-forth communication with Oracle Sales Representatives.

Customer Footprint began as a simple idea: create a unified read-only view of a customer’s Oracle relationship. As research progressed, the opportunity became larger. The project evolved into a broader self-service experience that could help customers, partners, franchisees, and internal Oracle teams understand the customer relationship more clearly, reduce dependency on manual support, and make subscription decisions with greater confidence.

I co-originated Customer Footprint with the Product Manager and was involved from the earliest concept stage through research, ideation, stakeholder alignment, prototype development, and validation.

As Principal UX Designer for Oracle Store / Oracle Application Labs, I owned the full user experience direction for the project. My role included framing the problem, helping define the product opportunity, conducting research with internal Sales Representatives and stakeholders, translating findings into experience requirements, designing the interaction model, and creating proof-of-concept mockups and an interactive prototype.

The Product Manager and I worked closely throughout the project, combining product strategy and UX discovery to turn an initially vague concept into a validated customer and internal-facing solution.

The project began in Q3 2023. The first iteration was presented to internal stakeholders and sponsors in February 2024. After the scope expanded, a second iteration was presented to stakeholders and selected external early adopters in April 2024. The final proof-of-concept mockups and interactive prototype were demonstrated in August 2024, followed by extensive user testing that produced the outcome metrics used in this case study.

To ground the exploratory work in real use cases, the Product Manager and I arranged a series of interviews with internal Oracle Sales Representatives. These conversations helped us identify the most common pain points in Oracle-to-customer interactions, especially around subscription ownership, renewals, and account history.

A clear pattern emerged: nearly 90% of their external contacts had less than two years of experience in their role, and roughly half had never gone through an Oracle subscription renewal process before. As a result, more than 80% of customer interactions were spent helping external account managers rebuild context, answering basic account questions, conducting internal research, and manually bridging information gaps.

During one of these sessions, I facilitated an impromptu Design Thinking workshop to quickly explore possible solution directions. Several concepts emerged, but the strongest was a visually rich interface organized around a Gantt-style timeline. This approach stood out because it could make subscription history, renewal timing, service relationships, and account structure understandable at a glance, while remaining flexible enough to support future expansion.

We also conducted deep dives into the tools currently available to Oracle teams, documenting both their user experience and the customer data they could provide. This allowed us to create a working matrix of needed data, available data, and source systems, helping define what the product experience could realistically show and where additional integration or data modeling would be required.

Our research showed that customers were not simply looking for another reporting tool. They needed a way to recover context that was otherwise scattered across systems, contracts, renewal records, internal knowledge, and repeated conversations with Oracle representatives.

One of the strongest findings was that Oracle’s customer relationship experience was often perceived as difficult to navigate. This was not because customers lacked interest or sophistication, but because the ecosystem itself was complex. Customers, partners, and franchise organizations often managed multiple subscriptions, plans, services, renewals, limits, costs, and contractual relationships without a single place to understand how those pieces fit together.

This became especially painful during renewal cycles. The customer-side employees responsible for managing the Oracle relationship often changed from year to year, creating a recurring loss of institutional knowledge. Each new account owner had to rebuild context: what the organization had purchased, which subscriptions were active, which ones were core or supplemental, when they had started, when they renewed, how they were grouped, how they were being used, and what decisions needed to be made next.

That same burden also affected Oracle’s internal Sales Representatives. Because external account owners lacked a reliable self-service view, they turned to Sales Representatives for clarification. But the internal tools available to Sales teams did not provide a complete holistic view either, which meant Oracle employees often had to perform their own manual research before they could answer customer questions. A renewal or expansion discussion could therefore become a slow back-and-forth process where both sides were trying to reconstruct the same account history from fragmented information.

The research made the opportunity clear: customers did not only need a current snapshot of their Oracle subscriptions. They needed a full customer footprint — a structured, historical, and actionable view of their relationship with Oracle.

Customers, partners, and franchise organizations lacked a unified way to understand the full scope of their Oracle relationship. Subscription data, renewal history, utilization, costs, service limits, plan structures, and account context were fragmented across systems and often required manual explanation from Oracle Sales Representatives.

This created a recurring cycle of knowledge loss and rediscovery, especially when customer-side account owners changed roles or left the organization. Each renewal period required new research, repeated clarification, and additional support from Oracle teams, slowing decision-making and reinforcing the perception that Oracle was difficult to work with.

Customer Footprint needed to turn a fragmented subscription ecosystem into a clear, self-service experience that gave users enough context to understand what they had, how it was structured, how it was being used, and what decisions they needed to make next.

Customer Footprint was designed to give users a complete, self-service view of their Oracle relationship.

Rather than presenting subscriptions as isolated records, the experience organized them into a broader account narrative. Users could see which subscriptions were active, when they started, when they were renewed, how renewal periods were structured, and how individual subscriptions related to larger Plans. This distinction was important because customers often needed to understand not only what they had purchased, but how those purchases worked together — which services formed the core of a Plan, which were add-ons, and how the overall subscription structure supported their business.

The solution also expanded the view beyond ownership and renewal data. By surfacing utilization, limits, costs, and related indicators, Customer Footprint helped account managers move from reactive renewal management to proactive subscription planning. They could identify underused services, anticipate upcoming decisions, plan budgets earlier, and optimize their Oracle relationship with greater confidence.

As the concept matured, Customer Footprint evolved from an external-facing read-only view into a broader experience serving both customers and internal Oracle teams. External account managers gained the context they needed to make informed decisions without relying on repeated Sales Representative explanations. Internal Sales Representatives gained a clearer view of their customer’s full profile, allowing them to support conversations more effectively while operating within appropriate permission and security boundaries.

The result was a more transparent, more actionable, and less frustrating customer experience. Customer Footprint reduced unnecessary support requests, shortened subscription decision cycles, and helped shift the relationship from annual rediscovery toward informed account management.

Customer Footprint produced measurable improvements across three important areas: reduced internal support burden, increased customer confidence, and shorter subscription decision cycles.

In the testing group, low-value inquiries to assigned Oracle Sales Representatives decreased by approximately 80%. These were the recurring questions customers previously had to ask because they lacked a reliable self-service way to understand their subscriptions, services, renewals, plan structure, utilization, limits, and costs.

User interviews and usability testing also showed a strong positive response to the new experience. Participants described the unified view as clearer, more useful, and more confidence-building than the fragmented process they had relied on before. Instead of reconstructing their Oracle relationship through multiple systems and repeated conversations, account managers could understand their full customer footprint in one place.

The solution also improved the pace of subscription decision-making. SaaS and OCI subscription discussions that typically required 4–6 weeks of negotiation, clarification, and back-and-forth communication were shortened by approximately 1–2 weeks. By giving customers better visibility earlier in the process, Customer Footprint helped them evaluate options, plan budgets, and make renewal or expansion decisions with less uncertainty.

Together, these outcomes showed that the value of Customer Footprint was not limited to usability. The experience reduced operational friction, improved customer self-service, supported more informed account management, and helped change the perception of Oracle from difficult to navigate toward more transparent and easier to work with.

Customer Footprint was a strong reminder that enterprise UX is often less about adding new capabilities and more about making existing complexity understandable.

The data already existed. The subscriptions, renewal dates, plans, utilization details, limits, and cost indicators were already somewhere inside the ecosystem. The problem was that customers could not turn that scattered information into a coherent understanding of their relationship with Oracle. Internal teams faced a similar challenge. Even Sales Representatives, who were expected to support customers through renewal and subscription decisions, did not have a simple holistic view of the customer’s full footprint.

The UX opportunity was to design context, not just an interface.

What worked well was the shift from a system-centered view of subscriptions to a customer-centered view of the relationship. Customer Footprint helped users understand not only what they had purchased, but how those purchases fit together, how they had changed over time, which subscriptions were core or supplemental, and where upcoming decisions needed attention. That broader context gave customers more confidence and reduced their dependency on repeated explanations from Oracle representatives.

The project also demonstrated the value of early, candid research with internal users. By speaking with Sales Representatives before committing to a solution, we uncovered the deeper pattern behind the original request: the issue was not simply visibility, but recurring knowledge loss, annual rediscovery, and the absence of a shared source of context between Oracle and its customers.

There was still room for improvement. The proof-of-concept validated the value of the experience, but a production version would require continued refinement around permissions, data reliability, source transparency, role-specific views, and integration with subscription management workflows. The internal-facing version also introduced additional responsibility: Oracle employees needed enough visibility to support customers effectively, but not so much control that permissions, trust, or compliance could be compromised.

For me, the project reinforced one of the most important principles of UX in complex enterprise environments: clarity can be a business capability.

When customers understand what they have, how it works, and what decisions are ahead of them, they do not just use the product more easily. They make better decisions, require less support, and feel more in control of the relationship.