Overview of Re-Envisioning a Product

From...

To...


Note: For privacy, I rebuilt the 'To' screen after my separation from the company and is my own prototype of the work white labeled into Accenture's brand colors because I like the bold color pallete. The image on the 'From' is findable on the web via product documentation.

Product Re-envisioning by the Numbers

Project Leader

My Role

1

Acquisition

+80

Interviews

$XXX M

Expected ARR

The Bottom Line

In order to remain competitive in the marketplace, we needed to deliver a scalable, mobile friendly, smart building experience based on modern architecture principles.

The Process

step 1

Running Generative Research

Using participatory design, the team worked with a third party, Lextant, to run a global study on the ideal building management solution.

step 2

Establishing a Current Experience Baseline

The product had multiple products coming together into a single pane of glass, and in the midst of the redesign the company acquired another SaaS company in the smart building space.

step 3

Scoping & Delivering the MVP

Breaking down the product vision into iterative chunks to be developed in the MVP, building ahead with the design system, and establishing & adopting new ways of working.

  • Ideal building management solution experience interviews
  • Experience model creation for our core persona
  • Story board iterations and concept testing
  • Building scorecards against experience model for future testing
  • Consolidation of existing product personas & refinement into 3 core user experience personas
  • Mapping current state architecture
  • Refinement of acquisition's product persona to ensure apples to apples comparison
  • Utilized product analytics to determine most valuable feature sets
  • Card sort to capture user's mental model
  • Tree test to establish future state architecture
  • Work with product to write and refine product requirements documents then define user flows
  • To increase speed of delivery, adopted Figma, Jira, & design ops best practices
  • Translation of product vision into feature sets & design deliverables
  • Prototype testing with experience metrics


The Experience Design generative research informed product & technology problem statements

Once there was a clear understanding and model of what our core persona was looking for product and technology developed their own problem statements in response to the research and to build the business case for the redesign and inform their own roadmaps.

example of an experience model
Note that there's a significant amount of detail behind each of these circles and this serves for illustrative purposes only. You can learn more about experience models by reading User Experience Research.

Product Problem Statement Example

The current product solution had a variety of challenges to be addressed to stay competitive and ensure customers achieve the full value from the solution. These challenges were also key customer asks / requirements and included:

  • Inability to personalize the experience for users and allow users to customize their experience further
  • Lack of mobile interface
  • Inherent challenges with meeting accessibility guidelines
  • Communicating outcomes to customers in a meaningful and actionable manner

Technology Problem Statement Example

There were also several platform and data shortcomings that were impacting the speed of customer value creation and the ability to create meaningful content for customers including:

  • Data stored "above" platform at the application layer instead of centrally
  • High costs for data processing and normalization
  • Difficulty in triaging and addressing data quality issues
  • Challenges to enabling AI-outcomes throughout the experience