Since we first released Kudozza, we’ve tried out different ways of presenting kudos, but we haven’t found the one format that works for every situation.
Organizations new to kudos usually prefer visually “rich” kudos.
But organizations that have been able to tap into the wealth that frequent giving of kudos brings to their culture, need kudos to be visually simpler and more compact as kudos tend to be all over their teams&channels.
And then we have customers in non-english speaking countries that prefer to translate the celebratory intro sentence of a kudos into their own language.
To fulfill all these needs, we’ve made it easy to configure the look of kudos per organization.
Examples
Visually highlighted kudos
This kudos has a very “loud” image so you will notice it. It also has a header which makes it a bit more ceremonial.
While an image always looks nice, it can be disturbing and takes precious space when rendered in the mobile version of Microsoft Teams.
The link is hidden behind the “More info” text.
The image is only displayed if no tag was used that contains an image. Otherwise the tag wins as it is more specific.
Compact kudos with intro text
Different text. Could also be translated. No image.
Use this if you have more kudos ongoing and you want to have a slim format that works in the message flow.
Pure kudos
Kudos without any static text as introduction. The author of the kudos is only mentioned in the “via” property of the message itself.
This is currently broken in the Microsoft Teams iOS client.
More information can be found in the configuration documentation.
On the other hand: We also updated the default look of Kudozzas kudos. If you like it, you don’t need to change anything!