đ Business Impact
⢠Reduced location scouting costs by 15%.
⢠Successfully convinced stakeholders to support mobile access for an enterprise desktop-only application
⢠Enabled engineering to scope and deliver a fully responsive experience with minimal refactoring
⢠Helped the team unlock broader device accessibility, expanding usability across phones and tablets
đŻ Project Role
Led product strategy and design execution for mobile adaptation of a complex desktop app. Worked closely with engineering and product to build support, reduce implementation friction, and deliver responsive solutions on an accelerated timeline.
đ Skills Used
⢠Product Design
⢠Visual Design
⢠Interaction Design
â˘Â 0 to 1 Product Development
â˘Â B2B Enterprise
⢠Prototyping
⢠Usability Evaluation
⢠Design Strategy
⢠Information Architecture
⢠Responsive Design
⢠Stakeholder Communication
The Problem
Convince team to move beyond desktop
My client had an enterprise app that converted a set of photos into a 3D modelâdesigned and built by an external agency. Before releasing the Beta, the product owner asked if I could redesign the app from the ground up in under three weeks.
I was initially told that users only required a desktop application. However, after reviewing the existing experience and its use cases, it became clear that most of the functionality could and should be accessible across devices.
The Solution
Show them the âtougher stuffâ
To change minds, I needed to prove that mobile could handle the same complexity as desktop. That meant showcasing edits that looked and worked just as smoothly on mobile.
So I presented a desktop edit screen side-by-side with a mobile mockup. The goal? Make it easy to see how little needed to change to bring the same power to mobile or tablet.
Here is my first example â
Getting engineering on board
When engineers saw the mobile design next to the desktop version, the reaction was exactly what I hoped for: "These are mostly the same." That similarity reduced perceived scope and resistance.
I broke the app into modular, âchunkifiedâ sections:
⢠Viewer
⢠Model Details
⢠Photo Set
⢠Tags
⢠Actions
This helped engineering visualize a component-based approach with four main breakpoints:Â 1440, 1023, 767, and 600. From there, they could plan a responsive build with reusable modules.
Sharing mockups in informal 1:1s before reviews gave engineering time to reflect and come prepared to collaborateânot resist.
Let's look at a few more examples â
Getting Product on board
Winning over product meant understanding who they wanted to impress. Maybe it was an exec using an iPad Pro. Maybe it was a stakeholder already advocating for mobile-first enterprise tools.
By acknowledging the political and strategic factors at play, I tailored my pitch to resonate. This wasnât just about screen sizeâit was about positioning the product for broader impact and visibility.
More Mobile Examples
The Results
From fixed desktop to fully responsive
The app is now a fully responsive experienceâaccessible on phones, tablets, and desktops. While the outcome was a team effort, it began with design leadership: a strategy to persuade stakeholders, guide engineering through modular thinking, and align product motivations with user value.
This project proves that a motivated Product Designerâarmed with vision, prototypes, and empathyâcan drive meaningful change.
