Which organization makes successful use of conversations in Pyramid?
Hi everybody, we see the potential of chatting in Pyramid but it’s behavior is less intuitive than we expected. Nevertheless we think that we can start using this functionality if we introduce it within our organization in a smart way.With smart I mean that we give guidelines on how to use it (and what not to use in the beginning).
As we have little experience we cannot imagine what the most effective guidelines should be. Therefore we would like to get in contact with another customer that has implemented conversations successfully for a while now.
Who can help us?
If you mean "conversations", when you refer to "chatting" then here are some thoughts based on our experience:
- the conversation threads are not a replacement for Teams or Slack chats. They are instead a highly integrated way for people to converse around analytics, data and reports that are viewed inside Pyramid. Unlike Teams/Slack, the threads are tagged to the report or the data element, and can be viewed in this context at all times. It's not a generic chat session that runs without context.
- the conversation threads allow participants to jump back to the original report that triggered the thread as well viewing a snapshot of the report structure and/or the underlying data as well. This means the data behind the conversation is primarily hydrated and live - it's not static.
- we extended the basic conversation concept with a custom workflow, that allows use to create tasks for people (rather than just 'chat' about things). we used the built in task template example. This has made the conversational aspect more directed and driven towards an actionable outcome.
We started with using the delivered Conversation functionality on a single dashboard for our monthly operational review meetings. Prior to each meeting, each of our facilities would use the Conversation functionality to comment on any metrics that were below the specified threshold. We developed custom logic to allow for comments to be displayed in a separate window on the dashboard so that users would not have to open the Conversations. The variances/comments are then reviewed on the call.
The team has since transitioned to using the Custom Workflows functionality. This allowed us to tailor the comments input screen to meet our needs and we created two fields, one to enter an explanation for the variance and another field to enter the action plan to address the variance. We also streamlined the process for entering comments by removing some of the other required fields from the original Conversation input screen.