My team was tasked with enhancing our PDF Editor to improve usability and efficiency. The previous design failed to make optimal use of screen space, leading to a cluttered and frustrating user experience. Our product manager prioritized the integration of drag-and-drop interactions to streamline tasks and make the editor more intuitive.

My team was tasked with improving our app's search functionality. The current system had separate search bars for each table, filtering only by keyword, which made file searches inefficient and frustrating. The filters were outdated and required too many clicks.

To address the challenge, I began with competitive research, followed by a two-week iterative design sprint to create low-fidelity wireframes. These served as the basis for weekly discussions with the product owner, helping us explore different search modes, filtering methods, and interactions. I refined ideas through multiple rounds of ideation, wireframing, and prototyping, incorporating team feedback and early user testing.We evaluated filtering mechanisms, from simple dropdowns to pill-based selections, focusing on usability and efficiency. Ultimately, we converged on a solution that balanced functionality and ease of use. After developing prototypes, we gathered real user data to validate the designs.

I quickly produced low-fidelity wireframes, enabling rapid iteration and collaboration. This helped visualize and refine multiple search interface ideas before advancing to higher fidelity designs. During this phase, I experimented with local and omni search modes, various filtering methods, and user interactions with search entities.

To validate our design concepts, I developed clickable prototypes for user testing. These prototypes provided valuable feedback on the functionality and usability of the new search features in a realistic setting. Insights from these sessions led to further refinements, ensuring the final design met both user expectations and business goals.

Once the prototypes were refined, we moved to user testing, using usertesting.com for our sessions. The main goal was to determine if users preferred omni search or local search, based on data collected from this A/B test.

The data showed that while Omni Search led to faster task completion times, it caused slightly more user errors than Local Search. Users preferred Local Search, with higher satisfaction scores and fewer errors. This suggests Omni Search is efficient but needs refinement to reduce errors and improve satisfaction. Actionable steps include enhancing Omni Search's usability, potentially through better guidance or error prevention mechanisms.

While we didn’t have the opportunity to measure the full impact of the redesigned search functionality by the time of this case study, our plan was to track key metrics post-launch. We aimed to measure improvements in task completion times, reductions in search-related errors, and overall user satisfaction through in-app surveys and analytics. Additionally, we planned to monitor the adoption rates of the new search features to ensure they were being used as intended.

During our competitive analysis, we identified a crucial gap: while competitors offered integrated eSignature features, our platform lacked this capability. This analysis highlighted the need to develop our own "Digital Signature" product to meet user expectations and stay competitive in the market. The insights gained from this process were instrumental in guiding our development priorities.

I began the process of designing our eSignature product by analyzing the user flows of our primary competitors. Most of these competitors followed many similar design conventions. Users expect eSignature applications to behave in a specific way, and I identified the design conventions that we should follow.

To develop the eSignature feature, I started by creating low-fidelity wireframes to explore and visualize different design possibilities. These wireframes served as a foundational tool for refining the eSignature interface before moving into more detailed and polished designs. This was a months long process; below are some samples from the many wireframes.

Although we didn't have the chance to fully measure the impact of the new eSignature feature by the time of this case study, we planned to track several key metrics post-launch. Our focus was on assessing improvements in user task completion times, reductions in signature-related errors, and overall user satisfaction through in-app surveys and analytics.