Case study

Culturely

A culture + performance operating system that supports HR, managers, and employees through OKRs, 1-on-1 meetings, and continuous alignment loops, delivered as a PWA.

B2B SaaSHRTechPWAOKRsPerformance
← Back
Culturely screenshot

TL;DR

  • What it is: A culture + performance operating system that supports HR, managers, and employees through OKRs, 1-on-1 meetings, and continuous alignment loops, delivered as a PWA (web-first, mobile-friendly).
  • My role: Owned product concept → workflow design → roadmap → delivery; built the core loops that connect goals, conversations, and visibility across teams.
  • Outcome: Launched in 2019 and positioned as a practical system to drive execution discipline and healthier manager-employee cadence.

Context

Most "culture" initiatives fail because they aren't operational. Teams either set goals but don't follow through, have meetings without structure, or track progress in disconnected docs/spreadsheets.

Culturely was built to make culture measurable through behavior: clear OKRs + consistent 1-on-1s + lightweight accountability, integrated into daily work.

Launch

Culturely launched in 2019 as a web-first product delivered as a Progressive Web App (PWA) - giving a mobile-friendly experience without building separate native mobile apps.

What the product does

OKRs (alignment + execution)
  • Create and track objectives and key results across individuals and teams
  • Visibility into progress and alignment across the org
  • A repeatable cadence for goal setting and check-ins
1-on-1 meetings (manager effectiveness)
  • Structured 1-on-1 templates and agenda-driven conversations
  • Follow-ups and continuity from meeting to meeting
  • A lightweight system to make 1-on-1s consistent and useful
HR visibility (without micromanagement)
  • Org-level visibility into goal alignment and manager cadence
  • Insights into whether teams are adopting healthy execution routines
Integrations (reduce friction)
  • Slack integration to meet users where they already work
  • HRIS integration to keep employee/team data in sync and reduce admin overhead

Feature highlights

Core (weekly usage)
  • OKR creation and tracking (individual + team alignment)
  • 1-on-1 meeting workflows (agenda, structure, continuity)
  • PWA experience (fast, accessible, mobile-friendly without native apps)
  • Slack integration for reminders, nudges, and workflow entry points
Advanced (system-level adoption)
  • HRIS sync for org structure and employee lifecycle updates
  • Cross-team visibility into progress and execution cadence
  • Templates and standardization to scale consistent habits across managers

Key decisions

Build around operating rhythms, not "culture content"

Tradeoff: inspirational content vs operational habits. We chose to anchor the product around OKRs and 1-on-1s - the two routines that actually change behavior.

Outcome: Clearer value, more repeatable adoption, and stronger day-to-day relevance.
PWA instead of native apps

Tradeoff: native polish vs speed + reach. Chose to deliver a PWA so teams get mobile-friendly access with faster iteration and lower maintenance cost.

Outcome: Better rollout speed and accessibility without splitting the roadmap across platforms.
Integrate into where people already work (Slack + HRIS)

Tradeoff: push users to a new tool vs embed into existing systems. Used Slack to reduce friction and HRIS as the source of truth for people/teams.

Outcome: Improved adoption and reduced admin work.

Impact

Launch
2019
Delivery
PWA (web-first, mobile-friendly)

Technical depth

  • Designed the data model connecting people ↔ teams ↔ OKRs ↔ 1-on-1s
  • Built product workflows optimized for consistency and repeat use
  • Implemented Slack integration for engagement loops and entry points
  • Implemented HRIS integration for org/team sync and lifecycle events
  • Built a PWA experience for performance and accessibility

What I learned

  • Culture products win when they create repeatable habits, not one-time engagement.
  • Managers need simple structure more than dashboards.
  • Integrations aren't "extra" - they're the adoption engine.

Collaboration

  • Engineering (architecture, integration design, PWA performance)
  • Design (low-friction OKR and 1-on-1 experiences)
  • HR leaders + managers + employees (workflow validation and rollout feedback)
  • Customer Success / Sales (onboarding playbooks and adoption loops)
See resume →