SCOPE Better by Role/Taks • 

Scope by Role was meant to be the second most-used way to scope on the platform. Only 22% of customers were using it. Research across users and the system showed why: load times hit 30 seconds on large scopes, key financial data needed extra clicks to find, and the table didn’t work like Excel, which is exactly how agency teams think about pricing. It wasn’t that users didn’t need it. It was just too painful to use.

95%

FASTER loads (30 s → 1.5 s)

50%

feature adoption

65%

FASTER scope completion

DISCOVERY

I went through over 100 client support tickets and ran sessions with clients and the CX team. Three things came up every time: the wait, missing margin data, and a table that didn’t behave like a spreadsheet. Those three things drove every decision. The original version had been built quickly and constantly topped up with features different clients requested, added without much thought, which had the opposite effect. Instead of making it more useful, it made it worse.

The page was on loading mode for over 9 seconds.
Loading screen remains around 10 secs or more depending of the size of their Scorecard
Original Scope by Role table and features
Original Scope by Role
WHAT I DID

The research pointed to one clear priority: fix the performance. Everything else could come once users could actually access the table and start using it. I rebuilt the flow around progressive loading. The numbers people needed loaded first. Everything else came after. The table was redesigned to work like Excel; no relearning needed. Margin impact showed up in real time. CX got a one-click trigger to generate quotes. Skeleton loaders replaced the blank wait screen so the product felt faster before the data even landed.

Scope by Role Wireframes
Wireframe of By Role view and By Task view
OUTCOME

Adoption went from 22% to 50%. Scoping time dropped by 65%. Load times went from 30 seconds to 1.5 seconds. We also started getting feature requests and feedback we’d never had before. A sign that it was finally being used properly.

Final interphase with anotations
Collection of most use components on this feature. Financials is use in all types of scoping, which is already on the design system.
Most relevant Finance information in one sight.
I designed the flow with a split path, depending of users choosing pre-loading roles or not. And how to let the user understand the consequences of their choice.
Flows when creating from scratch a Scope by Role, without and with preloaded Roles and Departments.

“The updated pricing tool has cut our project scoping time in half and eliminated the pricing errors that used to cost us thousands.

 

 

–– Agency CEO and ScopeBetter client

Scope by Role feature table redesigned.
Redesigned Scope by Role

Company

SCOPE Better

Year

2023-24

Design Tools

Figma and Miro

Project Timeframe

1 Month

Uncover more of my work

  • Ending the “needle-in-a-haystack” hunt. A zero-to-one feature that slashes the pain of editing 500-row scopes.
  • Agencies always work against the clock. Scope by Timeline gave them a way to plan and price a project visually, translating the existing scope table into an editable Gantt-style view that updated in real time.
  • The most important numbers in a CPQ platform were buried at the bottom of a 500-row table. A new financial summary block brought them to the top: configurable, collapsible, and built to make SCOPE Better feel like software, not a spreadsheet.
  • Design a flexible structure that supports richer communication at scale, without adding visual or cognitive clutter
  • Returns were a major pain point in the user journey and one of the biggest leaks in the business. It was a manual process, so the risk of error was guaranteed.
  • Redesigning Samsung's seller app(web and native) to turn training into a game, one bite-sized win at a time.
Back To Top
VIEW