Portfolio complexity
Financial, program, and technical information needed to be understandable in one place.
SAAS · SERVICENOW · FINANCIAL MANAGEMENT · CUSTOM VS. CONFIGURED
Leading UX strategy across custom and out-of-the-box ServiceNow financial management initiatives, balancing clarity, governance, adoption, and speed.
EXECUTIVE SUMMARY
Across two large ServiceNow financial-management programs, the work needed to give decision-makers a clearer view of portfolios, budgets, dependencies, and future needs.
One engagement was custom; the other focused on standard SaaS adoption. Together, they showed how UX can flex to meet different constraints without losing clarity or trust.
01 · THE DELIVERY CHALLENGE
I immersed myself in the existing workflows, agency and contract constraints, client priorities, and platform limitations. I synthesized those realities into a practical direction the delivery team could follow and the client could support.
Financial, program, and technical information needed to be understandable in one place.
Custom and configurable SaaS delivery required different ways of working.
Two-week SAFe cycles demanded a practical relationship between research and action.
New workflows needed training, communication, and stakeholder confidence.
02 · THE PRODUCT VISION
The platform brought configuration, analysis, evidence, and collaboration into one governed environment, helping people move from finding information to acting on it. Answers drew on an on-premises, fine-tuned, domain-specific language model and retrieval across more than a decade of source material, so sensitive data stayed inside the organization’s boundary.
Capture budget requests and funding needs in a consistent workflow.
See how funds are allocated and available as plans change.
Follow spend against funding timelines and budget-specific rules.
Compare financial information to support clearer portfolio decisions.
One consistent view across three distinct budgets
A broader financial view designed to serve as a consistent standard across the agency and its bureaus.
Vendor management built on the same layouts, connecting contract and spend context to the portfolio view.
Delivered as part of a custom ServiceNow engagement for a federal civilian agency. Client CUI details withheld.
03 · THE EXPERIENCE MODEL
The experience strategy combined shared research and design principles with the practical differences between building a tailored product and configuring a SaaS platform.
Turn stakeholder input into clear decisions about workflows, configuration, and tradeoffs.
Balance user needs with the capabilities and limitations of each implementation model.
Make communication, training, and readiness part of delivery—not an afterthought.
04 · FROM INSIGHT TO IMPACT
Led workshops and stakeholder interviews across program, financial, and technical domains.
Created prototypes and design concepts for both custom workflows and SaaS configuration.
Embedded UX criteria, training, and communications into agile delivery.
KEY NUMBERS · CUSTOM SERVICENOW PROGRAM
Within two months, I delivered layouts and design standards for three initiatives, bringing operating, capital investment, and working capital into a consistent annual portfolio view while retaining each budget’s distinct rules and timelines. The shared foundation also supported vendor management and broader agency financial views.
Research and stakeholder input informed workflow, configuration, and design priorities. Prototypes and adoption materials gave the delivery team concrete artifacts to use as implementation moved forward.
TAKEAWAY
Research-driven design helps teams move quickly without treating usability, confidence, and adoption as optional.