How our customers are using Klarity Works in their day-to-day

A blog outlining some of the ways our customers have surprised us in their usage of Klarity Works.

"Everyone has their own user experiences with how we like to use things and translate things, I just think having it all in one place is good for the business"

Lisa Parker - Head of HR

Introduction

 

I may be biased, but I use our product for almost everything I do.

 

From meeting notes, daily stand-up notes and transcribing user interviews, to writing our user guide, product spec and UX roadmap plans.

 

In addition to this, I get an insight to see how our customer and parent group, Invotra Group are using the product.

 

Whilst Klarity was initially designed to be policy management software, it has been fascinating to see the different ways people have began utilising our features.

 

In recent conversations with our users, I learned more about some of the ways our users are making the most of Klarity.

 

Product appropriation

 

The word ‘appropriation” carries weight, typically with negative connotations. However, within UX, appropriation is music to our ears: it simply means a product is being used for different purposes other than those originally intended.

 

Not only that, but appropriating a product fosters a sense of ownership. To a user that appropriates a product, they are using it in novel ways to solve a problem, which also leads to a sense of pride and self worth. And as we know, positive emotions are most likely to increase product loyalty. (Ou & Verhoef, 2017)

 

The fact that our customers were starting to use our product in ways we had not envisioned therefore was amazing to hear – we absolutely want to encourage this appropriation.

 

The teams

 

UX Design team

 

Documenting product screens and components

 

Managing a product’s design also means being responsible for a creating and maintaining extensive product component libraries.

 

Documenting a component library is no easy feat. This can include never ending lists screens in the product alongside even longer lists of components.

 

In short, this means creating a manual with many, many pages.

 

That is when our markdown-based, speedy document builder has become extremely convenient.

 

If you know exactly how many pages you need, including sub-pages, you can use it to bulk-create these in the blink of an eye.

 

Here’s what I’m talking about:

Klarity Works - Document builder screenshot

UX Writing & Content Strategy team

 

Creating a content matrix

 

I’ve gone over documenting the component library of product. But can we talk about how time consuming it can be to create a content matrix?

 

If you are unfamiliar with what a content matrix is, it’s nothing overly complicated. Originally a marketing strategy for visualising content, it’s a helpful way to gather inconsistencies in the language and tone of voice across a product.

 

Think content organised within a table, segregated by page or product area, with every sentence and word recorded accurately.

 

How do the UX Writing teams use Klarity to tackle this?

 

They use our quick-build tables, and they do it well.

 

See it here:

Klarity Works - Content matrix tables screenshot

Product teams

 

Writing efficient product specification

 

Product spec reaches every single person involved in building a product, and when everyone speaks the same language, especially in a remote world, that’s when the magic happens: there is trust, clarity and transparency.

 

Our Answers feature really brings this to light.

 

Answers are reusable snippets of information. Create one Answer, and add it in as many manuals as you like.

 

What’s even better, is that when an Answers is updated once, it also updates everywhere else that it has been used.

 

In conversation with Product Managers, I’ve come to find that Answers are the perfect solution when writing product spec where sources of truth need to be reused. Simply, you don’t need to write the same information over and over again across different documents.

 

Can you imagine all the different ways that using Answers could make your workflows more efficient?

 

See Answers in action here:

Klarity Works - Product Spec Answers screenshot

Business Admin team

 

Creating, updating and sharing an employee handbook

 

Every company is multifaceted and complex: they are its people, its policies, its culture, the learning, development, management, and so on.

 

With so many factors to be mindful of, how can these be neatly woven together in a place within reach of all employees?

 

Created with our document builder, incorporating several Answers and managed across different assignees, it’s never been easier to create an employee handbook.

 

On top of that, we’ve made it real easy to share anything created within Klarity: simply invite someone using their email address, or if they’re already signed up with us, just search for their username.

 

And we’ve taken this one step further by also making it possible to invite whole teams to content: all the right people in the right places.

 

Let’s take a look:

Human Resources team

 

Onboarding new employees

 

Starting a new job can be exciting, yet overwhelming. We can all remember our first few days as a new starter: a blur of new faces to meet, and a ton of new information to learn.

 

The latter can also involve reading through policies and guidelines, learning new processes and standards, all whilst being aware of new and old security risks.

 

How can we share all of this information in one go? The simplest answer: Kweries.

 

Kweries are advanced searches you can save. And they are Organisation-specific, which means that everyone in an Organisation will have access to its Kweries.

 

The HR team just needed to do one search, name it ‘Onboarding’, click ‘save’ …and voilà.

 

Accessible to everyone that is a member to that Organisation, selecting this Kwery opens all documentation related to onboarding, facilitating this process for new starters and HR managers, as well as saving them time.

 

Here’s another example of a Kwery:

More blogs you might like