Talk about your next project
Lattice case study

The lesson

Make the software story about the customer’s operating model first, then show how the rollout was shaped to fit it.

The move

The story opens with the Klick Health logo, the title, Shveta Malhan’s name and role, a customer image, and a left rail with company context, industry, company size, and the Lattice products used. A purple “AI SUMMARY” box says Klick Health wanted to keep its people-focused culture strong as the company grew, followed by a named quote from Shveta about Lattice’s People Strategy Group. The body starts with Klick Health’s people-first culture, then explains the lack of a formal company-wide goal-setting and performance review process, the choice of Lattice, the “Using Lattice at Klick Health” rollout, and the “Impact of Lattice” section. The rollout details include Lattice’s People Strategy Group, a beta group of senior executives, interviews with 150 “Klicksters,” and the “Cultivate Performance” review cycle, before the impact section cites OKR adoption and end-of-year review engagement.

Why it works

  • Our readThe story names Shveta Malhan at the top, so the rollout is anchored in one accountable people leader rather than a generic company voice.
  • Our readThe culture setup explains why Klick Health could not simply copy a standard OKR or review program.
  • Our readThe beta group, employee interviews, and named review cycle make the implementation feel like a designed change program, not just software deployment.

What not to copy

Don't copy Klick Health’s “crafts” structure, “Klicksters” language, or “Cultivate Performance” name. Keep the structure of culture context, missing process, advisory support, staged rollout, and customer-owned adoption proof.

More from Lattice

More case studies

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.