This case study gives an overview of my work at the internship. Interested in reading the whole case study?
Don't have the password? Send me an email - email me!
8 months
Product Design & Owner Intern
Product Design & Owner Intern
Figma, Pendo, Figjam, Claude Design
Hours/week saved per user
Sustainability Managers empowered
Major initiatives led
User stories written & refined
Brightly, a Siemens company, builds facilities and sustainability management software used by operations and sustainability teams managing large commercial property portfolios across North America.
Sustainability managers using Streams were spending 2–3 hours weekly on manual configuration to get data to and from ENERGY STAR.
They needed to connect their buildings to ENERGY STAR to track energy performance scores, sync utility data, and maintain consistent records across both systems.
This connection didn't exist in a way that users could control themselves. It required manual intervention, technical workarounds, and offered no visibility into whether the sync had worked or failed.
Performed competitive analysis and workflow mapping.
Led user interviews, surveys, and usability testing for Energy Manager and ESPM Integration.
Gathered and synthesized user requirements from internal service teams and end-users to identify pain points and opportunities.
Led the design process for Brightly’s energy monitoring platform integration, from designing wireframes and user flows, to iterating based on feedback, and delivering final designs with user stories for development.
Led the migration of historical client feedback into Pendo, Brightly’s product analytics and feedback tool.
Completed Pendo Essentials for Workforce Apps certification to ensure effective implementation.
Worked closely with UX designers, developers, and product owners to align design decisions with technical feasibility and business goals, ensuring smooth handoff from design to development.
Leveraged my software development background to identify APIs and provide technical recommendations during PO meetings.
Open the complete case study for the full process, research, strategy, design, testing, and learnings. This would require a password.
Don't have the password? Send me an email - email me!
Early on, I learned that it’s perfectly normal for some designs to get descoped or set aside. Rather than taking this personally, I recognized that design decisions are driven by business needs and changing priorities. Maintaining flexibility and focusing on the project’s broader goals allowed me to grow as a resilient and strategic designer.
Projects often move fast and sometimes limited budgets and tight timelines mean that not every step can be executed as planned. For example, after initial user testing and implementing feedback, we didn’t have the bandwidth for a second round of formal testing. To ensure some level of insight, I guided a fresh team member through the new designs, asking them to evaluate the experience from a user’s perspective. It wasn’t perfect—but was a practical solution given our constraints.
It’s important to adapt, but sometimes you have to stand your ground, even under pressure. On one project, internal process stakeholders had already reviewed our UI, and tight deadlines made skipping further user testing tempting. My team and I insisted on a quick round of testing with end users, balancing project urgency with the need for real feedback. This approach ensured our designs genuinely met user needs before launch.
Mastering features like auto layout in our design tools greatly accelerated my workflow. It became significantly easier to iterate on designs, incorporate feedback, and prepare files for handoff. This efficiency allowed for rapid refinements and greater overall team agility throughout the project.
While the contents of my work are under NDA, this case study highlights the main scope of work and outcomes. If you'd like to dive deeper and see the actual designs - email me!
Brightly, a Siemens company, builds facilities and sustainability management software used by operations and sustainability teams managing large commercial property portfolios across North America.
Sustainability managers using Streams were spending 2–3 hours weekly on manual configuration to get data to and from ENERGY STAR.
They needed to connect their buildings to ENERGY STAR to track energy performance scores, sync utility data, and maintain consistent records across both systems.
This connection didn't exist in a way that users could control themselves. It required manual intervention, technical workarounds, and offered no visibility into whether the sync had worked or failed.
Performed competitive analysis and workflow mapping.
Led user interviews, surveys, and usability testing for Energy Manager and ESPM Integration.
Gathered and synthesized user requirements from internal service teams and end-users to identify pain points and opportunities.
Led the migration of historical client feedback into Pendo, Brightly’s product analytics and feedback tool.
Completed Pendo Essentials for Workforce Apps certification to ensure effective implementation.
Led the design process for Brightly’s energy monitoring platform integration, from designing wireframes and user flows, to iterating based on feedback, and delivering final designs with user stories for development.
Worked closely with UX designers, developers, and product owners to align design decisions with technical feasibility and business goals, ensuring smooth handoff from design to development.
Leveraged my software development background to identify APIs and provide technical recommendations during PO meetings.
Early on, I learned that it’s perfectly normal for some designs to get descoped or set aside. Rather than taking this personally, I recognized that design decisions are driven by business needs and changing priorities. Maintaining flexibility and focusing on the project’s broader goals allowed me to grow as a resilient and strategic designer.
Projects often move fast and sometimes limited budgets and tight timelines mean that not every step can be executed as planned. For example, after initial user testing and implementing feedback, we didn’t have the bandwidth for a second round of formal testing. To ensure some level of insight, I guided a fresh team member through the new designs, asking them to evaluate the experience from a user’s perspective. It wasn’t perfect—but was a practical solution given our constraints.
It’s important to adapt, but sometimes you have to stand your ground, even under pressure. On one project, internal process stakeholders had already reviewed our UI, and tight deadlines made skipping further user testing tempting. My team and I insisted on a quick round of testing with end users, balancing project urgency with the need for real feedback. This approach ensured our designs genuinely met user needs before launch.
Mastering features like auto layout in our design tools greatly accelerated my workflow. It became significantly easier to iterate on designs, incorporate feedback, and prepare files for handoff. This efficiency allowed for rapid refinements and greater overall team agility throughout the project.
While the contents of my work are under NDA, this case study highlights the main scope of work and outcomes. If you'd like to dive deeper and see the actual designs - email me!
Brightly, a Siemens company, builds facilities and sustainability management software used by operations and sustainability teams managing large commercial property portfolios across North America.
Sustainability managers using Streams were spending 2–3 hours weekly on manual configuration to get data to and from ENERGY STAR.
They needed to connect their buildings to ENERGY STAR to track energy performance scores, sync utility data, and maintain consistent records across both systems.
This connection didn't exist in a way that users could control themselves. It required manual intervention, technical workarounds, and offered no visibility into whether the sync had worked or failed.
Performed competitive analysis and workflow mapping.
Led user interviews, surveys, and usability testing for Energy Manager and ESPM Integration.
Gathered and synthesized user requirements from internal service teams and end-users to identify pain points and opportunities.
Led the design process for Brightly’s energy monitoring platform integration, from designing wireframes and user flows, to iterating based on feedback, and delivering final designs with user stories for development.
Led the migration of historical client feedback into Pendo, Brightly’s product analytics and feedback tool.
Completed Pendo Essentials for Workforce Apps certification to ensure effective implementation.
Worked closely with UX designers, developers, and product owners to align design decisions with technical feasibility and business goals, ensuring smooth handoff from design to development.
Leveraged my software development background to identify APIs and provide technical recommendations during PO meetings.
Early on, I learned that it’s perfectly normal for some designs to get descoped or set aside. Rather than taking this personally, I recognized that design decisions are driven by business needs and changing priorities. Maintaining flexibility and focusing on the project’s broader goals allowed me to grow as a resilient and strategic designer.
Projects often move fast and sometimes limited budgets and tight timelines mean that not every step can be executed as planned. For example, after initial user testing and implementing feedback, we didn’t have the bandwidth for a second round of formal testing. To ensure some level of insight, I guided a fresh team member through the new designs, asking them to evaluate the experience from a user’s perspective. It wasn’t perfect—but was a practical solution given our constraints.
It’s important to adapt, but sometimes you have to stand your ground, even under pressure. On one project, internal process stakeholders had already reviewed our UI, and tight deadlines made skipping further user testing tempting. My team and I insisted on a quick round of testing with end users, balancing project urgency with the need for real feedback. This approach ensured our designs genuinely met user needs before launch.
Mastering features like auto layout in our design tools greatly accelerated my workflow. It became significantly easier to iterate on designs, incorporate feedback, and prepare files for handoff. This efficiency allowed for rapid refinements and greater overall team agility throughout the project.
While the contents of my work are under NDA, this case study highlights the main scope of work and outcomes. If you'd like to dive deeper and see the actual designs - email me!
Got a design problem worth solving, or want to talk shop?
I'd love to connect.
Got a design problem worth solving, or want to talk shop?
I'd love to connect.
Got a design problem worth solving, or want to talk shop?
I'd love to connect.
Got a design problem worth solving, or want to talk shop?
I'd love to connect.
Got a design problem worth solving, or want to talk shop?
I'd love to connect.
Got a design problem worth solving, or want to talk shop?
I'd love to connect.