OVERVIEW
ibi WebFOCUS is an enterprise-scale business intelligence (BI) and analytics platform. It enables organizations to turn their data into actionable insights through reporting, dashboards, data visualization, embedded analytics, and predictive capabilities. WebFOCUS supports traditional BI reporting as well as more modern analytics needs via self-service dashboards, and AI-powered insights.
PROJECT AT-A-GLANCE
BUSINESS PROBLEM
Customers were frustrated with an outdated interface that no longer aligned with their modern analytical expectations. Decades of legacy code and years of product development occurring in silos had created a fragmented, inconsistent experience that made the platform feel disjointed and difficult to navigate. As long-time users retired and a new generation of administrators, data analysts, and business users stepped in, the product struggled to meet contemporary standards for usability, design, and self-service analytics. This growing gap not only impacted customer satisfaction but also weakened WebFOCUS’s competitive position against newer, more integrated BI platforms that delivered cleaner workflows, modern UI patterns, and unified administrative control. The need for a cohesive, intuitive, and future-ready experience became critical in order to retain users, attract new ones, and bring innovation back to the forefront of the product.
The Before View
RESEARCH
Our user research efforts played a critical role in shaping the new WebFOCUS experience. We began by synthesizing feedback gathered over time through support channels and New Feature requests, which revealed recurring frustrations and unmet needs across the user base. To validate and expand on these insights, we conducted two focus group sessions with key target audiences to understand what aspects of the current experience were working, what was falling short, and what capabilities users expected moving forward. We then followed up with a series of one-on-one interviews, allowing us to dive deeper into the day-to-day pain points and specific workflow challenges that the new Hub needed to address. To validate our research, we completed a comprehensive competitive audit, evaluating leading BI platforms to understand market expectations, differentiated capabilities, and broader customer perceptions.
Together, these research activities provided a clear, evidence-driven foundation for defining the problems and guiding the design of a more unified, modern, and intuitive WebFOCUS Hub. We keep an ongoing dialog with our customers through an active community of ibi users who offer ongoing feedback and personal perspectives that shape our future vision.
Experience Themes
Our research also enabled us to clearly define the core user groups that the new Hub needed to serve. We identified key roles including administrators, developers, data scientists, analysts, and business consumers, and the unique responsibilities and expectations tied to each. This clarity allowed us to map specific needs and pain points to individual roles at different stages of their journey, ensuring that the redesigned experience would address multi-dimensional workflows.
Personas
The illustrations encouraged empathy, clarified priorities, and ensured that design, product, and engineering teams remained focused on delivering solutions that addressed real people and real workflows—not assumptions. We simplified further still to articulate the same essence at a higher level. We use the right visuals for the right conversations to tell specific parts of the story.
User Summary
Ecosystem diagrams and flow models allowed us to articulate the experience at a high level before moving into detailed design. From a platform-wide perspective, we could illustrate how the pieces fit together, highlighting key touchpoints along the user journey, showing variations by role, and mapping dependencies, relationships, friction points, and long-term scalability. These visuals anchored a series of focused discussions with leaders and stakeholders, helping us build shared understanding and alignment on both the concept and the overall approach. With that clarity, we received the green light to move forward.
Ecosystem View
Ecosystem Structural View
Flow Diagrams
GOALS & CHALLENGES
Our goal was to build and scale over a series of releases. We faced a lack of time and resources needed to push out a single big bang release. Instead, we focused on being more iterative and layering capabilities into the fold over time. We developed a feature roadmap and release plan with our partners in Engineering to define architecture requirements that would allow us to build a scalable solution. We prioritized roles, capabilities, devices, and core principles for the MVP with a plan to incrementally make strides towards reaching our final vision.
The primary challenge was the underlying infrastructure and how we could bring together differing code bases in a single experience. We opted for an approach that utilized a simple shell-like structure using iFrames to pull in existing UI from disparate tools. It required only minor adjustments to the tools themselves, mostly within the front-end CSS theme styling but did not require invasive updates to the core foundational code.
Hub Structural View
NEW EXPERIENCE
Because we had limited evidence that customers needed full mobile support, we adopted a lightweight, MVP-focused approach to responsive design. We introduced a single breakpoint that provided both a small and large layout, minimizing engineering effort while still enabling basic mobile usability. This allowed us to test real-world interest, gather feedback, and iterate over time as mobile demand evolved. To ensure alignment with engineering, we also defined clear design principles and illustrated the expected behaviors for this initial responsive experience.
I embarked on a series of content and mapping exercises. I explored all areas to prove our approach would work as expected. I diagrammed the sources and destinations as a way to document the new experience for alignment with the team as well as to hand off early tickets to engineering to begin working on.
Content Mapping
We established a common navigational UI to create consistency and scalability across the platform. By introducing universal navigation bars, shared utilities, and standardized context menus, we unified core actions under a single, predictable structure. This approach not only simplified the user experience but also provided a flexible framework for integrating new features and product areas while maintaining a cohesive and familiar interface.
The WebFOCUS Hub became the unified entry point for the entire WebFOCUS platform. It consolidated all major product areas including reporting, dashboards, data preparation, content management, and administration into a single, centralized experience. Instead of navigating multiple, fragmented interfaces, users now launch every capability directly from the Hub, making it the core workspace for developers, analysts, administrators, and business users alike.
WebFOCUS was designed with strong web accessibility standards in mind, and we continuously maintained an up-to-date VPAT to ensure the platform met key WCAG requirements and remained inclusive for all users.
A major advancement in this release was the unification of platform administration. All administrative functions: security, user and group management, data source configuration, scheduling, distribution, and environment settings were brought together into one cohesive, intuitive dashboard. This dramatically streamlined governance, reduced complexity, and gave administrators full visibility and control across the entire WebFOCUS ecosystem.
It wasn't the prettiest thing to look at... it meant we needed to continue to use the legacy "Bindows" styling. But it was a tradeoff we were willing to live with. It provided an immediate way to solve the problem. The design styling could be updated in a future release while we focused on standing up the core functionality required to administer the platform.
Shown here is an example of the tooling integration with the existing InfoAssist administration console displaying within unified Management Center plugin area. It was designed with flexibility to scale and accommodate all existing consoles as well as future additions.
Embedded Administration Console
With this redesign, the entire platform can now be configured, managed, and monitored from a single centralized location, improving operational efficiency and making it easier for organizations to maintain consistency and scale. The Hub also introduced a modern, clean UI that improves discoverability, organizes capabilities into logical sections, and provides a more user-friendly experience for both technical and non-technical users.
The WebFOCUS Hub represented a major transformation: a unified, modernized, and extensible command center that elevated usability, simplified administration, and strengthened the cohesion of the WebFOCUS platform and provided a strong foundation to support future innovative concepts.
WRAP UP
The first phases of the new Hub have been met with strong enthusiasm and positive feedback from customers, many of whom are now actively planning their next upgrade to experience the redesigned interface firsthand. We showcased the new capabilities across multiple virtual user group webinars and at the annual Summit event, where interest and engagement were especially strong. I also delivered several hands-on demonstrations that highlighted the improvements and offered a preview of what’s still to come.
Looking ahead, we continue to explore new capabilities informed by our early roadmap, ongoing user feedback, and the rapidly evolving BI and analytics landscape. Our efforts are increasingly focused on advancements in AI and ML, particularly LLM and SLM configurations, as well as more user personalization to ensure the Hub remains modern, responsive, and future-ready.