.png)
.png){kind=small}
Summer 2022 - Spring 2023
.png)
I joined the Pathfinder team shortly after they had been given the green light to take the initial hackathon idea and make it a consumer product. The next step was to create an Alpha version of the product for release to internal JLL employees. From the hackathon, we had a rough interactive prototype site that was essentially a basic proof-of-concept. There were quite a few outstanding questions such as:
• Which audience(s) might use Pathfinder?How does Pathfinder fit into the broader narrative of sustainability and commercial real estate?
• How do sustainability consultants currently create predictive models?
• What specific tools and techniques do they use?
Starting with these questions and the proof of concept prototype, I worked closely with my project manager and one of JLL’s senior sustainability consultants to unpack the in’s and out’s of commercial-scale modeling. Over the course of several weeks and many interviews with the consulting teams at JLL, we learned that consultants primarily created complex models in Excel. The challenge with data-intensive analysis in UI is incorporating the power of Excel, without forcing the user into spreadsheets. We wanted to maintain the easy of use and calculation that Excel gave consultants, but make the UI more usable by a less technical user type.
One of the fundamental challenges in creating this foundational UI was establishing a sense of hierarchy for the different modeling elements. Based on the previous series of discussions, we were able to categorize the model into three groups of entities: Scenarios, Buildings, and Actions. Scenarios are the main bucket that users are modeling within. Scenarios are collections of Buildings which contain Actions. Buildings might make up a client’s current real estate portfolio, might represent a particular geographic subset of a portfolio, or possibly represent a set of real estate the client might be interested in purchasing.
For all of these use cases, the client has to decide how to get the carbon footprint of these Buildings to net zero emissions. In Pathfinder, they can do this by applying Actions to each of their Buildings.
%20Scenario%20Level%20-%20Buildings%20Populated.png)
%20Add%20Action%20Choose%20Action%20Type.png)
%20Building%20Manager%20Filled.png)
A few months into the Pathfinder alpha project, a larger initiative was introduced to create a design system across JLL/T’s Revenue division products. I volunteered Carbon Pathfinder as the guinea pig product. As a result, a near complete overhaul of the visual design was needed. I worked closely with several Revenue designers to apply the new design system principles to Pathfinder, while also providing feedback and inspiration for new elements.
The result was a much cleaner and more functional UI. Some of the notable changes included: new typography, colors, formalizing spacing grids, and considering tablet-sizing responsiveness. In addition, this overhaul provided a great opportunity to establish new working pattens with the front-end development team. Through the process of several key meetings and regular check-in's, we were to hone in on a system of design, hand-off, and implementation that improved the working relationship for all.
The new Carbon Pathfinder (from top left to bottom right): Scenario Level, Building Level, Creating an action, and the Building Manager
%20Scenario%20Level%20-%20Buildings%20Populated.png)
%20Building%20Level%2C%20Actions%20(Populated)%20(1).png)
.png)
%20Base%20Year%20Energy%20(1).png)
Once development on the Alpha version of Pathfinder was complete, I collaborate with my product manager and our new user researcher Olivia Harold to test the product. We ran feedback sessions with internal JLL sustainability consultants, primarily based in the U.K. These sessions typically lasted 2 hours. In that time, there was open forum for users to jump in with specific feedback or questions. In between questions, we would discuss some of the considerations and tradeoffs made in the initial UI to get a sense for whether the users might validate some of these decisions.
At the end, we had an extensive list of improvements to make, primarily in terms of increasing transparency in terms of how the decarbonization calculations were made. There was also a clear opportunity to create some sort of onboarding experience to introduce users to the product, particular for those future users outside of JLL. Since this time, myself and the rest of the Pathfinder product and developments team have continued to iterate on this feedback. Pathfinder is now currently onboarding its first few public-facing clients.
