Nimblework
Product Manager · 2022–2023
Rebuilding onboarding for an enterprise SaaS platform targeting SMB teams.
Enterprise software. SMB expectations.
Digite had built a powerful enterprise agile platform over many years. Nimblework OKRs was the attempt to take that technology and bring it to small and mid-sized teams — the kind that were used to Asana and Monday, not heavyweight project management suites.
The core differentiator was real: OKR-driven execution that linked goals directly to work items and Jira tickets. But the product experience assumed trained users, guided onboarding, and high tolerance for complexity. None of those assumptions held for SMB buyers.
The result was a consistent pattern in analytics: new users explored roughly 10% of the feature set, many dropped off after initial exploration, and demos performed well when guided but struggled in self-serve.
Onboarding isn't a UX problem. It's a product strategy decision.
The instinct was to add features — more integrations, more templates, more guided tooltips. My read was different. The product wasn't failing because it lacked features. It was failing because it didn't have a clear opinion about what a new user should do first.
The bet was simple: reduce the path from login to first value, make that path opinionated, and trust that users who experienced the core workflow would stay. Everything else was noise until that was solved.
This also meant negotiating the removal of legacy features — waterfall-style project management, work breakdown structures — that carried emotional weight internally but created cognitive load for new users. That negotiation was as much a part of the work as the product decisions.
Simplify, sequence, then scale.
The work broke into three tracks:
Onboarding redesign
Mapping the full user journey from signup to first board, identifying every unnecessary step, and rebuilding the flow with a clear opinionated path. The result was a reduction from roughly 11 clicks to 5 to reach first value.
Templates as a product strategy
Building domain-specific templates for different use cases: marketing, engineering, HR, executive OKRs. Each template came with pre-configured views, sample data, and dashboards so users could experience value immediately without configuration. Templates became the primary discovery mechanism for new users.
Integrations and automation
Designing cross-tool workflows that allowed work to be created and updated from Gmail, Slack, and Microsoft Teams. The goal was to reduce context-switching for SMB users who already lived in those tools. Extended through Zapier for custom team processes.
Simpler entry. Stronger retention signal.
The onboarding redesign reduced time-to-first-value significantly — from roughly 11 clicks to 5 to reach a first working board. Template adoption became a measurable leading indicator for sustained engagement.
The deeper shift was internal: the team moved from thinking about feature accumulation to thinking about user-centric simplification. That mindset change showed up in how roadmap decisions were made and how the product was positioned in sales conversations.
What I'd do differently: push for earlier instrumentation of the onboarding funnel so decisions were driven by data from day one rather than analytics that came in after the fact. The Whatfix data was valuable — but we were always slightly behind where we needed to be in understanding drop-off patterns.