PROJECT 3

THE ONE WHERE I ASK GAME-CHANGING QUESTIONS

6 minute read

PROJECT HIGHLIGHTS

  • User and stakeholder research
  • Large, complex project

THE TEAM

  • Project manager
  • 30+ developers
  • + me (Lead UX Designer)

TIMELINE

  • Overall: 55 weeks
  • Design: ~20 weeks

Hey there, you busy recruiters and managers 👋
Here’s your highlight reel—skip ahead for the full story:

GlobalGreen Warehouses needed a streamlined way to manage their resource-intensive buildings. Their existing tools were outdated, scattered, and didn’t meet new climate or budget goals.

As the project’s sole UX designer, I guided the team from chaos to clarity. By questioning assumptions, listening to users, and overhauling the app, I helped cut through the noise and laid a foundation that made managing buildings—and their energy use—a whole lot smarter.

GlobalGreen’s Operational Hurdles

A snapshot of the chaos, storyboard-style—because words alone don’t do it justice:

Static Insight Image
The Ask

GlobalGreen wanted one app to control building systems, modernize old tools, and speed up upgrades—while keeping code in-house to cut long-term costs.

Stratus (anonymized) was hired to build it, but progress stalled. Teams were misaligned, goals were fuzzy, and no one had stepped back to ask the right questions.

That’s when TensorIoT stepped in—to bring clarity, align stakeholders, and get things moving again.

My Role

I joined as the sole UX designer to cut through the noise and bring direction. My job: challenge assumptions, uncover real user needs, and turn chaos into a clear, buildable plan.

Across three phases over two years, I helped align teams, prioritize user outcomes, and shape a product vision that stuck.

Version 1 (April - July 2022)

When I joined, the team handed me a list of features and rigid instructions to cram everything onto a “single of glass”—just slap some “shiny” on it, no time for bigger questions.

My quick mockup ticked all their boxes… until the demo. Stakeholders raised red flags: we didn’t have access to half the data powering these features, and no one was sure the design actually solved user pain points.

V1 designs
  1. EVERYTHING FOR EVERYONE = NOTHING FOR ANYONE

    This dashboard tries to do it all—leaving users overwhelmed and without clear priorities. Managers need focus, not a buffet of metrics. With thousands of sites and HVAC units, this layout wasn’t scalable anyway.

  2. A MOONSHOT WITHOUT THE ROCKET FUEL

    The visuals relied on data that didn’t exist. GlobalGreen had no way to track site-level energy use, and retrofitting for it would cost a fortune—and take years we didn’t have.

  3. LOST IN A MAZE OF MENUS

    Ambiguous menu labels led to confusion. What’s “my eBSM”? Are those links filters or full pages? Navigation shouldn’t require a guessing game.

Version 2 (August - December 2022)

After the v1 demo flopped, the team was stuck, unsure where to go next. Three phases in, it hit us: we’d skipped the basics. I stepped up and started asking the tough questions:

  1. What problems are we actually trying to solve?
  2. What data and resources do we really have to work with?
  3. And who’s calling the shots?

To tackle these questions, I identified Morgan, the Sr. Program Manager, as our key decision-maker, and together we pinpointed Regional Warehouse Managers as our central users. Reviewing existing apps and touring sites with Morgan laid the groundwork for key insights and next steps.

Then I went straight to the source—interviewing six Regional Managers to learn what frustrated them in the current app. Their pain points were clear: confusing filters, scattered data, and no way to prioritize.

Persona

WHERE THE CURRENT BMS FALLS APART

Turns out, our v1 had just repeated the same mistakes. Here’s what users struggled with—and how I made sure v2 didn’t.

While I dug into user pain points, devs explored what data was actually usable. We regrouped for a Long-Range Planning session, where I led the team through insights and helped shape a roadmap that got stakeholders excited 🥳.

Impact-effort matrix

IMPACT-EFFORT MATRIX

I led an effort vs. impact exercise to cut the noise and focus on high-value, realistic features. This gave v2 momentum and made our decisions bulletproof in front of stakeholders.

With direction locked, I designed a new app that tackled real user needs and nailed our business goals. Here's how we brought clarity, sanity, and a little ✨ polish ✨ to v2:

BMS, BUT MAKE IT MAKE SENSE

Version 3 (January - July 2023)

With funding unlocked and lessons from v2 in hand, we were ready to move from MVP to something that felt truly strategic—leaner code, smarter filters, and data-driven insights that scaled.

Here’s how we took things from solid to standout:

Over three phases, I became the team’s not-so-secret weapon—asking the sharp, game-changing questions that shifted priorities and cleared the path forward. By bridging user needs with business goals, I crafted designs that didn’t just solve problems—they set the stage for future success.

The payoff? A final demo I led that left stakeholders energized and on board, showcasing a sleek, scalable app that managers could actually use. With this foundation in place, the next steps were clear: continue migrating pieces of the old apps into this one, expand to other target personas, and ensure each new feature added strategic value.