
Building a UI/UX practice at SAVO.
SAVO is where I began to see how much I could contribute beyond frontend engineering. My path into UI/UX went through a company-wide shift in how we worked, Product Owner training, and a period with the Data Science team. Each chapter changed how I thought about building software with other people.
I led the initiative to form our UI/UX team, hired visual designer Brittany Mikottis, and worked alongside her on design and implementation. I also built the shared Ember.js component system and style guide used across several parts of the product.
SAVO was acquired by Seismic in 2018.
People behind the work LinkedIn profiles
UI/UX team
- Brittany MikottisVisual Designer
- Tom GreenUX Designer
- Allison PaulResearch outreach and testing
- Eric SandsDelivery Manager
Product and Data Science
- Peter CaronSenior VP of Product
- Jeff CharbeneauData Scientist
- Braun ReyesDatabase specialist
- Megan “Meg” GancarczykJunior Product Manager
- Greg GoodmanSenior Product Manager
- Zach DebelakHead of Product
Agile transition
- Brian HaukAgile Coach
- Andrew IkamasScrum Master
Leadership and support
- Jason LiuCEO
- Doug MarquisProduct Development / CTO
- John NarofskyMy manager

Starting with the work in front of me
SAVO helped salespeople find and use content for conversations with clients and prospects. I joined as a self-taught frontend engineer. For roughly my first two and a half years, I didn’t feel I was growing very much beyond the work assigned to me.
We worked in a waterfall process, following detailed product requirements documents that defined what we were supposed to build. Those requirements could still change late in the process as new demands came from sales. There wasn’t much room in my work to explore the problem or help shape the solution.
Seeing another way to work
The company was entering a period of change. In June 2014, SAVO announced a $35 million funding round led by Goldman Sachs, with two Goldman Sachs representatives joining the board.
Jason Liu was appointed CEO in March 2015. Doug Marquis joined that October as EVP of Product Development and later became our CTO. For me, the shift toward Agile development during this period opened up a different way of thinking about software.
I remember the organization becoming much flatter, with people who had held leadership roles moving into individual contributor work. It was also a difficult period. There were major cuts to QA and Support, and colleagues lost their jobs. The changes that opened up opportunities for me came alongside real disruption for other people.
Working with Brian Hauk, our Agile Coach, and Andrew Ikamas, our Scrum Master, was eye-opening. They demonstrated a more collaborative way of working through problems together. I began to see that I could contribute to how we approached the work, as well as what appeared on the screen.
That shift opened the door to my Product Owner training and a very different role on the Data Science team.
Finding my footing as a Product Owner
SAVO paid for me to become a Certified Scrum Product Owner (CSPO). I became the embedded Product Owner for the Data Science team, working on the Predictive initiative and reporting directly to the CTO.
I worked with Peter Caron, a Senior VP of Product, to define the goals for an intuitive recommendation system. We wanted to help salespeople prepare for deeper conversations with their clients.
The bigger ambition was to use a salesperson’s calendar to understand who they were meeting with, then connect that context with the content SAVO housed and other information we could gather. Rather than making someone search through a library before every meeting, we wanted to help bring relevant material to them.
Jeff Charbeneau joined as our Data Scientist. Much of his work involved “laying pipe”—building the data pipelines needed to collect information the team could work with. Braun Reyes, a database specialist on the team, worked with Neo4j to build graph databases.
My part often came through sprint planning and grooming sessions. We kept meetings spaced out so the team could spend most of its time building and experimenting, with room to decide how best to approach the problems. I facilitated those conversations and often worked at the whiteboard, sketching concepts as people talked through them. I brought my technical perspective where it helped, while learning a domain that was new to me.
Over time, I found it difficult to work with the uncertainty around the team’s direction. I was well outside my comfort zone, and I missed the tangible nature of frontend engineering: making a change on screen and seeing the effect of my work. I shifted my focus toward the interface and user experience work that followed.
The recommendation initiative ultimately didn’t reach customers; company priorities changed. Even so, the experience broadened how I thought about product development, facilitating a team, and giving people room to solve problems.
During that period, I read Steve Krug’s Don’t Make Me Think. It helped shape the user advocacy that followed.
Making room for the people using the software
The executives buying SAVO, the administrators managing it, and the people using it every day had different needs.
Product decisions were heavily influenced by sales commitments. We also supported older enterprise environments, which placed real constraints on the interface. I wanted us to hear more directly from the sales and marketing people who spent their days using what we built.
I researched ways to establish a baseline for the usability of our systems and settled on the System Usability Scale (SUS). The idea was straightforward: get an initial score, then use it to track whether we were making the software easier to use.
I worked with Megan “Meg” Gancarczyk, a Junior Product Manager at the time, to prepare the questionnaire and its introduction to the SAVO User Alliance Group. Just before it was due to go out, Greg Goodman, a Senior Product Manager, stopped the initiative over concerns about how low our initial score would be. We never sent the questionnaire, so we didn’t establish that baseline.
I still wanted us to give the people using SAVO more attention. I kept advocating for a visual designer and a dedicated UI/UX team.
Starting with the team
The dated interface gave us a concrete place to begin. My manager, John Narofsky, helped carry my request through the organization and secure the CTO’s approval to hire a Visual Designer.
I wrote the job posting, ran the interviews, and hired Brittany. From there, we helped form a UI/UX team that brought visual design, user experience, research, and frontend engineering together.
Eric Sands, previously our VP of QA, became the Delivery Manager on the UI/UX team after the Agile transformation. We worked together as colleagues on that team.
Brittany and I worked hand-in-hand throughout the work we produced together. I was involved in both design and implementation, and our collaboration continued as we built. That relationship was central to the Asset Page redesign and the shared UI foundation that supported it.
Helping people work with an asset
The Asset Page was where someone could view a document or other piece of content and decide what to do with it. We wanted to make it easier to navigate the asset and take the next action: save it, share it, or edit it.
Brittany and I worked through the redesign together, from design through implementation. We put it in front of end users through multiple rounds of feedback and usability testing.
The redesign shipped to customers and was well received. Users particularly appreciated the added mobile support, which was new to them at the time.

Finding content across desktop and mobile
Search screens from the SAVO portfolio archive, showing results, filters, and tags across desktop and mobile layouts.




More Search screens (4)




Bringing research into the process
Access to the SAVO User Alliance Group eventually gave us a pool of administrators and end users for interviews and testing. Tom Green was our UX Designer, and Allison Paul later managed outreach and scheduling. Allison had moved into our UI/UX team from Support during the layoffs, which allowed her to stay at SAVO. Tom and Allison both frequently facilitated user-testing sessions. We worked together to define research goals.
Getting candid feedback took relationship-building, too. We worked to create the trust and space for one-to-one conversations with the people using the software.
Alongside Brittany, the rest of our UI/UX team, Head of Product Zach Debelak, and the wider Product team, I helped define a product process that included research throughout the work. Our process diagram connected early exploration, design, development, and feedback after release.


Understanding how we worked together
I also wanted us to be able to describe the less tangible parts of our team culture. I brought ideas from my personal-development interests into a workshop with the UI/UX team.
We gathered in a room with whiteboard walls, and I projected an empty mind map from my laptop. Together, we built out our values, principles, and the skills, traits, and abilities we considered important. I facilitated the session and created the map; the team shaped what went into it.
The exercise gave us a clearer way to talk about ourselves as a team. Later, we used it when interviewing and hiring another UX researcher. It helped us move from a vague idea of “culture fit” to more specific conversations about how someone might work with us. We hired an excellent researcher, and I felt the exercise worked very well for us.

Learning to contribute beyond my title
When I first joined SAVO, I compared my self-taught background with the degrees and experience of the people around me. I thought of myself as someone who was good at CSS. I grew as an engineer there, deepening my JavaScript skills and learning to build shared UI components that other engineers could use. Over time, I also learned that my product thinking, commitment to users, and interests outside engineering could be useful to the team. That meant the world to me.









