Project Summary
I redesigned TechSmith’s Enterprise Resources page to better support IT admins deploying Camtasia and Snagit. Through stakeholder collaboration, competitive analysis, and usability testing, I transformed a cluttered resource into a guided deployment journey. The final design improved clarity, reduced confusion, and received strong validation from real IT admins.
Where it all began
At TechSmith, I was assigned to redesign the Enterprise Resources page - a key landing page that helps IT administrators deploy our products (Camtasia and Snagit) across their organizations. This page isn’t just for reference - it plays an important role in customer satisfaction and retention for enterprise clients.
The original task seemed simple: combine two existing pages - an outdated page full of links and a newer page created by the customer success team - into one streamlined resource to improve the deployment experience.
+
Easy enough, right?
I started by meeting with internal stakeholders to understand their goals for the redesign. The main pain points we discussed included:
Lack of a guided structure
Users didn’t clearly understand the tool’s benefits
The page had low discoverability
This feedback helped shape the early iterations of the new page. My initial designs focused on organizing the content and highlighting the most important links for IT admins.
I thought I was almost done - until it came time for reviews.
The review that changed everything
Before finalizing the design, I sent it to Ashley, our marketing team's UX designer. Her feedback completely shifted the project and ultimately helped me grow as a designer.
Ashley challenged the structure of my original design. She pointed out that while the design looked cleaner, it didn’t actually support the real goal: helping IT admins easily deploy software at scale. She advocated for us to return to the UX process to understand our target users' needs better.
Ashley encouraged me to do competitive analysis, looking at how other companies structure their deployment resources. While researching, a clear pattern emerged: every page I saw included step-by-step guidance, actionable tips, and intuitive navigation, making it easier for IT professionals to understand the deployment process.
Inspired by these insights, I restructured the page as a guided deployment journey, offering clarity, flexibility, and support for different user needs.
From assumptions to understanding
To make sure the new page truly fit users’ needs, I collaborated with our UX research team. The researcher recruited five IT admins who had previously deployed our products, and we conducted usability testing using the prototype I designed.
Their feedback was invaluable with every interviewee asking if they could use their own deployment tools - at this moment I realized I did not understand how our deployment process worked. To fix this, we brought in an internal subject matter expert to clarify what the tool actually does - and does not do - which helped eliminate confusing or misleading content on the page.
Before our final interview, we updated the prototype based on feedback, simplifying the language and clarifying the process. I made sure to include that IT admins can, in fact, use their own deployment tools.
Our final test was with Amy, an IT admin actively deploying Snagit. Her reaction said it all:
This is much easier than what’s out there already…
I would happily be sending this to my deployment team
and saying here’s your step by step. You’ve really improved the workflow.
Hearing that from someone using the old and new pages in real time was a huge validation and exciting moment as a UX designer.
What I learned
What started as a basic content update turned into a valuable learning experience with tangible improvement for our users. I had the opportunity to dive into the full UX process - doing research, making changes based on feedback, and testing with real users. Along the way, I collaborated with people across the company, from stakeholders to researchers to subject matter experts, to make sure the solution was accurate and effective.
One of my biggest takeaways was the importance of empathy in design, focusing on what IT admins actually need instead of just what we thought they need.