Skip to content
Case studies

Dooly

Fast and Furious Innovation

TL;DR

Dooly challenged itself by dividing into small cross-functional teams to explore ways to deliver customer value quickly. Using a lean design process and iterative approach, our small team delivered a initial feature that remained a core value proposition until Dooly's acquisition.

Role
Lead Product Designer
Team
1 Product Manager, 1 Designer, 2 Engineers
Timeline
5 days for first release, with two follow-on releases right after

Dooly was an innovative B2B Sales technology startup focused on helping Account Executives (AEs) spend less time updating their CRM and more time selling. Its web application and browser extension tools saved account executives time and effort every day and improved CRM hygiene.

Dooly was acquired in April, 2024 by Mediafly, Inc.

The Challenge

AEs in sales organizations manage a lot of deals in a quarter. They, their sales manager, and other sales leaders in the organization are always asking, "what's up with X deal?" That question sends AEs digging through the CRM for updates, wasting hours every week.

Design goals

Our goals for this project were to help AEs:

  1. Prioritize by helping them see which deals needed attention quickly
  2. Diagnose the most important information on a deal, so they can decide what to do next
  3. Act by helping them understand what they need to do to progress their deals

The twist

For Innovation Week at Dooly, staff were split into four cross-functional teams. Each team had the same objective: ship something valuable in one week.

What we did

With only one week to deliver a solution, we spent the first day on research and ideation, three days in execution mode, and the final day on bug fixes and demoing. We ran a deliberately lean design process in Miro:

Stakeholder interviews and secondary research

I paired with the team's PM to interview stakeholders, including an end user, about pain points tied to our design goals. Engineers observed the conversations. We also reviewed product analytics to check what people told us against how users actually behaved, then consolidated everyone's observations on a shared Miro board.

We used Miro to collaborate on interview findings

Job prioritization

I facilitated a workshop where the team sorted notes into jobs, then prioritized those jobs by feasibility, perceived value, and alignment with the outcomes we believed mattered.

Our simplified jobs map in Miro, with outcomes at the top and jobs below

Sketching workshop

I ran a design workshop with the PM and engineers to generate a wide range of solutions, sketched in Miro or on paper and photographed in. We used dot voting to align on a single candidate.

Team members sketched in Miro or on paper, then aligned by dot voting

Daily check-ins

The team checked in every morning to review progress, talk through problems, and adjust. We tracked progress on the same Miro board, with links to Figma designs and visual previews so stakeholders could follow along.

Product design

We leaned on existing componentry as much as possible to minimize development effort. The first iteration used mostly existing widgets and tooltips.

The first iteration of the feature used mostly existing components

Results

Our team was the only one to ship its first feature iteration on time. In the following weeks we got good signals from users, product analytics, and sales staff. The feature set would be named Deal Vitals, and it became an important selling point for Dooly as it matured over the following months.

First release: Deal Vitals checklist

A widget on the deal overview page acting as a data-hygiene checklist.

A Deal Vitals checklist widget made it easy to see what needed to be done

Feedback on social media was positive, validating our solution path and giving us the impetus to deliver follow-on releases:

Deal Vitals was received quite positively by our customers

Early success signals were corroborated by product analytics showing increased engagement and supporting Dooly's core value proposition of helping organizations improve their sales data:

Increased engagement with Dooly tied to Deal Vitals

Subsequent releases: pipeline scanning and vitals customization

After reviewing feedback on the first release, we quickly shipped follow-up releases to address design goals we had defined together at the start of Innovation Week. The first was to help AEs quickly look across their pipeline:

Pipeline scanning let AEs look across their pipeline to see which deals needed attention

As more organizations started using Deal Vitals, it become obvious that sales teams had different ways of evaluating which deals needed attention. So we introduced configuration to Deal Vitals, letting customers decide when Deal Vitals should appear and what things matter most:

Deal Vitals configuration let teams set up relevant indicators

Summary

Dooly challenged itself by dividing into small cross-functional teams to explore ways to deliver customer value quickly. Using a lean design process and iterative approach, our team delivered an initial feature quickly. Deal Vitals remained a core value proposition for Dooly until its acquisition in 2024.

Deal Vitals was a core differentiator for Dooly