Meltwater

I doubled a product organization in six months without losing a single person. That sentence sounds like a recruiting brochure, but the 100% retention number during that kind of hypergrowth is the result I’m most proud of from my time at Meltwater — because it validated an approach to team building I’ve used in every role since.

The Platform

Meltwater started as a media monitoring service and evolved into an enterprise intelligence platform processing 10 to 50 terabytes of data daily across a 60-plus petabyte historical repository. Customers ranged from PR teams tracking brand sentiment to crisis response organizations monitoring real-time signals — everything from competitive analysis and industry trends to literal threat detection. The AI sentiment analysis engine turned that firehose of media, social, and news data into actionable intelligence. My role was designing the interfaces that made that intelligence accessible: how analysts configured triggers, consumed alerts, explored trends, and reported findings to stakeholders who needed answers without understanding the underlying data infrastructure.

The design challenge was density without overwhelm. Users needed to monitor dozens of concurrent signals across millions of sources, drill into anomalies in seconds, and produce executive-ready reports — all within the same tool. The product served everyone from a solo PR manager at a mid-market company to a 30-person insights team at a Fortune 500, and the interface had to scale across those contexts without fragmenting into separate products.

Scaling the Team

When I arrived, the product organization had 17 people supporting an engineering team of over 200 across five continents. That ratio was unsustainable. Design was a bottleneck, and the team knew it. I needed to nearly double headcount fast while keeping the existing team intact and productive — not an easy combination when new hires consume mentorship bandwidth from the people already doing the work.

My approach was culture-first hiring paired with structural changes that distributed decision-making authority. I restructured the team to give strong performers more autonomy — providing oversight and decision-making frameworks rather than dictating detail. The goal was a team that could operate effectively whether I was in the room or not.

Two early hires were critical. I brought in Ityam, whom I’d first hired at Kno when she was a year or two out of her master’s program, and Travis, a graduate school colleague. These weren’t just skilled designers — they were people who could echo the systems thinking approach and mentor new hires during onboarding while I focused on the next round of recruiting. Ityam went on to lead her own design and product team at a Series C company. That trajectory started with the mentorship structure we built at Meltwater.

The remaining hires came through a deliberate process: culture fit first, then skills assessment, then a realistic preview of the actual work and team dynamics. No surprises after the offer letter. The result was 18 new team members in six months and zero departures from the existing team — a retention rate that organizational behavior research consistently identifies as the product of ownership and participation, not compensation or perks.

Systems Thinking as Operating System

The broader initiative I drove at Meltwater was introducing systems thinking as a shared language for how the organization solved problems. For sales executives, I framed it around understanding customer problems as interconnected systems rather than isolated feature requests. For engineering leaders, it was about communication structures that reduced the friction between product intent and technical execution.

On the design and product side, I established concrete frameworks. SSNiF analysis — Stakeholder, Situation, Need, Feature — gave the team a repeatable structure for decomposing problems before jumping to solutions. I automated design communication through InVision, established Balsamiq and Sketch as core tools, and implemented Zeplin when it first launched to bridge design-engineering coordination. These weren’t just tool choices — each one formalized a handoff point that had previously been informal and inconsistent.

I also brought the team into strategic conversations on a weekly basis. Everyone focused on the tactical execution they owned, but everyone also participated in the broader product direction. This wasn’t democratic decision-making for its own sake. Teams that understand the strategic context behind their tactical work make better decisions independently, generate stronger ideas than top-down direction produces, and develop the kind of ownership that makes people want to stay. I presented this philosophy at board level and leadership events — not as a design methodology but as an organizational operating principle.

What Carried Forward

I was at Meltwater for thirteen months. The systems thinking culture and design operations I established persisted well beyond my tenure and contributed — alongside many other factors and many other people’s work — to the environment that supported Meltwater’s 2020 IPO. The frameworks and team structures I built at Meltwater became the template I refined at Reva and Legacy Logix: hire for culture, distribute authority through structure, bring everyone into the strategic conversation, and remember that my job is to take all of the blame and give all of the credit. If I do that well, the team succeeds.