UX review, recommendations, and wireframes · A Howze-Edge LLC engagement
A platform built by engineers, about to be handed to everyone else
OptiCx runs analytics on the chillers, cooling towers, and pumps inside huge facilities. Built for internal engineers, it now had to work for Technical Account Managers at scale, and one day for customers. The team didn’t want a redesign. They wanted direction they could build themselves.
- The problem
- An analytics platform built by engineers for engineers, about to be handed to account managers and, one day, customers.
- What we learned
- TAMs do not think in features like Charts, Alerts, and Reports. They think in Sites, Rules, Issues, and Equipment.
- The decision
- Organize around those objects, scope everything with one context bar, and answer the team's ten questions as patterns they could build themselves.
UX Design Findings & Recommendations
OptiCx Analytics Platform
Prepared for Optimum Energy
Howze-Edge LLC · Robert Howze-Edge, Principal · April 2026 · Version 3
- Foundation · Object model
- A · Issue management, Q1–4
- B · Information architecture, Q5
- C · Rule construction, Q6
- D · Rule administration, Q7–8
- E · Visual consistency, Q9–10
- Next steps · Sequencing
What they got
Answers they could build on their own
Not a redesign. A findings report that answers each question straight, a shared object model, four wireframes for the riskiest change, and design rules engineers and AI coding tools can follow.
The finding everything else hangs on
The navigation was organized around features: Charts, Alerts, Reports, Admin. But TAMs don’t think in features. They think in Sites, Rules, Issues, and Equipment.
Charts & PagesAlertsReportsAdministration
SiteRuleIssueEquipment
How we got there
Diagnose first, then direct
- 1Walkthrough
The product team demoed the platform and the problems they felt.
- 2Hands-on audit
With my own login, I worked through it the way a TAM would.
- 3Ten questions
We agreed on the questions that mattered most for the next tier of service.
- 4Working sessions
Each answer was pressure-tested with the team, live.
- 5Findings and direction
A report, wireframes, and design rules the team could build alone.
The ten questions
Every question got a straight answer, then a pattern to build
AIssue management
A filterable table with saved views, fewer default columns, and count badges that let TAMs scan without clicking.
One vertical timeline that merges every human action, read before you act, beside a separate action panel.
Bring the data to the issue. Quick links now, embedded mini-views next, a split pane later.
Table to scan, panel to understand, inline actions to resolve. The TAM never leaves the page.
BInformation architecture
A persistent context bar scopes every page below it: Global, a Customer, or one Site. Pick once.
Phase it, and tie every visual change to a functional one so the new look means a better tool.
CRule construction
Keep the four steps. Add a summary step, drafts, and an entry point that knows where you came from.
DRule administration
Show what applies here, not everything that exists, with available rules one click below.
A schedule belongs to the rule-site pair. Show "Global default" or "Custom" right where you read it.
EVisual consistency
Define one badge color system and one filter bar, write them down, and use them everywhere.
The table answers "Do I need to care?" The panel answers "What do I do about it?"
Foundation · Object-oriented UX
Map the nouns before drawing a single screen
I listed every noun the team and the TAMs used, then what each one holds, what you can do with it, and what it connects to. The object model is why the rest of the recommendations hang together instead of reading like a list of fixes. Pick an object.
Mapped to the interface: attributes become table columns and panel fields, calls to action become the panel’s buttons, and relationships become the quick links. That’s Q1, Q2, and Q3 in one sentence.
Direction sketch · not the shipped product
A working sketch of the issue workspace
The report described patterns. This sketch puts them together so you can feel them. Switch the context to one site and watch the table change. Open an issue, read its history, then verify or resolve it. The green Q markers show which question each part answers.
- Q5aOne context bar
Pick Global, a customer, or one site, once. Every page follows it.
- Q1Saved views with counts
Scan the tabs without clicking into each one.
- Q2–4Table, panel, inline actions
Scan, understand, and act without leaving the page.
Rule administration · Q6 to Q8
Show what applies here, not everything that exists
At a station, a TAM needs the 15 rules running there, not the 200 in the library. The library is for the people who build rules. The site view is for the people who run plants.
- Every 6 hoursGlobal default
The rule uses the library’s schedule. Muted, because nothing needs attention.
- Every 2 hoursCustom
This site overrides it. Distinct, with an edit icon, so overrides never hide.
- No scheduleCreate
A warning and a way out, right where you notice it.
A schedule belongs to the rule and site together, not to the rule alone. Once that was clear, the confusion went away.
The riskiest change, drawn first
From a picker on every page to one bar for the whole product
Moving the site context out of each page touches every screen, so it got wireframes before anything else. Low fidelity on purpose: the team argued about the structure, not the colors.
Rules engineers and AI tools can follow
Decide once, write it down, use it everywhere
The team had already picked a component library. The bigger win was the layer on top: a short set of rules so every new screen comes out consistent, whoever builds it.
State badges
One color per state, in every table, report, and eventually the customer portal.
- UnverifiedNeeds triage
- OpenUnder investigation
- ResolvedDone and documented
- IgnoredDismissed, with a root cause
- ViolationNot in workflow yet
Priority badges
Priority gets its own shape and color, so it never reads like a state.
- HighAct today
- MediumThis week
- LowWhen there’s room
Table or panel?
For every proposed column: would a TAM use it to decide which row to click? If not, it goes in the panel, or nowhere.
Table: “Do I need to care?”
- Name
- Source
- Priority
- State
- Occurrences
- Last activity
Panel: “What do I do about it?”
- Timeline
- Occurrence chart
- Root cause
- Resolution
- Labor hours
- Comments
- Related rule, site, equipment
Refresh in phases
Never ship a redesign that only changes the look. Every visual change rides along with a better tool.
- Q2New components on Issue Management, Rules, and the rule wizardNew pages only
- Q3Top navigation, the context bar, and the System Overview sidebarThe plant schematic stays as is
- Q3–Q4Everything else, as each page comes up for feature workNo paint-only passes
What I recommended doing first
A sequence, not a wish list
- Week 1Align on the context model
A 30-minute whiteboard session. Saves weeks of rework.
- Weeks 1–2Write the design rules down
Badges, filters, tables, panels, in a form engineers and AI tools can follow.
- Q2Ship Issue Management
The TAM’s daily driver, and the base for every new service deliverable.
- Q2Ship Rules Administration
Fold the scheduler page into one rules list with a context toggle.
- Q3–Q4Refresh the rest, in step with features
No paint-only passes. Every new look ships with a better tool.
